RTCS subsystem started task PROC

The following figure displays sample RTCS subsystem started task PROC. The OSZ$RTCS member in the TOSZCNTL target library contains this sample JCL.

//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

Related topic

Sample-JCL-and-z-OS-image-configuration-members

You can save 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 that is used to START the RTCS Initiator address space contains four characters INIT, the default name of the RTCS subsystem started task PROC remains the same, except that the characters RTCS are 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.

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 is started under the Master Subsystem using SUB=MSTR, the RTCS subsystem address space starts under the Master Subsystem by default.


 

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