Creating and customizing the RTCS Initiator started task PROC

Use the following procedure to create and customize the RTCS Initiator started task PROC.

Related topic

Manually-configuring-RTCS

  1. Select a name for the RTCS Initiator started task PROC.This name will be used in the z/OS START command to start the RTCS Initiator address space, preferably under the Master Subsystem (MSTR). We recommend using the name OSZINIT , but this is not required.

    Important

    • A model RTCS Initiator started task PROC (OSZINIT) is provided in RTCS-initiator-started-task-PROC.
    • If you are sharing data sets, you must complete this task only once per sysplex Otherwise, complete this task for each of the target z/OS images.
    • You will use the RTCS Initiator started task PROC that is created in this step to start RTCS. The RTCS subsystem address space is not started directly. When you run the RTCS Initiator started task PROC, it performs specific z/OS system checks, validates that the product’s production data sets have been properly allocated, and internally starts the RTCS subsystem address space. The DSNAMEs that are specified in the RTCS Initialization member and dynamically allocated by the RTCS Initiator started task are recorded in ECSA storage. This information is used to dynamically allocate data sets as required in the RTCS subsystem and Generalized Server address spaces.

  2. Copy the OSZ$INIT member from the SMP/E TOSZCNTL target library to SYS1.PROCLIB or a JES-managed started task procedure library using the member name that you selected in Step 1.We recommend that you start RTCS under the Master Subsystem by using SUB=MSTR on the START command. 

    If you start RTCS under the Master Subsystem and you use an unmodified MSTJCL00, you must use SYS1.PROCLIB specifically for the started tasks that are started under the Master Subsystem. Otherwise, you do not require to create the PROC in SYS1.PROCLIB. You can use any started task procedure library that is defined in the IEFPDSI DD statement concatenation in the Master Scheduler JCL that contains the member MSTJCLxx of SYS1.PARMLIB. If you start RTCS under your primary JES, you can place the PROC in any JES-managed started task PROCLIB.

  3. Modify the STEPLIB DD statement in the new PROC to specify the DSNAME of the RTCS subsystem program library (POSZRTCS). For example, you can use the PDSE that was created in Creating-POSZRTCS.




 

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