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.

RTCS subsystem started task PROC


The following figure is an example of the RTCS subsystem started task PROC. The text that should be customized is shown in bold. This sample JCL is contained in member OSZ$RTCS in the TOSZCNTL target library.

RTCS subsystem started task PROC

  //OSZRTCS  PROC
//*
//OSZRTCS EXEC PGM=OSZMOSYS,           RTCS Subsystem Initialization
//             TIME=1440,              No SMF CPU or wait time limits
//             REGION=0M               No limits on virtual storage

Copy this member into one of the following locations:

  • SYS1.PROCLIB or another PROCLIB that is available to started tasks that are started under the Master Subsystem (MSTR)
  • A JES-managed started task PROCLIB

Specify the member name of this PROC in the OSZRTCS-PROC option of the RTCS Initialization member of Logical PARMLIB. If the name of the PROC used to START the RTCS Initiator address space contains the four characters INIT, the default name of the RTCS subsystem started task PROC will be the same, except that the characters RTCS will be substituted for the characters INIT in that PROC name. If you name the started task PROCs in this manner, you do not need to update the RTCS Initialization member (for this purpose).

The RTCS subsystem control address space is started internally by the RTCS Initiator address space, as early as possible in the z/OS IPL process. If the RTCS Initiator address space (by default, PROC OSZINIT) was started under the Master Subsystem using SUB=MSTR, then, by default, the RTCS subsystem address space will be started under the Master Subsystem also.

 

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