Using the linkage stack to identify the failing module

A linkage stack for a task represents the sequence in which modules and subroutines were called during execution of a task. It provides a valuable insight into the sequence of events up until the time of failure, and it also flags any program or subroutine that was executing when the error was detected.

About this task

After you find which task was in error from the kernel’s task summary (see Finding which tasks are associated with the error), you need to find out which module was in error. If you report a problem to the IBM® Support Center, the information you need to provide includes the module name.

Figure 1 shows a typical kernel linkage stack.

Figure 1. Example of a kernel linkage stack showing a task in error
KE_NUM @STACK   LEN  TYPE ADDRESS  LINK REG OFFSET ERR NAME

0090   2A83F040 01E0 Bot  28F03C00 A8F04230 000630     DFHKETA
0090   2A83F220 03E0 Dom  28F20900 A8F20B76 000276     DFHDSKE
0090   2A83F600 1130 Dom  28F54BC8 A8F56168 0015A0     DFHXMTA
0090   2A840730 0AA0 Dom  296150C8 A9616546 00147E     DFHPGPG
                     Int   +0003CA A96152AE 0001E6     INITIAL_LINK
0090   2A8411D0 0E90 Dom  2998BA00 A9380644 000000 *Y* DFHAPLI1
                     Int   +002B4E A998C77A 000D7A     CICS_INTERFACE
0090   2A842060 06C0 Sub  29380A58 A9381E2E 0013D6     DFHSRP
0090   2A842720 1290 Dom  28FAB880 28FB02CD 004A4D     DFHMEME
                     Int   +003D82 28FABB6A 0002EA     SEND
                     Int   +001840 28FAF6EA 003E6A     CONTINUE_SEND
0090   2A8439B0 06F0 Dom  2906B5B8 A906D0E0 001B28     DFHDUDU
                     Int   +000C6C A906B7CA 000212     SYSTEM_DUMP
                     Int   +001AE6 A906C63E 001086     TAKE_SYSTEM_DUMP

Procedure

  1. Find the task number of the task in error from the KE_NUM column, and use this as an index into the linkage stack entries. These are shown in the dump after the task summary.
  2. When you have found the task number, look at the TYPE column. The TYPE column, as shown in the example, can contain any of the following entries:
    • Bot marks the first entry in the stack.
    • Dom marks a stack entry caused by a domain call.
    • Sub marks a stack entry caused by a subroutine.
    • Lifo marks a stack entry caused by a LIFO module.
    • Int marks a call to an internal procedure identified to the kernel.
  3. The modules and subroutines are shown in the listing in the order in which they were invoked, so the first module you see is at the bottom of the stack, and the second module is next from bottom. You often see DFHKETA and DFHDSKE, respectively, in these two positions.

    The last module or subroutine in the listing is at the top of the stack, and it represents the last call that was made before the dump was taken. Assuming that the system abend caused the dump to be taken, this is likely to be a routine associated with dump domain.

    In the example in Figure 1, program DFHAPLI1 is shown to be in error.

  4. If module DFHAPLI or DFHAPLI1 is flagged as in error, consider first whether an application is the cause of the failure. DFHAPLI is the application language interface program, and it is on the linkage stack whenever an application is being executed. If an application is the cause of the error, it is your responsibility to correct the problem.
  5. If an application is not the cause of the error, or the module flagged in error is not DFHAPLI or DFHAPLI1, report this module name to the IBM Support Center, together with the other information described in Using the PSW to find the offset of the failing instruction.

What to do next

You can sometimes use the technique described in this section to gather the information that the IBM Support Center needs to resolve a CICS® system abend. However, you should normally use the summary information presented in the formatted output for the kernel domain storage areas. This method is valid only if the abend has occurred in a module or subroutine that has a kernel linkage stack entry. This is the case only where the module or subroutine has been invoked by one of the following mechanisms:
  • A kernel domain call
  • A kernel subroutine call
  • A call to an internal procedure identified to the kernel
  • A LIFO call
Routines that have been invoked by assembler language BALR instructions do not have kernel linkage stack entries.


dfhs10z.html | Timestamp icon Last updated: Monday, 5 June 2017