This module is invoked by CA TLMS operating system intercepts used for processing during OPEN/CLOSE/EOV. All functions are consolidated into this module, which is automatically installed by CAIRIM (CA Resource Initialization Manager component). The following programs are executed by the operating system intercepts from TLMSOSMM.
TLMSCLSE is a module executed as an exit from CLOSE. Linked into the common SVC, it is activated by an SVC called from the intercept. CLOSE modules differ depending on the operating system in use.
TLMSCLSE examines the CLOSE in process and builds a CA TLMS transaction with a type code of 1 for output tape or 2 for input tape. For output files, a type 1 transaction may cause a gummed label to be printed, and the DSN and run statistics to be recorded in the VMF.
TLMSCLSE passes the transaction to CA TLMS by issuing an SVC to the TLMSQMGR module. TLMSCLSE does not wait for the process to complete; an immediate return to CLOSE processing takes place.
TLMSOPEN is a module executed as an exit from OPEN. Linked into the common SVC, it is activated by an SVC called from the intercept. The OPEN modules differ depending on the Operating System in use.
TLMSOPEN examines the OPEN in process and builds a CA TLMS transaction with a type code of 6. For output files, a type 6 transaction is intended to obtain permission to write upon the mounted volume, and to flag the VMF that the volume is in use. For input files, a type 6 transaction is used to verify the input DSN against the VMF DSN, if the IDSNVER system option is set to YES.
TLMSOPEN passes the transaction to CA TLMS by issuing an SVC to the TLMSQMGR module. OPEN then waits for the process completion post. When posted, a return vector is passed back to OPEN, reflecting the status of the transaction: good, use tape; or bad, demount tape and try again.
TLMSQMGR is linked into the common SVC. For CA TLMS, TLMSQMGR performs all cross-memory services when invoked by either of the exit modules (SVCs): TLMSOPEN, TLMSCLSE. These exit modules build a CA TLMS transaction, then invoke TLMSQMGR to queue the transaction (in a CSA queue), and notify TLMSMAIN that there is a transaction to be processed.
At a later point in the cycle, TLMSQMGR is again invoked, by TLMSMSGQ. TLMSQMGR dequeues the transaction, and presents it to TLMSMSGQ.
The module accessed through SVC which manages security calls to the operating system security component.
|
Copyright © 2014 CA.
All rights reserved.
|
|