Creating the RTCS subsystem started task PROC

Use the following procedure to create the RTCS subsystem started task PROC.

Note

  • 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.
  • A model RTCS subsystem started task PROC (OSZRTCS) is provided in RTCS-subsystem-started-task-PROC. Other than selecting the actual PROC name and possibly making some additions to the EXEC statement to adhere to local conventions and requirements, such as adding an ACCT parameter, no further changes should be made to the model PROC. In particular, no DD statement should be present.
  1. Select a name to be used for the RTCS subsystem started task PROC.BMC recommends using the name OSZRTCS, but this is not required. This name will be used in an z/OS START command that the RTCS Initiator (OSZSIRIS) issues to start the RTCS subsystem address space.

  2. Copy member OSZ$RTCS 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.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.

Related topic

Manually-configuring-RTCS


 

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