Finding Fortran information in a Language Environment dump

To locate Fortran-specific information in a Language Environment dump, you must understand how to use the traceback section and the section in the symbol table dump showing parameters and variables. Figure 1 shows an example of a Fortran dump; Table 1 provides additional information about each section within the dump.

Figure 1. Sections of the Language Environment dump
CEE3DMP V1 R3.0: Condition processing resulted in the unhandled condition.         08/30/01 10:32:56 AM                 Page:    1

Information for enclave SAMPLE

  Information for thread 8000000000000000
[1]
  Traceback:
    DSA Addr  Program Unit  PU Addr   PU Offset  Entry         E Addr    E  Offset   Statement  Load Mod  Service  Status
    0002D018  CEEHDSP       05936760  +0000277C  CEEHDSP       05936760  +0000277C              CEEPLPKA           Call
    0002F018  AFHCSGLE      059DF718  +000001A8  AFHCSGLE      059DF718  +000001A8              AFHPRNAG           Exception
    05A44060  AFHOOPNR      05A11638  +00001EDE  AFHOOPNR      05A11638  +00001EDE              AFHPRNAG           Call
    05900A90  SAMPLE        059009A8  +0000021C  SAMPLE        059009A8  +0000021C       6_ISN  GO                 Call

[2]
  Condition Information for Active Routines
    Condition Information for AFHCSGLE (DSA address 0002F018)
      CIB Address: 0002D468
      Current Condition:
        FOR1916S The OPEN statement for unit 999 failed. The unit number was either less than 0 or greater than 99, the highest
unit number allowed at your installation.
      Location:
        Program Unit: AFHCSGLE Entry: AFHCSGLE Statement:  Offset: +000001A8
    Storage dump near condition, beginning at location: 059DF8B0
      +000000 059DF8B0  5060D198 5880C2B8 58F0801C 4110D190  05EFD502 D3019751 4770A1F0 4820D2FE  |&-Jq..B..0....J...N.L.p....0..K.|

  Parameters, Registers, and Variables for Active Routines:
    CEEHDSP (DSA address 0002D018):
      Saved Registers:
        GPR0..... 000003E7  GPR1..... 0002D3B4  GPR2..... 0002DFD7  GPR3..... 0002E027
        GPR4..... 0002DF94  GPR5..... 00000000  GPR6..... 00000004  GPR7..... 00000000
        GPR8..... 0002E017  GPR9..... 0593875E  GPR10.... 0593775F  GPR11.... 85936760
        GPR12.... 00014770  GPR13.... 0002D018  GPR14.... 800250DE  GPR15.... 85949C70

  GPREG STORAGE:
    Storage around GPR0 (000003E7)
      -000020 000003C7  Inaccessible storage.
      +000000 000003E7  Inaccessible storage.
      +000020 00000407  Inaccessible storage.
    Storage around GPR1 (0002D3B4)
      -000020 0002D394  00000006 00000000 0002E017 0593875E  0593775F 85936760 00014770 00000000  |.............lg;.l.¬el.-........|
      +000000 0002D3B4  0002DFD7 0002E027 0002DF94 0002DF94  0002DDF4 0002DEC4 0002E158 0002D018  |...P.......m...m...4...D........|
      +000020 0002D3D4  0002D468 00000000 00000000 00000007  859D67E0 00000000 00000000 05914848  |..M.............e............j..|
   ⋮
[3]
      Local Variables:
          ABC              CHARACTER*3      123
          J                INTEGER*4                444

[4]
  File Status and Attributes:
    The total number of units defined is 100.
    The default unit for the PUNCH statement is 7.
    The default unit for the Fortran error messages is 6.
    The default unit for formatted sequential output is 6.
    The default unit for formatted sequential input is 5.

Table 1 describes the sections shown in the sample dump in Figure 1 .

Table 1. Understanding the Language Environment traceback table
Section Contents
[1] The traceback section of the dump contains condition information about your routine and information about the statement number and address where the exception occurred. The traceback section helps you locate where an error occurred in your program. The information in this section begins with the most recent program unit and ends with the first program unit.
[2] The condition information section contains information for the active routines. It indicates the program message, program unit name, the statement number, and the offset within the program unit where the error occurred.
[3] The local variable section contains information on all variables and arrays in each program unit in the save area chain, including the program that caused the dump to be invoked. The output shows variable items (one line only) and array (more than one line) items. Use the local variable section of the dump to identify the variable name, type, and value at the time the dump was called. Variable and array items can contain either character or noncharacter data, but not both.
[4] The file status and attribute section of the dump displays the total number of units defined, the default units for error messages, and the default unit numbers for formatted input or formatted output.