Running EREP in a Multisystem Environment

EREP will invoke formatters for MVS constructs. The formatters invoked are downward compatible. In an environment where different releases of MVS are running, the newest release of those formatters should be invoked by either of the following methods:

Formatting reports under the highest release system.
Using steplib to access the highest levels of formatters in the corresponding SYS1.MIGLIB.

You can combine history data sets as input to EREP by concatenating DD statements for them on the ACCIN statement. You will need to make sure the space allocated for the DIRECTWK data set is large enough to hold all the input records, since EREP copies the records to DIRECTWK before starting its selection processing.

In a multisystem environment, where I/O devices are shared between processor systems, take special care to make sure you get complete and accurate reports about the shared devices.

The following table presents suggested procedures for running EREP in a multisystem environment.

ACTIONS

STEPS AND EXAMPLES

Put all DASDID, LIMIT and SHARE statements into a separate data set.

Specify the data set name on the SYSIN DD statement for:
- System summary
- System exception series
- Threshold summary
- Trends report
- PRINT reports for shared I/O devices
Code the EREP parameters on the EXEC statement; do not use PARM='CARD' in these steps. See Table 1 for an example.

Reorder the EREP job steps shown in the sample EREP job in s Step 1: Creating a History Data Set through Step 10: Updating a History Tape to run the processor and SCP detail reports before the system-level reports.

Create a history data set without requesting a report.
Run MCH and CCH detail edit reports.
Run software detail edit reports.
Run detail edit reports for dedicated I/O devices (for example, 2305).
Run event history against the working data set.
Concatenate the history data sets from each system on the ACCIN DD statement, then run the following reports:
1. System summary
2. System exception
3. Detail edit reports for shared I/O devices
Add the records from the concatenated data sets to an existing permanent history data set.

Note: You may not want to run all of these reports every time.

Recommendations:

Develop a technique to make sure that each system’s ERDS has been copied before the first step that uses concatenated input runs. For example, include a step that creates a named data set, then test for that data set before requesting the first system-level report.
Install this procedure on each system in the complex, so reports can be run from any one of them at any time.