DFHSO0004 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 happened to be executing at the time when the error was detected.
System action
An exception entry is made in the trace table.
A system dump is taken unless you have specifically suppressed the dump (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing continues unless you have specified in the dump table that CICS should terminate.
Message DFHME0116, which contains the symptom string for this problem, is produced.
User response
If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.
Since some CICS functions can use a lot of CPU time, this message may have been caused by a long-running function, and there may not be an error. Usually, CICS purges a CICS function which exceeds the runaway task time interval that you have specified in the ICVR system initialization parameter. This means that execution of module modname is terminated and CICS continues.
If you have specified system initialization parameter ICVR=0 and you consider that module modname is looping, you must terminate CICS in order to terminate the runaway function.
If CICS has terminated module modname, and you consider that it was not a runaway, you should increase the value of the ICVR system initialization parameter. You have to close down CICS at a suitable time to do this permanently. You can change the ICVR time interval temporarily online using the CEMT transaction.
If raising the ICVR time does not solve the problem, you may need further assistance from IBM to resolve the problem. See IBM problem support for guidance on how to proceed.
Module
DFHSOCK, DFHSOSEXMEOUT parameters/Message inserts
- applid
- X'offset'
- modname
Destination
Console