MVS systems require system controls that create the interface between EREP and the operating system’s data management functions. You provide these system controls as part of the EREP run, as follows:

//JOB statement

Required; initiates the job.

//EXEC statement

Required; executes the EREP program.

The following table shows where to find information about the coding options for the EREP parameters on the EXEC statement:

TO CODE THE PARAMETERS	SEE
As in-stream data	Table 1 and the SYSIN DD statement in MVS System Controls
Or on the JCL EXEC statement	Table 1

Important: The EXEC statement is one place to request more storage to accommodate EREP using the REGION parameter. See Increasing Region Size for more information.

//ACCIN DD statement

Optional; defines the history input data set.

Important: ACCIN file MUST have been created from an EREP ACC=Y statement. Files built with system utilities may cause unpredictable results.

The history input can be in more than one data set. You can concatenate the DD statements, making sure the record formats (RECFM) are either blocked or unblocked but not both.

The data set with the largest blocksize must be first in the concatenation, so that the system allocates a device suitable for all the data sets.

You may use the ERDS or a history data set for input. Table 1 shows some ways to combine input from ERDS and

See Data Control Block (DCB) Requirements for information about the DCB requirements.

//DIRECTWK DD statement

Optional; defines and allocates DASD space for the temporary work data set needed to process history (ACCIN) input records.

//SERLOG DD statement

Optional; defines the system error recording data set (ERDS) as the input data set. (The default name of the ERDS is SYS1.LOGREC; but for MVS release 5.1 and later, it can be installation modified.)

Note: The SERLOG statement only defines the ERDS. You cannot use the SERLOG statement to define a data set copied from the ERDS.

When you include history data sets as input for your report you must define them on the ACCIN statement. Table 1 shows some ways to combine input from ERDS and history data sets.

Table 1. How to Define Inputs to EREP

WHEN INPUT IS	PARAMETER REQUIRED	DD REQUIRED
Only ERDS	Neither HIST nor MERGE	SERLOG
Only History files	HIST, not MERGE	ACCIN
Both History and ERDS	MERGE, not HIST	ACCIN and SERLOG

See Information about the ERDS for information about the ERDS processing.

//ACCDEV DD statement

Optional; defines and allocates space for the output history data set. You need this statement if you want EREP to accumulate the records to an output data set after completing the report.

The following is an example of the ACCDEV statement:

//ACCDEV   DD  DSN=C961231.EREP.OUTPUT.DATA,DCB=(BLKSIZE=6000,
//         RECFM=VB),UNIT=SYSDA,DISP=(NEW,CATLG),
//         SPACE=(CYL,(50,10),RLSE)

See Data Control Block (DCB) Requirements for information about the DCB requirements.

//EREPPT DD statement

Optional; defines and allocates space for the output data set that holds the EREP report.

You must code this DD statement whenever you request a report. The blksize should be a multiple of 133 for a 132 character line length. See SYSOUT in the examples in Table 1. You may view the report at a terminal by specifying the SYSOUT class for online display.

The following example shows how to define this data set:

//EREPPT   DD  DSN=C961231.EREP.EREPPT30,DCB=(BLKSIZE=13300,
//         RECFM=FBM,LRECL=133),UNIT=SYSDA,
//         SPACE=(CYL,10,,),DISP=(NEW,CATLG)

See examples in Table 1.

//TOURIST DD statement

Required; defines and allocates space for the output data set that holds EREP messages and processing information.

The blksize should be a multiple of 133 for a 132 character line length. See SYSOUT in the examples in Table 1. You can send the TOURIST output to the SYSOUT class, let it default to the message class for the job, or spool it to a JES device.

//SYSIN DD statement

Required; defines the data set you use to enter EREP controls as in-stream data.

You must supply a SYSIN DD statement as follows:

• You can include EREP parameters, if you code PARM='CARD' on the EXEC statement. The parameters must precede the control statements with ENDPARM separating them. See Table 1 for more detailed information.
• You must code EREP control statements as SYSIN data.
• You must use a dummy statement when you have no control statements or parameters to enter. Code it as:

  //SYSIN DD DUMMY

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.