Using the DEBUG Parameter

If a problem with your EREP run is associated with an input record, you must be able to look at the record. Use an event history report and include the DEBUG parameter with its option 17 in the EREP controls to see the records used, as shown in the following example:

EVENT
HIST
ACC=N
LINECT=60
DATE=(89040-93365)
DEBUG=(17)

The records in the report will appear one line item at a time with an unformatted hexadecimal dump immediately following each line item. See DEBUG — Debug (Diagnostic Parameter) for coding details.

If you select a print report with DEBUG=(17) a hexadecimal dump of every record that passed filtering appears in the EREP messages file (TOURIST output).

The IBM service representative can help you interpret the records, by referring to the maintenance documentation for the device that generated the record.