RTCS initiator started task PROC


The following is an example of the RTCS initiator started task PROC.

//<OSZINIT>  PROC
//*
//<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>

The text in the angle brackets (<>) represents variable or placeholder text that you can replace with values that are specific to your site.

The following table describes the default values. 


RTCS initiator started task PROC customizations

Default value

Description

Link for more information

OSZINIT

RTCS subsystem started task PROC name

SYS2.RTCS.POSZRTCS

RTCS subsystem program library DSNAME

To update the default values, follow these steps:

  1. Update the statements to reflect the actual DSNAMEs and PROCs to be used. 
    The Desktop Installation Assistant establishes the DSNAMEs if it is used to configure the target z/OS image.
  2. If you copy this PROC for use on another z/OS image, update these DD statements. 
    The member OSZ$INIT in the TOSZCNTL target library contains this sample JCL.
  3. Copy the OSZ$INIT member into one of the following locations:
    • SYS1.PROCLIB or another PROCLIB that is available for started tasks which are started by using the Master Subsystem (MSTR).
    • A JES-managed started task PROCLIB.
  4. Sart the RTCS Initiator address space as early as possible in the z/OS IPL process after the security system has been initialized. The following examples describe the command for the RTCS Initiator started task with the PROC member name.

OSZINIT

OSZINIT,SUB=MSTR

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, non-shared RTCS Subsystem 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 STEPLIB DD statement of the RTCS Initiator started task PROC JCL specifies the DSNAME of the RTCS Subsystem program library. This library is used as a 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 the prefix is  xOSZRTCS, the default DSNAMEs of other data sets is constructed from the POSZRTCS DSNAME prefix and their own individual, low-level indexes, for example, xOSZLINK, xOSZHTML, xOSZPSWD, or REGISTRY.


 

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