Report Samples
This section shows samples of various report sections produced by Abend-AID.
Report Sections
Abend-AID report sections are shown on the pages that follow.
Several sections have standard content regardless of the programming language: the Header, Registers, Trace, File, and Epilog sections. Other sections provide information specific to the programming language and database in use. Only those sections for which information is available at the time of the error are presented in the Abend-AID report. For example, you will not have a Db2 section if the program does not access Db2.
Press Enter to go directly to the Analysis of Error section. You can directly obtain any report section by entering its identification number or name in the SELECT SECTION field. Alternatively, you can use the cursor point-and-shoot method by pressing the Tab key to position the cursor on any highlighted section identification name, and then pressing the Enter key.
Header Section
The Header section, shown in Header section – COBOL, is the first section of the Abend-AID report. This is a standard section that always provides the same type of information. The Header section identifies:
- Date and time of the error
- Job name
- Job number
- Step name
- Operating system release level
- Licensee name and number
- Abend-AID release number.
Other information given in the Header section includes:
- CP FMID
- System on which your program was executing
- DFP release level
- JES2 release level
- CPU model number
Header section – COBOL
Analysis of Error Section
The Analysis of Error section usually provides enough diagnostic information to resolve the problem. The cause of the error and corrective actions are described. The information varies, depending upon the programming language used. For external errors like S813-04, the diagnosis includes:
- Cause of the error
- DDNAME and data set name (whenever possible).
Analysis of Error Section – S813 Example
In the example above, the file name from the DD card did not match the name on the tape label. Abend-AID provides a quick resolution to this problem. Change the JCL and resubmit the job.
Analysis of Error Section – SFCC in Language Environment
In this example, an application program identified in the Header section was compiled with a higher level of LE than was used for execution. Abend-AID identifies the type of fault, SFCA or SFCC, and the problem.
For data-related errors, the Analysis of Error provides:
- Type of error
- Fields in error
- Location (displacement) of the fields within their respective base locator cell number
- Contents of the fields in error
- Description of the error.
For reports with XLS support enabled, you can use the cursor point-and-shoot method to display the Program Listing section by pressing the Tab key to position the cursor at the highlighted text and pressing Enter.
Analysis of Error Section with COBOL XLS
Analysis of Error Section with COBOL Basic Support
Analysis of Error Section with PL/I XLS
Analysis of Error Section with PL/I Basic Support
Analysis of Error Section with Assembler XLS
Analysis of Error Section with Assembler Basic Support
Error Location Section
The Error Location section provides information that can be used to locate the statement in error. Information presented in this section includes:
- Program’s compile date
- Program’s link-edit date
- Program name and module lengths
- Load module name and the load library name
- Location of the last I/O operation or subroutine call, if applicable.
For reports with XLS support enabled, you can use the cursor point-and-shoot method to display the Program Listing section by pressing the Tab key to position the cursor at the highlighted text and pressing Enter.
Error Location Section with COBOL XLS
Error Location Section with COBOL Statement in Error from ABNLLPDS
Error Location Section with COBOL Basic Support
Error Location Section with PL/I XLS
Error Location Section with PL/I Basic Support
Error Location Section with Assembler XLS
Error Location Section with Assembler Basic Support
Trace Section
The Trace section is a standard section that shows you which programs were called and in what order. Also provided in this section are the Application Program Attributes for all application programs in the Call Trace Summary. The Trace section gives the following information:
- Called/linked programs on the save area chain
- Program locations where the calls occurred
- Program in error, when available
- Library that each load module in the Call Trace was loaded from
- Application Program Attributes listing:
- Each program’s name and its load module
- Compile date, length, and language for each program.
For reports with XLS support enabled, you can use the cursor point-and-shoot method to display the Program Listing section by pressing the Tab key to position the cursor at the highlighted values and pressing Enter.
The following figure shows a sample Trace section.
Trace Section
Registers Section
The Registers section is a standard section that displays Supporting Environmental Data, which identifies:
- Abending program status word (PSW) and program PSW
- Entry point (EPA) and load point addresses (LPA)
- Instruction length code (ILC)
- Register contents and descriptions at the time of the error
- Load module name.
Registers Section
Program Storage Section
The Program Storage section formats program storage for application programs on the calling chain.
Program Storage Section with COBOL XLS
Program Storage Section with COBOL Basic Support
Program Storage Section with PL/I XLS
Program Storage Section with PL/I Basic Support
Program Storage Section with Assembler XLS
Program Storage Section with Assembler Basic Support
Program Listing Section
Available only with XLS. The Program Listing Section displays the program source code and identifies the current statement. The current statement in the program in error is either the actual statement in error or the last call. The current statement in any program other than the program in error indicates the last known call in that program.
Program Listing Section with COBOL XLS
Program Listing Section with PL/I XLS
Program Listing Section with Assembler XLS
File Section
The File section is a standard section that provides information for every file open at the time of the error. This section identifies:
- Data Management Control Block information
- DDNAME and data set name
- File statistics
- Current and previous record information, when available
- Other information that is based on the type of file access method used.
The following figure shows a sample File section for an Abend-AID report for a JES2 file.
File Section for a JES2 File
The following figure shows a sample File section for a VSAM file.
File Section for a VSAM File
The following figure shows a sample File section for a QSAM file.
File Section for a QSAM File
The following figure shows a sample File section for an IAM file.
File Section for a IAM File
Db2 Section
See Abend-AID for Db2 for a complete description.
IMS Section
See Abend-AID for IMS for a complete description.
IDMS Section
See Abend-AID for IDMS for a complete description.
Current Sort Record Section
The Current Sort Record section is available only when the program uses an internal COBOL sort. This section identifies:
- Sort fields. For example: SORT FIELDS=(0001,008,ZD,A)
- Record type and record length. For example: Record Type=F,Length=(00080)
- Concatenated sort key
- Current sort record in vertical-hexadecimal format.
The following figure shows a sample Current Sort Record section for a COBOL program.
Current Sort Record Section
Abend-AID for WebSphere MQ Section
Displays either WebSphere MQ batch or WebSphere MQ IMS information created by Abend-AID for WebSphere MQ. For more information about viewing Abend-AID for WebSphere MQ report information, see Understanding WebSphere MQ Diagnostics.
LE Section
Abend-AID collects and interprets the runtime options from LE’s options control block. This information is available from Abend-AID’s Language Environment Selection List.
LE information identifying LE run-time options (OCB)
LE Control Blocks
Abend-AID displays significant control blocks from the LE runtime environment. As an example, the following figure shows the Common Anchor Area.
LE Section – Common Anchor Area
LE Heap Storage
Abend-AID validates and analyzes LE Heap Storage. If damage to the heap storage structure is detected, Abend-AID provides diagnostic information to assist in problem determination and resolution. This includes valuable storage displays to help determine the cause of the original error.
The following figure shows the LE Heap Storage Report section when damage to the heap storage structure is detected.
LE Section – Heap Storage – with errors
The following figure shows the LE Heap Storage Report section when no errors were detected in Heap Storage.
LE Section – no errors
Epilog Section
The Epilog section, at the end of a report, summarizes Abend-AID’s action.
- How the report was printed, if applicable:
- From batch (as a SYSOUT of your JOB)
- From an Abend-AID report data set, identifying name and number.
- The vertical and horizontal hexadecimal translation tables.
- Whether a system dump was printed or suppressed.
- The following warning messages when applicable:
The IBM COBOL Load List for this application appears to be corrupted.
The system save area chain for this application appears to be broken.
The COBOL environment appears to be corrupted.
Working Storage Display was suppressed for one or more CSECTs by CSECTBYP.
CWINCLUD processing was suppressed because the CWINCLUD table is incompatible with this release of Abend-AID. Contact your Abend-AID installer to run JCLINCLD.
The SYSOUT data set at dump capture was not LRECL 133.
Therefore, Abend-AID is in narrow format.
Report Routing Information
- Abend-AID’s memory utilization statistics. Note that the Above, Below, and Total figures refer to the largest amount ever in use for each category. The amounts shown in the Total lines will tend to, but not necessarily, agree with the totals of the Above and Below detail lines.
- How Abend-AID was called.
Epilog Section
Epilog Section with Warning
