Step 9: Generating a Detail Edit Report for Software Records

Use the following example to generate a set of detail edit and summary reports of all software and operational records:

EXAMPLE JCL	EXPLANATION
`//STEP9 EXEC PGM=IFCEREP1,PARM='CARD'`	Execute IFCEREP1 with the parameters in the SYSIN DD statement, see Table 1.
`//ACCIN DD DSN=EHISTORY,DISP=(OLD,PASS)`	Define the history input data set. EHISTORY is the data set created in Step 1: Creating a History Data Set. Multiple history data sets can be concatenated on this DD statement.
`//DIRECTWK DD UNIT=SYSDA, // SPACE=(CYL,(10,10))`	Define and allocate DASD space for the temporary work data set needed to process history (ACCIN) input records.
`//EREPPT DD SYSOUT=A,DCB=BLKSIZE=133`	Define and allocate space for the output data set that holds the EREP report.
`//TOURIST DD SYSOUT=A,DCB=BLKSIZE=133`	Define and allocate space for the output data set that holds EREP messages and processing information.
`//SYSIN DD DSN=EREP.PARMS(STEP9) // DISP=(OLD,PASS)`	Define the data set containing the EREP parameters needed for this step. The contents of the parameter data set, EREP.PARMS(STEP9), are listed below.
	EREP control statements do not apply to software records, so the EREP.CONTROLS data set is not needed.
`/*`	This delimiter is optional; refer to the JCL manual for your MVS system.

EREP.PARMS(STEP9) contains the following EREP parameters:

EREP PARAMETERS	EXPLANATION
`PRINT=PS`	Request both detail edits and summaries.
`TYPE=SIE`	Select the records by type: S Software (SFT): System abends and other software events I System initialization (IPL): Initial program load E System termination (EOD): End of day and other terminating events
`HIST`	Input records are in the history data set.
`ACC=N`	No history data set generated.
`ENDPARM`	End of parameters. `ENDPARM` must begin on column 1. Parameters may be indented.