The next block of information is important if the application has multiple program modules. It lists the calling sequence of programs that resulted in the execution of the program that produced the ABEND.
************************ * MODULE CALL SEQUENCE * ************************ A B C D E F G H LOAD PROGRAM PROGRAM ENTRY COMPILE VER/ MODULE PROGRAM/PROCEDURE ADDRESS LENGTH ADDRESS DATE TIME LANGUAGE REL -------- ---------------------------- -------- ------ -------- -------- ------ --------- ----- SYSTEM 00000000 000000 36300908 ASSEMBLER CALLED CEE CEE 00000000 000000 00000000 ASSEMBLER CALLED CAOEDEMO CAOEDEMO 36300908 004AA8 36300908 14 MAR,2008 16.38.30 COB Z/OS 3.4.1 (ABENDED)
The module call sequence portion displays the following information:
Displays the load module name in which the called program resides.
Displays the name of the called program. For COBOL and Assembler, this is the CSECT name. For PL/I this is the active procedure name.
Displays the storage address of the start of the called program.
Displays the length of the called program.
Displays the storage address of the entry point of the called program.
Displays the date and time of compilation.
Displays the source language in which the called program is coded.
Displays the version of the COBOL or PL/I compiler used for compilation.
Note: The register Save Area Trace portion is at the end of the abend report. If you want to know the actual contents of the registers when control was passed from program to program, see the Save Area Trace.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|