Investigating loops that cause transactions to abend with abend code AICA

If the loop causes a transaction to abend with abend code AICA, it must either be a tight loop or a non-yielding loop. You do not need to find which type you have, although this is likely to be revealed to you when you do your investigation.

About this task

Both a tight loop and a non-yielding loop are characterized by being confined to a single user program. You should know the identity of the transaction to which the program belongs, because it is the transaction that abended with code AICA when the runaway task was detected.

Procedure

  1. Get the documentation you need.
  2. Look at the evidence.
  3. Identify the loop, using information from the trace table and transaction dump.
  4. Determine the reason for the loop.

Results

Use the following information to complete the steps above.


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