End of supportThis version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.BMC recommends upgrading to the latest version of the product. To see documentation for that version, seeBMC Discovery for z/OS 1.8.

Add RTCS entries to system parameters

This step describes how to create started task procedures for the following RTCS address spaces:

  • RTCS Generalized Server
  • RTCS subsystem
  • RTCS Initiator

The RTCS Initiator started task procedure starts RTCS. The RTCS subsystem address space is not started directly. When it runs, the RTCS Initiator started task procedure performs certain system checks, verifies that the product data sets have been properly allocated, and starts the RTCS subsystem address space. The DSNAMEs that are allocated by the RTCS Initiator started task procedure are recorded internally by RTCS and used to dynamically allocate these data sets in the RTCS subsystem and Generalized Server address spaces. 

BMC recommends that all customers start the RTCS Initiator under the MVS Master Subsystem (by specifying SUB=MSTR on its START command). By doing so, the RTCS subsystem address space will also be started automatically under the Master Subsystem by the RTCS Initiator. 

It is not generally desirable to start RTCS under the primary JES, but this mode of operation is supported. If RTCS is started under the primary JES, you will not be able to shut down the primary JES cleanly until the RTCS subsystem address space (as well as all other started task address spaces) are first shut down completely. Under rare circumstances it will be not be possible to shut down the RTCS subsystem address space completely. This is one of the main reasons BMC recommends that RTCS be run under the Master Subsystem.

Note

For each of the following procedures, if you use an unmodified MSTJCL00, you must use SYS1.PROCLIB for started tasks that are started under the Master Subsystem (MSTR). Otherwise, you can use any started task procedure library that is defined in the IEFPDSI DD statement concatenation in the z/OS Master Scheduler JCL (member MSTJCLxx of SYS1.PARMLIB)

RTCS Generalized Server—TOSZCNTL member OSZ$EXEC

Use member OSZ$EXEC as a model to create the RTCS Generalized Server started task procedure.

Note

The RTCS Generalized Server procedure must be defined in a procedure library for the Master Subsystem and in a JES-managed procedure library. These procedure libraries might be the same library, depending on your site’s PROCLIB configuration. If the OSZEXEC procedure is to reside in two separate data sets (one for each PROCLIB concatenation), each procedure must be identical and must have the same PROC name.

  1. Choose a name for the RTCS Generalized Server started task procedure.

     BMC recommends using the name OSZEXEC.

    If this procedure needs to be placed in two PROCLIB concatenations, you must use the same name for both PROCs in each one. The specified PROC name is used in MVS START commands that are issued internally by the RTCS subsystem address space, and the only difference between any two generated START commands is the presence or absence of SUB=MSTR, so the PROC names need to be identical in the data set for each type of PROCLIB.

    You might need specify the PROC name to be used to start a Generalized Server address space in the OSZEXEC-PROC parameter of the RTCS initialization member from the Logical PARMLIB data set used by the RTCS Initiator started task procedure, as described by RTCS Initiator—TOSZCNTL member OSZ$INIT.

    The default PROC name is OSZEXEC. If that is acceptable, no modification of the default RTCS initialization member is required.

  2. Copy member OSZ$EXEC from the TOSZCNTLSMP/E target library to any valid Master Subsystem PROCLIB and change the member name to the name that you chose in step 1.

    This procedure must exist in a Master Subsystem PROCLIB, because RTCS Generalized Server address spaces are sometimes started by RTCS with a specification of SUB=MSTR.

  3. Copy member OSZ$EXEC from the TOSZCNTL SMP/E target library to any valid JES-managed started task PROCLIB and change the member name to the name that you chose in step 1.

    This procedure must exist in a JES-managed PROCLIB, because RTCS Generalized Server address spaces are sometimes started by RTCS without specifying SUB=MSTR. In this case, the RTCS Generalized Server runs under the primary JES, and its procedure is expanded by using the usual JES-managed started task PROCLIBs.

RTCS subsystem—TOSZCNTL member OSZ$RTCS

Use member OSZ$RTCS as a model to create the RTCS subsystem started task procedure.

  1. Choose a name for the RTCS subsystem started task procedure.

    BMC recommends using the name OSZRTCS.

    This name is used in an MVS START command that is issued internally by the RTCS Initiator to start the RTCS subsystem address space.

    You might need to specify the PROC name to be used to start the RTCS subsystem address space in the OSZRTCS-PROC parameter of the RTCS initialization member from the Logical PARMLIB data set used by the RTCS Initiator started task procedure, as described by RTCS Initiator—TOSZCNTL member OSZ$INIT. 

    The default PROC name is OSZRTCS. If that is acceptable, no modification of the default RTCS initialization member is required.

  2. Copy member OSZ$RTCS from the TOSZCNTL target library to one of the following locations and change the member name to the name that you chose in step 1:
    • SYS1.PROCLIB if the RTCS subsystem and the RTCS Initiator are to be run under the Master Subsystem
    • a JES-managed started task PROCLIB if they are to be run under the primary JES


RTCS Initiator—TOSZCNTL member OSZ$INIT

Use member OSZ$INIT as a model to create and customize the RTCS Initiator started task procedure.

  1. Choose a name for the RTCS Initiator started task procedure.

    BMC recommends using the name OSZINIT.

    This name is used in an MVS START command to start the RTCS Initiator address space.

  2. Copy member OSZ$INIT from the TOSZCNTL target library to one of the following locations and change the member name to the name that you chose in step 1:
    • SYS1.PROCLIB if the RTCS Initiator is to be run under the Master Subsystem
    • a started task PROCLIB if it is to be run under the primary JES
  3. In the member that you created in step 2, change the STEPLIB DD statement to specify the DSNAME of the RTCS subsystem program library that you allocated in “Subsystem program library—TOSZCNTL member OSZINJ71” in Validate Runtime Component System (RTCS) data sets.

Related topic

Mainframe-customization-steps-for-z-OS


 

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