Space announcement We are no longer updating this version of the documentation for the infrastructure components (DBC, LGC, and NGL).  You can no longer leave comments on it. For the latest version of the documentation, see Common Mainframe Infrastructure 2022 release.

Creating the RTCS Generalized Server started task PROCs

The RTCS Generalized Server PROC must reside in some data set (but not necessarily in the same data set) that is allocated to each of the following PROCLIB concatenations:

  • Master Subsystem procedure library
  • JES-managed started task procedure library

The PROC might reside in a single data set that appears in both concatenations, depending on your site’s PROCLIB configuration. If the PROC is to reside in two separate data sets (one for each PROCLIB concatenation), then each PROC must be identical and must have the same member (PROC) name.

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 Generalized Server started task PROC (OSZEXEC) is provided in RTCS-Generalized-Server-started-task-PROC.

To create the RTCS Generalized Server started task PROCs

  1. Select a name to be used for the RTCS Generalized Server started task PROCs.
    • BMC recommends using the name OSZEXEC, but this is not required.
    • If this PROC needs to be placed in two concatenations, you must use the same name for both PROCs. This name will be used in START commands that will be issued internally by RTCS.
  2. Copy member OSZ$EXEC from the SMP/E TOSZCNTL target library to any valid Master Subsystem PROCLIB and use the member name that you selected in Step 1.
    • This PROC must exist in a Master Subsystem PROCLIB, because RTCS Generalized Server address spaces are sometimes started by RTCS with a specification of SUB=MSTR.
    • If 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).
  3. Copy member OSZ$EXEC from the SMP/E TOSZCNTL target library to any valid JES-managed started task PROCLIB and use the member name that you selected in Step 1.This PROC must exist in a JES-managed PROCLIB, because RTCS Generalized Server address spaces are usually started by RTCS without specifying SUB=MSTR. In this case, the RTCS Generalized Server runs under the primary JES, and its PROC is expanded by using the usual JES-managed started task PROCLIBs.

 

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