Creating and customizing the RTCS Initiator started task PROC

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

Note

A model RTCS Initiator started task PROC (OSZINIT) is provided in RTCS-Initiator-started-task-PROC.
You need to completed this task only once per sysplex if you are sharing data sets. Otherwise, this task needs to be completed for each target z/OS image.
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 certain 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 (or defaulted to based on the DSNAME of the RTCS subsystem program library) and dynamically allocated by the RTCS Initiator started task are recorded in ECSA storage. That information is then used to dynamically allocate these data sets, when and as required, in the RTCS subsystem and Generalized Server address spaces.

Select a name for the RTCS Initiator started task PROC.This name will be used in an z/OS START command to start the RTCS Initiator address space, preferably under the Master Subsystem (MSTR). BMC recommends using the name OSZINIT , but this is not required.
Copy member OSZ$INIT 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.BMC recommends that you start RTCS under the Master Subsystem (by using SUB=MSTR on the START command). But this is not absolutely required.
If you start RTCS under the Master Subsystem and you use an unmodified MSTJCL00, you must use SYS1.PROCLIB specifically for those started tasks that are started under the Master Subsystem. Otherwise, the PROC does not need to be created in SYS1.PROCLIB, and you can use any started task procedure library that is defined in the IEFPDSI DD statement concatenation in the Master Scheduler JCL (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.
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.

On this page