Example Descriptions

Use the examples in this as models for your EREP runs. The detailed explanations in later sections are provided to help you understand the examples.

The following is an example of job control language (JCL) to execute a series of EREP reports as it would appear in a file without the annotation of the more detailed example provided on s Step 1: Creating a History Data Set through Step 10: Updating a History Tape:

//EREPPRNT JOB ,ESTER,
//  MSGCLASS=T,NOTIFY=C961231,USER=C961231
//*------------------------------------------------------------------*/
//*  STEP0:    COPIES SYS1.LOGREC TO TEMPORARY DATA SET              */
//*------------------------------------------------------------------*/
//S0      EXEC PGM=IFCEREP1,REGION=1024K,
//             PARM='ACC,ZERO=N'
//SERLOG   DD  DISP=(OLD,KEEP),DSN=SYS1.LOGREC
//ACCDEV   DD  DISP=(NEW,PASS),DSN=&ERRDATA;,
//             UNIT=SYSDA,SPACE=(CYL,(2,2)),
//             DCB=(RECFM=VB,BLKSIZE=6144)
//DIRECTWK DD  DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL,(10,10))
//EREPPT   DD  SYSOUT=A,DCB=BLKSIZE=133
//TOURIST  DD  SYSOUT=A,DCB=BLKSIZE=133
//SYSIN    DD  DUMMY
//*
//*------------------------------------------------------------------*/
//*  STEP1:    PRINTS SYSTEM SUMMARY REPORT                          */
//*------------------------------------------------------------------*/
//S1      EXEC PGM=IFCEREP1,REGION=1024K,
//             PARM='HIST,ACC=N,SYSUM'
//ACCIN    DD  DISP=(OLD,PASS),DSN=&ERRDATA;
//DIRECTWK DD  DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL,(10,10))
//EREPPT   DD  SYSOUT=A,DCB=BLKSIZE=133
//TOURIST  DD  SYSOUT=A,DCB=BLKSIZE=133
//SYSIN    DD  DUMMY
//*
//*------------------------------------------------------------------*/
//*  STEP2:    PRINTS SYSTEM EXCEPTION REPORTS                       */
//*------------------------------------------------------------------*/
//S2      EXEC PGM=IFCEREP1,REGION=1024K,
//             PARM='HIST,ACC=N,SYSEXN,TABSIZE=128K'
//ACCIN    DD  DISP=(OLD,PASS),DSN=&ERRDATA;
//DIRECTWK DD  DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL,(10,10))
//EREPPT   DD  SYSOUT=A,DCB=BLKSIZE=133
//TOURIST  DD  SYSOUT=A,DCB=BLKSIZE=133
//SYSIN    DD  DUMMY
//*
//*------------------------------------------------------------------*/
//*  STEP3:    PRINTS SIM DETAIL AND EDIT SUMMARIES                  */
//*------------------------------------------------------------------*/
//S3      EXEC PGM=IFCEREP1,REGION=1024K,
//             PARM='HIST,ACC=N,ZERO=N,PRINT=AL'
//ACCIN    DD  DISP=(OLD,PASS),DSN=&ERRDATA;
//DIRECTWK DD  DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL,(10,10))
//EREPPT   DD  SYSOUT=A,DCB=BLKSIZE=133
//TOURIST  DD  SYSOUT=A,DCB=BLKSIZE=133
//SYSIN    DD  DUMMY
//*
//*------------------------------------------------------------------*/
//*  STEP4:    PRINTS EVENT HISTORY                                  */
//*------------------------------------------------------------------*/
//S4      EXEC PGM=IFCEREP1,REGION=1024K,
//             PARM='HIST,ACC=N,EVENT'
//ACCIN    DD  DISP=(OLD,PASS),DSN=&ERRDATA;
//DIRECTWK DD  DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL,(10,10))
//EREPPT   DD  SYSOUT=A,DCB=BLKSIZE=133
//TOURIST  DD  SYSOUT=A,DCB=BLKSIZE=133
//SYSIN    DD  DUMMY

The JCL in s Step 1: Creating a History Data Set through Step 10: Updating a History Tape is an example of one way to set up an EREP run with several steps.

This is only an example: You must decide which reports are relevant to your installation, in what order they should be generated, and how often they should be run.

Important: Jobs coded to invoke EREP upon receipt of messages indicating that LOGREC is near-full must be coded with the correct message number. An IFB060E is issued when LOGREC is near full on an MVS 4.2 system. An IFB080E is issued when LOGREC is near full on an MVS 5.2 or OS/390 R1 and above system.

Step 1: Creating a History Data Set creates a history data set that is used in the other reports. By creating a history file and then running all the reports against that file, you ensure that all of the reports are using the same set of records.

The parameters and control statements for this example are shown in the data sets listed on the SYSIN (DD) statements. The data sets containing the EREP parameters (EREP.PARMS) are included with each step of the example.

Table 1 shows some of the EREP control statements that could be in the EREP.CONTROLS data set used in each step of the example.

Table 1. Contents of EREP.CONTROLS
EREP CONTROL STATEMENTS	EXPLANATION
`LIMIT 3830,EQUCHK=5,OVRN=10`	To limit the number of records appearing on the reports. The DASD subsystem exception report shows temporary equipment checks and overrun errors for a 3830 control unit only if there are 5 or more equipment checks or 10 or more overruns recorded against the device.
`SHARE=(011111.01BX,022222.02BX)`	Causes the records from DASD drive 0 (device addresses 01B0 and 02B0) to be combined and presented as data for 01B0 on CPU 011111.
Note: The control statements are specific to the installation and the reports requested. EREP Control Statements describes what each of the control statements does. EREP Control Statements in the EREP Reference provides the information to code the control statements.

Parameters and Control Statements describes how to use the EREP parameters and EREP control statements. The EREP parameters and control statements are described in greater detail in in the EREP Reference.