Utilities › TMSINIT Utility—Activate, Deactivate CA 1

TMSINIT Utility—Activate, Deactivate CA 1

Use the TMSINIT utility to activate, batch activate or deactivate CA 1 on the operating system. TMSINIT also initiates the CA 1 health checks.

CAIRIM initialization activities for CA 1 must have completed successfully for TMSINIT to execute properly. CA 1 can be present in your operating system in one of the following four states:

• In an active state, all CA 1 batch and online facilities are fully functional. The CA 1 OSI is installed and tape activity is tracked.
• In a batch active state, all CA 1 batch and online facilities are fully functional. No realtime tape activity is tracked. The OSI is restored if it is currently installed.
• In an inactive state, some CA 1 batch facilities but none of the CA 1 online facilities are functional. No realtime tape activity is tracked. The OSI is restored if it is currently installed.
• In an uninitialized state, a few CA 1 batch facilities but none of the CA 1 online facilities are functional. Any jobs requesting tape I/O are abended (S8xx). Most CA 1 utilities will abend with U0011. The uninitialized state occurs when the operating system has been IPLed and TMSINIT has not been executed to place CA 1 into an active, batch active or inactive state. If the subsystem and TMSINIT have not been started, each tape open will receive IECTMS0.

  Note: For a description of this message and correction action, see the Messages Reference Guide.

Except for the first execution after an IPL to activate CA 1, all calls to TMSINIT will result in an additional call to the security system. If the first execution of TMSINIT after an IPL is to deactivate or batch activate CA 1, an additional call to the security system is made. If TMSINIT is run as a batch job, the security authorization of the job is used to determine access. If TMSINIT is run as a started task, a WTOR is issued to obtain the operator's user ID and password. This information is used to determine if the operator has the correct authority to reinitialize, batch-activate or deactivate CA 1. Set the SECWTO option in the TMOOPTxx member of CTAPOPTN to NO if you do not want to validate that the operator executing TMSINIT as a started task has the correct level of authority. This will allow TMSINIT to be executed as a started task by anyone with access to a console.

TMSINIT is used to activate CA 1, and is typically included as part of the system IPL procedures. Deactivation and batch activation of CA 1 can also be performed with this utility. TMSINIT, as a started task, does not stay active in the system once CA 1 is initialized. The system console is issued WTORs for operator response by the SVCs called by TMSINIT, such as:

IEFTMS0 REPLY 'U' FOR CA 1. rnn.n INITIALIZATION OR HELP

Where nn.n is the CA 1 release number.

Important! The IEFTMS0 message should not be responded to by an automated console manager, such as CA-Opera, since there are variable responses to this WTOR. In certain types of critical situations, several executions of TMSINIT may be needed with a response other than U. If an automated console manager is used, then PARM=NODATE should be specified for normal TMS initialization. Do not call the started task for TMSINIT execution TMS, as this is the CA 1 subsystem name.

Note: If you have other vendor products which modify the operating system data management modules and these modified versions MLPA'd, you must include the CAG8LIB2 DD in the CAIRIM procedure and the TMSINIT procedure. Any MLPA data set must be specified in the CAG8LIB2 DD which contains these modifications. If you have a data set name for the contents of the LPA other than SYS1.LPALIB, you must put that data set name in the CAG8LIB1 DD and include the DD in the CAIRIM procedure and the TMSINIT procedure. Ensure that both the CAIRIM procedure (CAS9) and the TMSINIT procedure have security access (READ) to the libraries containing the operating system's data management module. If all of the open/close routines are not copied to the modified library, then you must have SYS1.LPALIB in the concatenation with CAG8LIB1.

For the first execution of TMSINIT after an IPL to activate or batch activate CA 1, TMSINIT initiates the CA 1 health checks in the CA Common Services CAHCHECK address space if it is available. The CAHCHECK address space comes up very early in the IPL and normally remains up for the entire IPL. Thus, CA 1 health checks that are hosted by the CAHCHECK address space monitor CA 1 for the life of the IPL.

If the CAHCHECK address space is not available, TMSINIT will not initiate the CA 1 health checks. In order to initiate and host the CA 1 health checks, the CTS address space must be started. If CTS is started in an environment where the CAHCHECK address space is not available, CTS will automatically start the CA 1 health checks.

Because TMSINIT can be used to change system options that CA 1 health checks examine, any subsequent executions of TMSINIT will trigger those CA 1 health checks to run again regardless of whether TMSINIT or CTS originally initiated them.

CA 1 must be active before other software packages that use tape or look for the CA 1 mount messages. These include but are not limited to OAM and HSM.