Abend error recording initiated by O/C/EOV

Both the O/C/EOV problem determination and recovery routines trace control blocks and work areas when abnormal termination conditions are encountered in O/C/EOV processing.

The problem determination routines are invoked only when the error is associated with known, describable errors. These errors, called determinate errors, are identified with a system completion code and a return code in register 15. The problem determination routines are not invoked when an indeterminate error (for example, a program check) is encountered.

The O/C/EOV system recovery routines are called by the system recovery/termination manager (R/TM) as a result of the ESTAE macro issued during open, close, or EOV initialization. These recovery routines are called on every abend condition whether determinate or indeterminate.

The problem determination and recovery routines pass information to the Generalized Trace Facility (GTF). The records passed to GTF appear in the abend dump. The records will also be written to the GTF data set under the following conditions: (1) if GTF is active and operating in external mode while the job to be traced is running and (2) if the operator responds TRACE=USR when the GTF message SPECIFY TRACE OPTIONS appears at the console. To correlate these events with other events, you may also want to trace SVCs, I/O events, and others. GTF makes the records available to the ABDUMP routine and writes them to the GTF data set specified by the user. The user must define the data set for the GTF output. For information on how to use GTF, see z/OS MVS Diagnosis: Tools and Service Aidsz/OS MVS Diagnosis: Tools and Service Aidsz/OS MVS Diagnosis: Tools and Service Aids.

GTFTRACE USR(DMA1)

DMA1 is the name GTF uses to identify data put in the data set by O/C/EOV routines.

See z/OS MVS IPCS User's Guide and z/OS MVS IPCS Commands for detailed information on using IPCS.

Recording of abends within O/C/EOV can be controlled by 2 bits at CVTDMSR (X'110' into the CVT).