Creating POSZRTCS
Because of PDSE sharing requirements, consider making a unique copy of this library for exclusive production use on each individual target z/OS image on which RTCS is to be started. Alternatively, you can use a single data set, shared among all members of a single sysplex.
For more information about production libraries,their advantages, and about sharing this library in a sysplex, see Runtime-production-libraries.
Requirements for creating POSZRTCS
The following requirements apply when creating POSZRTCS:
- The POSZRTCS library that you create must be a PDSE library. BMC recommends that it be allocated as a non-SMS-managed PDSE (that is, no STORCLAS specified), but it can be SMS-managed if desired.
The name of the data set that you create must be specified by the DSNAME parameter on the STEPLIB DD statement in the RTCS Initiator PROC (see Creating-and-customizing-the-RTCS-Initiator-started-task-PROC).
This is the only RTCS production library whose DSNAME needs to be specified in a DD statement in a started task PROC. If each of the remaining RTCS production libraries are allocated with a DSNAME prefix that matches this library, along with its recommended low-level index, the RTCS Initiator will be able to derive a matching, default DSNAME for them, which the RTCS subsystem will then use to dynamically allocate these data sets. If not, then the DSNAMEs of the non-conforming production libraries will need to be specified by the appropriate parameters in the RTCS Initialization member (which is usually, OSZINI00) of the z/OS Logical PARMLIB data set.
- Because it will be dynamically allocated by the RTCS Allocator (OSZMOSYS, the first program to run in the RTCS Subsystem address space), this library must be cataloged. The catalog must be available when RTCS is STARTed.
- The low-level index of the DSNAME selected for this production library should be POSZRTCS or OSZRTCS.
To create POSZRTCS
Allocate and copy the target SMP/E RTCS subsystem program library (TOSZRTCS) into a new POSZRTCS PDSE.
You can customize the sample JCL shown in the following figure.
The text that should be customized is shown in bold. This sample JCL is contained in member OSZINJ71 in the TOSZCNTL target library.//OSZINJ71 JOB (acct),'CREATE POSZRTCS PDSE',
// MSGLEVEL=(1,1),CLASS=A,TIME=1
//*
//* acct JOB statement accounting information
//* xxxxxx VOLSER on which to allocate .POSZRTCS PDSE
//* tlibprfx DSN prefix of RTCS SMP/E target libraries
//*
//ALLOC EXEC PGM=IEFBR14
//*
//* Allocate a new non-SMS-managed cataloged PDSE for
//* the RTCS Subsystem Library. This data set may be
//* SMS-managed, but the JCL will have to be changed
//* to allocate an SMS-managed data set. There is no
//* particular need for the library to be SMS-managed.
//* This data set CAN be shared by more than one system
//* if MVS sysplex PDSE sharing requirements are met.
//*
//OSZRTCS DD DSN=SYS2.RTCS.POSZRTCS,
// DISP=(NEW,CATLG),
// UNIT=3390,VOL=SER=xxxxxx,
// DSNTYPE=LIBRARY,SPACE=(CYL,(16,5,01)),
// DSORG=PO,RECFM=U,LRECL=0,BLKSIZE=23476
//*
//COPY EXEC PGM=IEBCOPY,TIME=1,REGION=4M
//*
//* Copy SMP/E Target RTCS Subsystem LIBRARY
//* to the newly-allocated 'production' PDSE.
//*
//SYSPRINT DD SYSOUT=*
//TOSZRTCS DD DISP=SHR,DSN=tlibprfx.TOSZRTCS
//OSZRTCS DD DISP=SHR,DSN=*.ALLOC.OSZRTCS
//SYSIN DD *
COPY INDD=((TOSZRTCS,R)),OUTDD=OSZRTCS
//*
Related topic