RTCS Generalized Server started task PROC
The following is an example of the RTCS Generalized Server started task PROC. The OSZ$EXEC member in the TOSZCNTL target library contains this sample JCL.
//OSZEXEC PROC KEY=8,P=*,C=*,O=
//*
//OSZEXEC EXEC PGM=OSZEXEC&KEY, Generalized Server execution key
// TIME=1440, No SMF CPU or wait time limits
// REGION=0M, No limits on virtual storage
// PARM=('P=&P', Product or Package to initialize
// 'C=&C', General Server RTCS Context Name
// '&O',) Instance-specific Server options
//*
//*
//OSZEXEC EXEC PGM=OSZEXEC&KEY, Generalized Server execution key
// TIME=1440, No SMF CPU or wait time limits
// REGION=0M, No limits on virtual storage
// PARM=('P=&P', Product or Package to initialize
// 'C=&C', General Server RTCS Context Name
// '&O',) Instance-specific Server options
//*
You can save this member into the following locations:
- A JES-managed started task procedure library that is available to started tasks that are started under the primary JES
- SYS1.PROCLIB or another PROCLIB that is available to started tasks that are started under the Master Subsystem (MSTR)
You can specify the member name of this PROC in the OSZEXEC-PROC option of the RTCS Initialization member of Logical PARMLIB.
If the name of the PROC used to START the RTCS Initiator address space contains the four characters INIT, the default name of the RTCS Generalized Server started task PROC will be the same, except that the characters EXEC will be substituted for the characters INIT in that PROC name.
If you name the started task PROCs as described, you do not update the RTCS Initialization member.
Related topic
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*