Coding Control Statements

Here are some considerations and recommendations to keep in mind when coding control statements:

Several control statements are required for each EREP run.
The same control statements may apply to several EREP runs.
EREP ignores statements that do not apply.
The control statements usually change only when your configuration changes.
Some EREP control statements require considerable preparation.
Putting control statements in a file is preferable to entering the statements in the input data stream.

Each EREP control statement has its own coding rules. Here are a few general coding rules that you must follow:

Using ENDPARM
Control statements cannot be mixed with EREP parameters. If parameters and control statements are in the same file, you must code ENDPARM to indicate the end of parameters before coding any control statements. ENDPARM must begin on column 1.

Entering Control Statements

The following table shows the operating system specific guidelines you must follow.

OP. SYSTEM	EREP CONTROL STATEMENT GUIDELINES
MVS	The EREP control statements must always be entered as SYSIN data. You can enter the control statements as in-stream data. You can put the control statements into a separate file specified by the SYSIN JCL statement. Refer to the SYSIN DD statement description in MVS System Controls and Coding the JCL in the EREP User's Guide for more information and examples.
VM	There are several ways to enter control statements: You can enter CPEREPXA on the command line and supply the parameters and then the control statements in response to its prompting messages. You can put the parameters and control statements in a file that is called as an operand to CPEREPXA. You can use the CMS EXEC &STACK control statement to enter the parameters and then the control statements as in-stream data before coding the CPEREPXA EXEC. Refer to Entering CPEREPXA Operandsin the EREP User's Guide for more information and examples.
VSE	You must always code control statements as in-stream data in the SYSIPT data statement. Refer to Assignments at Initialization in the EREP User's Guide for more information.

Continuing Control Statements
You cannot continue a control statement from one line to the next. However, you can code several control statements by repeating complete statements on new lines in order to convey your information to the EREP program. See the control statement descriptions for more details.
CPU Serial Number Restriction
The combined number of CPUs or system images specified on all of the control statements for an EREP run cannot exceed 16.

Use the SYSIMG statement to expand EREP’s capabilities.

The SYSIMG statement allows EREP to process records from an n-way processor so that those processors operating in the same system image are reported under the CPU serial number. See SYSIMG Control Statement for additional information.