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 an EXEC to run a system summary report, a system exception report, and a detail edit report as it would appear in a file without the annotation of the more detailed example provided in s Step 1: Creating a History File through Step 10: Updating the History Tape:

GLOBAL TXTLIB ERPTFLIB EREPLIB
************************************************************************
*  DEFINE INPUT/OUTPUT FILES AND RUN SYSTEM SUMMARY REPORT.
************************************************************************
FILEDEF ACCIN DISK IR22987 DUMREC01 A
FILEDEF ACCDEV DISK EHISTORY DAILY A
FILEDEF TOURIST DISK TOURIST SYSUM A
FILEDEF EREPPT DISK REPORT SYSUM A
CPEREPXA PARMFILE SYSUM A
************************************************************************
*  DEFINE OUTPUT FILES AND RUN SYSTEM EXCEPTION REPORT.
************************************************************************
FILEDEF TOURIST DISK TOURIST SYSEXN A
FILEDEF EREPPT DISK REPORT SYSEXN A
CPEREPXA PARMFILE SYSEXN A
************************************************************************
*  DEFINE OUTPUT FILES AND RUN DETAIL EDIT REPORT.
************************************************************************
FILEDEF TOURIST DISK TOURIST PRINTPS A
FILEDEF EREPPT DISK REPORT PRINTPS A
CPEREPXA PARMFILE PRINTPS A

Important: CPEREPXA is the current version of CPEREP.

The EREP run shown in s Step 1: Creating a History File through Step 10: Updating the History Tape is presented as steps in an EXEC with multiple executions of the CPEREPXA EXEC using different sets of operands. The operands in the examples have been put in files named on each CPEREPXA EXEC. The contents of the files are included in each step of the example.

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.

The first step of the EXEC defines the input and output files needed for EREP and creates a history file to use in the steps that follow. EREP automatically sends its output to the devices named on the EREPPT and TOURIST file definition statements. The execution of the CPEREPXA EXEC includes the writing and routing of the output.

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.