Previous Topic: Values You Can Specify for the OPSSTATS SubparameterNext Topic: Generate the Summary Section


JCL PARM Parameters

To simplify the typical batch JCL, all of these subparameters have defaults. Therefore, you may need to specify only the name of the report.

Examples: JCLPARM parameters

The following example shows JCL that requests an Automation Statistics Report that includes all statistics segments. This is true because the SEGMENTS value, which defaults to ALL, is not specified in the JCL.

//STEP1    EXEC PGM=OPAME010,PARM='PARMDD=PARMFILE'
//OPSSMF   DD DISP=SHR,DSN=ops.smflog.dataset.name
//OPSSRM   DD DISP=SHR,DSN=ops.cclxcntl(OPAME000)
//SYSPRINT DD SYSOUT=*
//PARMFILE DD *
OPSSTATS=YES,SMFTYPE=215

The following example shows JCL that requests an Automation Statistics Report that includes only event data for OSF servers and disabled AOF rules. This JCL defines the report further by specifying that only data between the hours of 8:00 a.m. and 5:00 p.m. should be included and that the report should print with a width of 80 characters.

//STEP1    EXEC PGM=OPAME010,PARM='PARMDD=PARMFILE'
//OPSSMF   DD DISP=SHR,DSN=ops.smflog.dataset.name
//SYSPRINT DD SYSOUT=*
//PARMFILE DD *
WIDTH=80,OPSSTATS=YES,
SEGMENTS=(OSFEVENT,AOFEVENT),FROMTIME=(8:00),
TOTIME=(17:00)'

The OPS.CCLXSAMP (OPAMEPRM) provides an example of how to build a REXX EXEC for the parameters, and then have them go to a data set.