TMSINIT started again when OPSMAIN is recycled
Article ID: 442712
Updated On:
Products
Issue/Introduction
TMSINIT is used to activate, batch activate, or deactivate CA 1 on the operating system. Once initialization is complete, TMSINIT terminates and does not remain active as a task.
When SSM is initialized it may attempt to start TMSINIT again because it is not found as an active started task.
Environment
OPS/MVS
Cause
TMSINIT is not defined with type CA1 in SSM
Resolution
The rule SSMSTATE is the place where the actual state of tasks is detected after OPS/MVS is restarted. For TMSINIT, there is already code in the exit SSMSTAUX that is code called by SSMSTATE and can be customized according to each site requirements.
If you browse the SSMSTAUX exit you will see the code below:
/*--+----1----+----2----+----3----+----4----+----5----+----6----+----*/
If res_type = 'CA1' Then Do
say 'res_type: 'res_type
res_jstate = down /* Assume CA1 is down */
res_tstate = down
Call TYPECA1 /* Find true state */
If Result = 0 Then Do
res_jstate = up /* Set jobname state to up */
res_tstate = up /* Set type test state to up */
end
end
The subroutine TYPECA1 follows this section. It checks in storage if CA 1 (TMSINIT) has already been started or not.
You need to either use TYPE=CA1 for TMSINIT or change this part of the code in SSMSTAUX to check for the jobname for example:
If res_job = 'TMSINIT' Then Do
Feedback
