Sample JCL and parameter (TOSZCNTL) library members
The following table describes the TOSZCNTL library members:
Member | Description |
---|---|
OSZ$INIT | OSZ$INIT is sample RTCS Initiator started task procedure (PROC) JCL. You can copy this member and save into SYS1.PROCLIB or another Master Subsystem started task procedure library that is specified in the z/OS image’s Master JCL. We recommend naming the copied member as OSZINIT; however, this is not required. You can customize the STEPLIB DD statement by specifying the DSNAME of the RTCS subsystem program library. If OSZINIT is started under the z/OS Master Subsystem (MSTR), the PROC must be located in SYS1.PROCLIB (or equivalent). After that, you can use the following operator command to start the RTCS Initiator: S OSZINIT,SUB=MSTR If OSZINIT is started under the Primary JES, the PROC can be located in any JES-managed started task PROCLIB. After that, you can use the following operator command to start the RTCS Initiator: S OSZINIT |
OSZ$RTCS | OSZ$RTCS is sample RTCS subsystem started task procedure (PROC) JCL. If OSZINIT is started under the Master Subsystem, the PROC must be located in SYS1.PROCLIB (or equivalent) because OSZRTCS is also, by default, started by the RTCS Initiator (internally) under the z/OS Master Subsystem (MSTR). Because no parameters, data sets, or DD statements exist in this PROC, customization is not required. If RTCS is started under the Master Subsystem or into a JES-managed PROCLIB, you can copy this member and save into one of the following:
We recommend naming the copied member as OSZRTCS. You must specify the RTCS subsystem PROC name in the OSZRTCS-PROC option in the RTCS initialization member of Logical PARMLIB. |
OSZ$EXEC | OSZ$EXEC is sample RTCS Generalized Server address space started task procedure (PROC) JCL. Because no parameters, data sets, or DD statements exist in this PROC, customization is not required. Copy this member and save it to all of the following locations:
We recommend naming the copied member as OSZEXEC. You must specify the RTCS Generalized Server PROC name in the OSZEXEC-PROC option in the RTCS initialization member of Logical PARMLIB. |
OSZ$REGI | OSZ$REGI is sample JCL that is used to execute the RTCS Registry Maintenance Utility (RMU). You can copy this member and save it to a site-specific data set. To specify the DSNAMEs of the SMP/E target XML (TOSZRXML) document library and any customized XML document library, you must customize the DD statements in the JCL along with the JOB statements. |
OSZRBACK | OSZRBACK is sample JCL that is used to perform RMU backup processing. You can copy this member and save it to a site-specific data set. The BACKUP control statement in OSZRBACK writes a portable, sequential backup of the data in an RTCS registry to the data set defined by the specified ddname. You must specify the ddname of the backup data set. |
OSZRREST | OSZRREST is sample JCL that is used to perform RMU restore processing. You can copy this member and save it to a site-specific data set. The RESTORE control statement in OSZRREST restores the contents of the sequential backup data set defined by the specified ddname to the currently active registry. You must specify the ddname of the backup data set that you want to restore. |
OSZSCHED | OSZSCHED is a sample set of required SYS1.PARMLIB PPT additions for RTCS. You can copy this member and save it to the required z/OS target image-specific PARMLIB data set. Copy it as a new member named SCHEDxx, or copy its contents into any existing PPT member. |
Related topic