//OSZINIT PROC
//*
//* VENDOR_IDENTIFICATION *********************************************
//* *
//* VENDOR: BMC SOFTWARE, INC. *
//* COPYRIGHT: NONE. INTENDED TO BE COPIED TO SYS1.PROCLIB(OSZINIT) *
//* OR ANOTHER MVS MASTER SUBSYSTEM STARTED TASK PROCLIB *
//* OR A PRIMARY OR SECONDARY JES STARTED TASK PROCLIB. *
//* *
//* PRODUCT_IDENTIFICATION ********************************************
//* *
//* PRODUCT_NAME: RTCS COMPONENT_ID: KERNEL *
//* PRODUCT_FMID: ZOSZ310 DIAGNOSIS_PIDS: ZOSZ-310 *
//* CURRENT_RMID: BP00526 LAST_UPDATE: 11/08/23 *
//* *
//* MEMBER_DESCRIPTION ************************************************
//* *
//* MEMBER: OSZINIT (DOCUMENTED PROCEDURE LIBRARY MEMBER NAME) *
//* OSZ$INIT (SMP/E DISTRIBUTION LIBRARY MEMBER NAME) *
//* STATUS: PRODUCT INSTALLATION/CUSTOMER CONFIGURATION MATERIAL *
//* CONTENTS: RTCS INITIATOR ADDRESS SPACE STARTED TASK (STC) *
//* PROCEDURE. THIS PROC IS INTENDED TO BE PLACED INTO *
//* THE MASTER SUBSYSTEM STARTED TASK PROCEDURE LIBRARY *
//* (ANY DATA SET IN THE //IEFPDSI CONCATENATION IN THE *
//* MASTER SCHEDULER JCL, IN 'SYS1.PARMLIB(MSTRJCLnn)'; *
//* IN AN UNMODIFIED SYSTEM THIS WILL BE 'SYS1.PROCLIB'). *
//* IT MAY ALSO BE PLACED INTO ANY JES-MANAGED STARTED *
//* TASK PROCEDURE LIBRARY IF RTCS IS NOT TO BE STARTED *
//* UNDER THE MASTER SUBSYSTEM (SUB=MSTR). BMC SOFTWARE *
//* RECOMMENDS THAT THE RTCS INITIATOR BE STARTED UNDER *
//* THE MASTER SUBSYSTEM BY USING SUB=MSTR ON THE START *
//* COMMAND USED TO INITIATE IT, FOR EXAMPLE: *
//* *
//* START OSZINIT,SUB=MSTR *
//* *
//* BUT, THIS IS NOT REQUIRED. OSZINIT CAN BE STARTED *
//* UNDER THE PRIMARY JOB ENTRY SUBSYSTEM (JES) USING *
//* THE FOLLOWING COMMAND: *
//* *
//* START OSZINIT *
//* *
//* OR, FOR JES2 INSTALLATIONS, THE RTCS INITIATOR CAN *
//* BE STARTED UNDER A SECONDARY JES BY SPECIFYING THE *
//* SSID OF THE SECONDARY JOB ENTRY SUBSYSTEM: *
//* *
//* START OSZINIT,SUB=JESA *
//* *
//* THE RTCS INITIATOR STARTS THE RTCS SUBSYSTEM ADDRESS *
//* SPACE IN THE SAME MANNER THAT IT WAS STARTED. SO, IF *
//* YOU WANT THE RTCS SUBSYSTEM ADDRESS SPACE TO EXECUTE *
//* UNDER THE MASTER SUBSYSTEM (SO YOUR PRIMARY JES CAN *
//* BE SHUTDOWN, BUT LEAVE RTCS RUNNING), THEN YOU START *
//* THE RTCS INITIATOR UNDER THE MASTER SUBSYSTEM, ALSO. *
//* *
//* USAGE_NOTES *******************************************************
//* *
//* This member must be copied into 'SYS1.PROCLIB', or *
//* any other procedure library (PROCLIB) available for *
//* use with started tasks which are started under the *
//* Master (MSTR) Subsystem. If RTCS is to be started *
//* under a Primary or Secondary Job Entry Subsystem, *
//* then this member must be copied to a Started Task *
//* procedure library (PROCLIB) which has been defined *
//* for use by the MVS C/I when converting the JCL of *
//* Started Tasks. *
//* *
//* The RTCS Initiator address space should be started *
//* as early as possible in the MVS IPL process (after *
//* the security system has been initialized, however). *
//* *
//* For example, the following commands could be used: *
//* *
//* o START OSZINIT,SUB=MSTR *
//* o START OSZINIT *
//* *
//* The RTCS Initiator address space is *NOT* the same *
//* address space as the RTCS Subsystem address space. *
//* *
//* The RTCS Subsystem address space is STARTed by the *
//* RTCS Initiator after performing certain validation *
//* procedures on the MVS image, reading initialization *
//* parameters from the indicated member of the Logical *
//* PARMLIB data set, and validating access to the data *
//* sets specified in the initialization parameters. No *
//* DD statements other than STEPLIB are required here. *
//* The DSNAMEs of all other data sets required by the *
//* RTCS Subsystem will default or can be specified in *
//* the initialization parameters in the PARMLIB member. *
//* *
//* If a //PARMLIB DD statement is not included, then *
//* the RTCS Initiator reads the RTCS initialization *
//* parameters from the indicated member of the MVS *
//* Logical PARMLIB data set [concatenation], which *
//* is defined in the LOADxx member of SYSn.IPLPARM *
//* or SYS1.PARMLIB. If not specified, the Logical *
//* PARMLIB concatenation consists of SYS1.PARMLIB, *
//* only. *
//* *
//* If the MVS Logical PARMLIB concatenation cannot be *
//* used to contain the RTCS initialization parameters *
//* then include a //PARMLIB DD statement that defines *
//* the data set(s) containing the RTCS initialization *
//* parameters member(s). Do not specify a member name *
//* in the DSNAME parameter on the DD statement; just *
//* specify the DSNAME (or DSNAMEs if a concatenation). *
//* *
//* The RTCS initialization parameters are read from *
//* member name OSZINI00, by default. To use another *
//* member name, you can specify a different 'OSZINI' *
//* member name suffix using INI=xx, or the complete *
//* member name using MBR=name, in the START command *
//* parameter field (the 4th positional parameter of *
//* the START command operand). For example: *
//* *
//* START Command Member *
//* --------------------------------------- -------- *
//* START OSZINIT,,,(INI=42),SUB=MSTR OSZINI42 *
//* START OSZINIT,,,(MBR=OSZINI42),SUB=MSTR OSZINI42 *
//* START OSZINIT,,,(MBR=OSZPARMS),SUB=MSTR OSZPARMS *
//* *
//* The data sets that are needed by the RTCS Subsystem *
//* are specified in the RTCS initialization parameters. *
//* The initialization parameters and data set names *
//* are passed to the RTCS Subsystem address space by *
//* the RTCS Initiator internally in MVS ECSA storage. *
//* This enables the RTCS Subsystem PROC (by default, *
//* PROC OSZRTCS) to have absolutely no DD statements. *
//* *
//* The RTCS Subsystem address space will dynamically *
//* allocate these data sets, and then unallocate the *
//* program libraries, thus enabling maintenance to be *
//* performed by the customer system programmer using *
//* SMP/E, for example. This is necessary because the *
//* RTCS subsystem address space would normally never *
//* be shutdown (although it is possible to do so). *
//* *
//* The RTCS security domain used by distributed *
//* identity can also be specified on the START *
//* command parameter field. For example: *
//* *
//* Security *
//* START Command Domain *
//* -------------------------------------- -------- *
//* START OSZINIT,,,(SDOM=LPAR1),SUB=MSTR LPAR1 *
//* *
//* For more details on the usage of the security *
//* domain see the SDOMAIN= parameter in the RTCS *
//* initialization member. *
//* *
//* *
//* SUGGESTION: After this PROC has been copied into your PROCLIB, *
//* and has been successfully tested and used to start *
//* the RTCS Initiator, edit it to delete all comments *
//* ('//*' in columns 1-3). Started tasks which start *
//* under the Master Subsystem have ALL of their PROC *
//* JCL copied into SYSLOG, which just causes clutter. *
//* Only the PROC, EXEC, and DD statements are needed. *
//* *
//*********************************************************************
//*
//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=%poszrtcs%
//*
//* PARMLIB: RTCS Initialization Parameter Library (optional)
//*
//* If no //PARMLIB DD, RTCS uses the MVS Logical PARMLIB
//*
//*PARMLIB DD DISP=SHR,DSN=%oszprmlb%