Looking at the evidence

Once you have collected the necessary documentation, use the following guidance to analyze the information you have gathered.

Procedure

  1. Look first at the kernel task summary. The runaway task is flagged “*YES*” in the ERROR column. The status of the task is shown as “***Running**”.
  2. Use the kernel task number for the looping task to find its linkage stack.
    • If a user task is looping, DFHAPLI, a transaction manager program, should be near the top of the stack. You are likely to find other CICS modules at the top of the stack that have been invoked in response to the abend. For example, those associated with taking the dump.
    • If you find any program or subroutine above DFHAPLI that has not been invoked in response to the error, it is possible that CICS code, or the code of another program, has been looping.

Results

If you find that the loop is within CICS code, you need to contact the IBM® Support Center. Make sure you keep the dump, because the Support Center staff need it to investigate the problem.

If the kernel linkage stack entries suggest that the loop is in your user program, you next need to identify the loop.



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