Starting RTCS
RTCS should be started as soon as possible during the IPL of a z/OS image. RTCS should be started either prior to or concurrently with the primary JES. RTCS does not use any JES services.
The RTCS subsystem must be available for products to execute. If the RTCS kernel has not been loaded and initialized, products that use RTCS services usually terminate abnormally (abend) during their initialization process. Products that use the RTCS Generalized Server (program OSZEXEC[n]) to obtain control in the proper execution key abend immediately, even before any product code is loaded. This action alerts you that the RTCS facilities are not available for the involved z/OS image.
To ensure that products will function properly, BMC recommends starting RTCS after the external security manager (ESM) has been started and successfully initialized. If you have a valid reason to start RTCS prior to ESM initialization, ensure that the ESM or your automation facility issues the following command after the ESM has completed initialization:
F RTCS,REFRESH,SECURITY
In the preceding command, RTCS represents the SSID of the RTCS subsystem.
Start RTCS by using the z/OS START command to initiate the RTCS Initiator address space. The actual START command depends on the member name of the RTCS Initiator started task PROC (usually located in SYS1.PROCLIB, but can be in a JES-managed started task PROCLIB) that was selected during z/OS image configuration.
For example, if the member name OSZINIT is selected and the OSZINIT PROC JCL has been properly customized to specify the correct POSZRTCS DSNAME to be used by RTCS, one of the following z/OS START commands is used to start the RTCS Initiator address space:
The RTCS Initiator performs the following tasks before internally starting the RTCS subsystem address space:
- Reads and processes the RTCS Initialization member from the Logical PARMLIB data set
- Determines and validates the DSNAMEs of the production data sets to be used by the RTCS subsystem and the Generalized Server address spaces
A series of messages is issued to SYSLOG. The following figure provides an example of a subset of the messages.
RTCS subsystem messages
OSZ0069I //TASKLIB DD DISP=SHR,DSN=SYS1.RTCS.POSZRTCS
OSZ0001I RTCS SUBSYSTEM INITIALIZATION IN PROGRESS
OSZ0005I RTCS SUBSYSTEM PC SERVICES NOW AVAILABLE
OSZ0029I OBJECT MANAGEMENT SERVICES NOW AVAILABLE
OSZ0143I NONBACKED DATA SPACE ACCESSED USING DSP BY RTCS REGISTRY 246
DATA SPACE CREATED AND INITIALIZED AND IS UNAVAILABLE FOR XCF SHARING
DSNAME=RTCS.SUBSYS.MEMORY.REGISTRY.NOSHARE.RTZ2
VOL=SER= DDNAME= SCOPE=GLOBAL,EXCLUSIVE RS_TCB=006E5400
ALET=01FF0019/000000740000000B TRACE=00000000/133C5000 DS_TCB=**NONE**
OSZ0022I RTCS SUBSYSTEM MEMORY REGISTRY IS NOW AVAILABLE
OSZ0069I //SYS00001 DD DISP=OLD,DSN=SYS1.RTCS.REGISTRY
OSZ0147I SYS00001 ALET=01FF001A DIV SERVICES ATTACHED TCB=006E4C58 251
BATCH UPDATE WINDOW: 000001 SEC 000006 SEC 000060 SEC, LIMIT: 4000
CURRENT VALUE: 000060 SEC (DIV SAVE NOT PENDING) COUNT: 0000
DIV SERVICES IS ONLY UPDATER WAITERS QUEUE CONTAINS NO TASKS
OSZ0149I SYS00001 ALET=01FF001A DIV SAVE CPU=00.0216 ELAP=03.5958
OSZ0143I VSAM LINEAR DATA SET ACCESSED USING DIV BY RTCS REGISTRY 253
HAS BEEN OPENED FOR UPDATE ACCESS, AND IS EXPOSED FOR XCF CONNECTIONS
DSNAME=SYS1.RTCS.REGISTRY
VOL=SER=XXXXXX DDNAME=SYS00001 SCOPE=GLOBAL,SHARED RS_TCB=006E51D0
ALET=01FF001A/000000740000000B TRACE=00000000/12F75000 DS_TCB=006E4C58
OSZ0079I RTCS SUBSYSTEM SYSTEM REGISTRY IS NOW AVAILABLE
OSZ0432I SECURITY ESMTYPE(RACF) SELECTED BY ESMTYPE(AUTO)
OSZ0443I RTCS SECURITY - SAFSUBSYS(&SSID ) APPLID(&PRODUCT)
OSZ0444I UNDEFINEDUSERINHERIT(ACCEPT) UNDEFINEDUSERSIGNON(REJECT)
OSZ0445I GROUPINHERIT(ALWAYS) DEFAULTUSERID(<blanks>)
OSZ0446I SECTRACE(NONE ) TESTMODE(0A)
OSZ0447I ESM(RACF) RCVT ID(RCVT) VRMN(7730) FLGS(033D0800000000FFF080)
OSZ1083I RTCS LICENSE MANAGER ACTIVE
OSZ0039I CONSOLE COMMAND INTERFACE AVAILABLE FOR OSZRTCS CSCB=RTCS
OSZ0030I RTCS SUBSYSTEM (RTCS) IS NOW AVAILABLE ASID=001D OSZA=13175000
OSZX=13176400 ASVT=025DE040