Space announcement We are no longer updating this version of the documentation for the infrastructure components (DBC, LGC, and NGL).  You can no longer leave comments on it. For the latest version of the documentation, see Common Mainframe Infrastructure 2022 release.

Adding the RTCS start command to SYS1.PARMLIB

Use the following procedure to the RTCS start command to SYS1.PARMLIB.

Determine the appropriate COMMNDxx member of SYS1.PARMLIB (or the logical PARMLIB data set for the z/OS image), and modify the member to include one of the following lines:COM='S OSZINIT,SUB=MSTR’

COM='S OSZINIT'

In the commands, the OSZINIT value represents the name of the RTCS Initiator started task PROC.

Note

The RTCS subsystem should usually be started before the primary JES but after the ESM has initialized.

At some sites, this will not be possible because the ESM is started after or under the primary JES. In such cases, the RTCS subsystem should be started as soon as possible, even if it is to be started under the Master Subsystem (SUB=MSTR). If this is still not possible (because the RTCS subsystem needs to be started before the primary JES and run under the Master Subsystem so that it will be available for product address spaces that also start before the primary JES and which are also started under the Master Subsystem), after the ESM has completely initialized on the z/OS image, issue the following operator command:

F RTCS,REFRESH,SECURITY

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*