How to allocate and initialize the following datasets for the OPS/MVS Servers started tasks:
Release : All
Component : OPS/MVS
These files are referenced in the OPS/MVS OPSUSS / OPSOSF / OPSECF Service tasks in the following way :
//USSCMIN DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.USSCMIN,
//USSCMOUT DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.USSCMOUT,
//SYSTSPRT DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.USSOUT
//SYSPRINT DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.STDOUT,
//SYSOUT DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.STDERR,
// DCB=(RECFM=V,LRECL=132,BLKSIZE=136,DSORG=PS) ...
2) OPSECF ...
//SYSTSPRT DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.ECFOUT
//SYSTSIN DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.ECFIN,
// DCB=BLKSIZE=128 ...
3) OPSOSF ...
//SYSTSPRT DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.OSFOUT
//SYSTSIN DD SUBSYS=&SSID,DISP=SHR,DSN=SYS1.OPS.OSFIN,
// DCB=(BLKSIZE=6144,LRECL=6144) ...
To better explain how these datasets should be correctly managed, the below notes have been added to the Comments section on top of each of the sample tasks provided in the Target library CCLXCNTL :
...All of the data sets used in this procedure must be cataloged in the master catalog, or must be referenced by VOLSER and UNIT name, so that this PROC can be started by the master subsystem with SUB=MSTR on the START command, when JES is not up.
...The data set names used on the SYSTSIN and SYSTSPRT DD statements do not have to exist. They are there only because SMS requires a DSN to be specified on this type of DD statement. ...
The data set names used on the subsystem datasets do not have to exist. They are supplied to meet SMS requirements for a DSN to specified on a subsystem dataset allocation. ...
These are special datasets in that they are controlled by the subsystem specified by the SUBSYS= parameter on the DD statement. In this case, OPS/MVS controls these input and output datasets for the Servers.
The DCB attributes on the 'IN' DD names control how much data can be passed to these servers.