DFHME0004    applid A possible loop has been detected at offset X'offset' in module modname.

Explanation

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which was executing at the time the error was detected.

System action

An exception entry is made in the trace table. A dump is taken, unless you have specifically suppressed dumps in the dump table. This situation may not be an error, or if it is an error it may not be critical, so CICS is not terminated immediately, even if you have specified terminate in the dump table. CICS will purge the runaway task if you have specified this in the SIT.

Message DFHME0116, which contains the symptom string for this problem, is produced.

User response

This error affects message generation, and the message (ME) domain does not automatically terminate CICS. You should decide whether the problem is serious enough to bring CICS down.

Since some transactions can use a lot of CPU time, this message may have been caused by a long-running transaction. Usually, CICS terminates a task which it considers to be a runaway task. It does this termination when the task exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds).

If you have declared ICVR=0, you have to terminate the task yourself if you consider that it has gone into a loop. Purge the task using the CEMT transaction.

If CICS has purged the task and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You will have to bring CICS down at a suitable time in order to do this.

If raising the ICVR time does not solve the problem, you will need further assistance from IBM. See IBM problem support for guidance on how to proceed.

Module

DFHMEDM, DFHMESR, DFHMEME

Destination

Console



DFHME0004.html | Timestamp icon Last updated: Sunday, 4 June 2017