DFHST0004    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.

Note that no applid is included for DFHSTUP modules.

System action

An exception entry is made in the trace table.

For modules DFHSTST and DFHSTTI, a system dump is taken and the collection interval is set to 24 hours. Message DFHST0101 will also be issued.

For module DFHSTDM, the action depends on the initialization error action value which is used by the domain (DM) manager. The usual action will be to terminate CICS with a dump.

For module DFHSTUE, processing continues.

For modules DFHSTWR, DFHSTRD, and DFHSTUx (modules within DFHSTUP), the job step is terminated with a dump.

For ALL modules, a system dump is taken, unless you have specifically suppressed dumps in the dump table.

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

User response

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 CPU 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 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 will 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.

Module

DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE, DFHSTUx (Modules within DFHSTUP), DFHSTWR, DFHSTRD

XMEOUT parameters/Message inserts

  1. applid
  2. X'offset'
  3. modname

Destination

Console



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