The summary section

The summary section contains a list of all events (such as abends and call entries) in chronological order. It is preceded by the heading:
<H1> E V E N T   S U M M A R Y

With each event entry in the list is also provided key information, such as module name, program name, and failing line or statement number. This information is a summary of the information that is provided in the details section for the event.

The following is provided for each entry in the list:
Event #
This section is a unique sequence number in ascending chronological order assigned to the event. The event number is used as reference to the detailed information for the event in the Event Details section of the report.
Event Type
The event type as one of the following:
Abend abend-code
An abend event occurs when system hardware or software terminates a program because it attempted to perform an invalid action, or because a valid action could not be performed for some reason. A system or user abend code generated by the operating system or other software is associated with the abend.

Multiple abends can be associated with a fault because an abend can be "trapped" by software and converted to an abend of another type.

AMODE64->31
An event representing the Language Environment switch from AMODE 64 to AMODE 31.
BALR
A BALR event occurs when control is transferred from one program to another via a branch and link mechanism and information about the status of the first program is not saved in a standard save area by the second program.
Branch
A branch event occurs when the Breaking Event Address Register (BEAR) hardware feature provides relevant information about the instruction that caused a wild branch.
Call
A call event occurs when control is transferred from one program to another via a branch and link mechanism and information about the status of the first program is saved in a standard save area by the second program. With link events, call events show an execution trail through the fault.

Z Abend Investigator reconstructs the call events from the save-area information obtained at the time of the abend. There might be none, one, or many call events associated with each abend event for a fault.

Current PRB
A current Program Request Block (PRB) event.
Debug Tool
A z/OS® Debugger event.
EXEC CICS
A CICS EXEC CICS statement event.
EXEC DLI
A CICS EXEC DLI statement event.
EXEC SQL
A CICS EXEC SQL statement event.
Execute
An EXecute event summarizes the execution of an EX machine instruction that occurred prior to an abend event.
HFZSNAP
An HFZSNAP event.
Interrupt
An Interrupt Request Block (IRB) event.
Java™
A Java event. Usually, a call to a Java method.
LE Condition
An Language Environment® unhandled condition event.
Link
A link event occurs when control transfers from one program to another through a supervisor call mechanism, and information about the status of the first program is saved in a standard save area by the second program. With call events, link events show an execution trail through the fault.

Z Abend Investigator reconstructs the link events from the save area information obtained at the time of the abend. There might be none, one, or many link events associated with each abend event for a fault.

ONCODE code
A PL/I 2.3 non-LE run-time ONCODE event. The ONCODE condition is shown.
PC number
A PC event occurs when a PC (Program Call) instruction is executed that causes control to be transferred to a system service.
SVC number
An SVC event occurs when an SVC instruction (other than a link) is executed that causes control to be transferred from an application program to a system service.

SVC events appear in the analysis when an abend occurs in a system service routine invoked by an application program. There can be at most one SVC event associated with each abend event for a fault.

Fail Point
If the event has been identified as the point of failure, then this identification is indicated by ***** in this column.
Module Name
If available, the name of the load module that is associated with the event. Otherwise, n/a.
Program Name
If available, the name of the program or CSECT that is associated with the event. Otherwise, n/a.
EP Name
If available, the name of the entry point that is associated with the event. Otherwise, n/a.
Event Location
One or more of the following abbreviations might appear in this field:
F#n
Source file number
L#n
Source file line number
S#n
Listing file statement number
M+x
Offset from start of load module
P+x
Offset from start of program
E+x
Offset from start of entry point
Description
The following information is provided:
  • If available, a brief description of the program or load module function.
  • The data set name from where the module was loaded, or LPA if the module was found in LPA, or CSA if the module was found in CSA.

    If the data set name cannot be determined for a module not in LPA or CSA, then Not determined is shown.