DFHXS0004.html |
Last updated: Thursday, 27 June 2019A 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.
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.
Message DFHME0116, which contains the symptom string for this problem, is produced.
Notify the system programmer. 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 processor time, this message may have been caused by a long-running function. So there may not be an error here. Usually, CICS purges a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds). This means that module modname in the message is terminated and CICS continues.
But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you have to 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 ICVR time interval in the SIT. You have to bring CICS down at a suitable time to do this permanently. But you can change the ICVR time interval temporarily online, using the CEMT transaction.
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.
Console
Last updated: Thursday, 27 June 2019