An abnormal end (abend) or program check has occurred in module module. This implies that there may be an error in CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.
The code aaa/bbbb is a three digit hexadecimal MVS code (if applicable), followed by a four digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).
Message DFHME0116 is normally produced containing the symptom string for this problem.
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.
Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.
Look up the MVS code, if there is one, in the relevant
MVS codes manual which is detailed in the book list
in the front of this manual.
Next, look up the CICS alphanumeric code in this manual.
This tells you, for example, whether the
error was a program check, an abend, or a runaway,
and may give you some guidance concerning
user response.
If module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.
If you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHTISR, DFHTIDM
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
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 when the error was detected.
Message DFHME0116 is normally produced containing the symptom string for this problem.
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.
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 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 CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTISR, DFHTIDM
XMEOUT Parameters: applid, X'offset', modname
An error has occurred during the running of module modname. The MVS Store Clock facility is the timing mechanism for the operating system.
The code X'code' is the exception trace point id which uniquely identifies the place where the error was detected.
Message DFHME0116 is normally produced containing the symptom string for this problem.
An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues if possible, 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.
If CICS is still running, it is necessary to decide whether to terminate CICS. First, investigate the MVS Store Clock and find out whether it is working properly. If this is the cause, you should take the appropriate action to have it repaired or replaced.
In the unlikely event that this is not a hardware problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTISR, DFHTIDM
XMEOUT Parameters: applid, modname,X'code'