RTCS Initiator started task PROC
The following figure is an example of the RTCS Initiator started task PROC.
The text in <brackets> represents items that you need to replace with values that are specific to your site; the table describes these items. Update these statements to reflect the actual DSNAMEs and PROCs to be used. The DSNAMEs are established by the Desktop Installation Assistant, if it is used to configure the target z/OS image. If you copy this PROC for use on another z/OS image, update these DD statements, if necessary. This sample JCL is contained in member OSZ$INIT in the TOSZCNTL target library.
//*
//<OSZINIT> EXEC PGM=OSZSIRIS, RTCS Initiator Program
// TIME=1440, No SMF CPU or wait time limits
// REGION=0M No limits on virtual storage
//*
//* STEPLIB: RTCS Subsystem Program Library (.TOSZRTCS, or a copy)
//*
//STEPLIB DD DISP=SHR,DSN=<SYS2.RTCS.POSZRTCS>
RTCS Initiator started task PROC customizations
Default value | Description | Detailed information |
|---|---|---|
OSZINIT | RTCS subsystem started task PROC name | |
SYS2.RTCS.POSZRTCS | RTCS subsystem program library DSNAME |
Copy this member into one of the following locations:
- SYS1.PROCLIB or another PROCLIB that is available for started tasks that are started by using the Master Subsystem (MSTR)
- A JES-managed started task PROCLIB.
The RTCS Initiator address space should be started as early as possible in the z/OS IPL process after the security system has been initialized. The following examples illustrate the appropriate command (the RTCS Initiator started task PROC member name is shown in bold).
S OSZINIT
S OSZINIT,SUB=MSTR
The RTCS Initiator address space is not the same address space as the RTCS subsystem address space. The RTCS Initiator starts the RTCS subsystem address space internally after performing validation procedures on the following items:
- z/OS system image
- STEPLIB data set (which becomes the POSZRTCS parameter, internally)
- POSZLINK data set
- POSZHTML data set
- SREGVLDS VSAM LDS used to back the RTCS system registry (for dedicated, nonshared RTCS system registry configurations)
- POSZPSWD product authorization table library
STEPLIB DD statement
The RTCS Initiator internally passes the DSNAMEs of the data sets that are used by the RTCS subsystem and the RTCS Generalized Server address spaces in z/OS ECSA storage.
The RTCS Initiator obtains the DSNAME of the RTCS subsystem program library (POSZRTCS) from the STEPLIB DD statement of the RTCS Initiator address space started task PROC JCL. The RTCS subsystem address space dynamically allocates this data set, loads the RTCS kernel and DLLs, and deallocates the program library to enable maintenance to be performed by using SMP/E.
The DSNAME of the RTCS subsystem program library (which is specified by the STEPLIB DD statement of the RTCS Initiator started task PROC JCL) is used as the model to determine the default DSNAMEs of the other RTCS data sets used by the RTCS subsystem and the RTCS Generalized Server. The data set prefix (the part up to but not including the low-level index) is determined and the low-level index is examined to see if it is xOSZRTCS, where x is any character. If it is xOSZRTCS, the default DSNAMEs of all of the other data sets will be constructed from the POSZRTCS DSNAME prefix and their own individual, appropriate low-level index, such as xOSZLINK, xOSZHTML, xOSZPSWD, and REGISTRY.
Related topic