An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.
The code abcode is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-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).
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.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.
If there is an MVS code, look it up 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
DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM
XMEOUT Parameters: applid, abcode,X'offset', modname
An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected. For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.
An exception entry (code 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 will continue 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 will be issued
to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Inform the system programmer. This indicates a possible error in CICS code. The severity of its impact will depend on the importance of the function being executed at the time of the error.
CICS may not have been terminated.
If the message occurs once and 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 the message recurs or 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
DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM
XMEOUT Parameters: applid, X'code',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 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.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Notify the system programmer. If CICS has not been terminated, it will be 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 will purge 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 will be terminated and CICS will continue.
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 will 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
DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM
XMEOUT Parameters: applid, X'offset', modname
An MVS GETMAIN was issued by module modname, but
there was insufficient storage available to satisfy the
request.
The code X'code' is the exception trace point id
which uniquely identifies the place where the error was detected.
This error has occurred above the 16M line.
The code mvscode is the MVS GETMAIN return code.
An exception entry is made in the trace table (code code in the message). A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS will continue 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 is normally produced containing the symptom string for this problem.
Inform the system programmer. If CICS has been terminated by another module, look out for the relevant termination messages (from, for example, the domain manager), and look up the user response suggested for these messages.
If CICS is still running, the problem may be a temporary one which will right itself if more storage becomes available. If you can manage without module modname, you may decide to continue and bring CICS down at a convenient time to resolve the problem. If the message recurs or if you cannot run without the full use of all CICS modules, you should bring CICS down in a controlled shutdown.
Try decreasing the overall size limits of the DSAs or EDSAs. Or, try increasing the size of the whole region, if it is not already at maximum size. If CICS is not already terminated, you will need to bring CICS down to do this. See the CICS System Definition Guide or the CICS Performance Guide for further information on CICS storage.
Console
DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM
XMEOUT Parameters: applid, X'code',modname, mvscode