An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code.
Alternatively:
The code aaa is, if applicable, a 3-digit hexadecimal MVS system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The 4-digit code bbbb, which follows aaa, is a user abend code produced either by CICS or by another product on the user’s system.
If X'offset' contains the value X'FFFF', then module modname was in control at the time of the abend, but the program status word (PSW) was not addressing this module.
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
Or CICS will continue 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.
Look up the MVS code aaa, if there is one, in the relevant MVS codes manual which is detailed in the book list in the front of this manual.
If the modname insert contains the value ????, then CICS was unable to determine which module has abnormally terminated. In this case, examine the system dump to determine which area of code has caused the program check.
The user should examine other messages to determine what the module which issued this message was doing at the time the abend occurred. From these messages they can deduce which product has produced the abend code bbbb. If bbbb is identified as a CICS code, it may be either alphameric or numeric.
If the user abend code is from another product (for example, IMS), refer to the appropriate messages and codes manual to determine the cause of the abend.
The entries in the appropriate manuals will give the user guidance regarding the nature of the error, and may also give some guidance concerning the appropriate user response.
If you want to suppress system dumps that precede ASRA and ASRB abends, you must specify this on an entry in the dump table, using either CEMT or an EXEC CICS command. Further guidance on suppressing system dumps can be found in the CICS® System Definition Guide.
You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHOTxx
XMEOUT Parameters:
applid,
aaa/bbbb,
X'
offset',
modname
The OT domain has received an unexpected error response from some other part of CICS. The operation requested by OT is described by code X'code'.
For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.
A system dump is taken and the system attempts to continue operation unless specifically inhibited by dump table entries.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Investigate the cause of the problem as follows:
If you cannot resolve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHOTDM, DFHOTTR, DFHOTCO, DFHOTSU
XMEOUT Parameters:
applid,
X'
code',
module
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.
Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.
Or CICS will continue unless you have specified in the dump table that CICS should terminate.
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.
This may not be an error as some CICS functions can use a lot of processor time, and this message may have been caused by a long-running function.
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 parameter, which is measured in milliseconds). This means that the module modname will be terminated and CICS will continue.
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 function, 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. You can change the ICVR time interval temporarily online, using the CEMT transaction.
If raising the ICVR time does not solve the problem, you need further assistance from IBM to resolve this problem.
Console
DFHOTRM
XMEOUT Parameters:
applid,
X'offset',
modname
A Java class of the OT domain has detected an unexpected error condition. The description of the error is described in description. The class and method are described in classname and methodname.
For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.
A system dump is taken and the system attempts to continue operation unless specifically inhibited by dump table entries.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Investigate the cause of the problem as follows:
If you cannot resolve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHOTDM, DFHOTTR, DFHOTCO, DFHOTSU, dfhjjts.jar
XMEOUT Parameters:
applid,
description,
classname/methodname
The task with transaction token tran_token has been executing with an inflight OTS transaction for a period of time exceeding its timeout value. An attempt was made to purge the task, but this failed either because the task was protected from being purged at this time, or the transaction definition for tranid specifies SPURGE(NO).
The task continues to execute with no further attempts to purge the task.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Consider making the transaction definition for tranid specify SPURGE(YES). See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHOTIS2
XMEOUT Parameters:
applid,
tranid,
X'
tran_token
'
A system exception was thrown while a GIOP request was being processed by this server. The hostname identifies the server.
The system exception is returned to the client of the GIOP request.
Investigate the cause of the problem as follows:
Also look for II trace points 0132, 0714 and 0201. II 0132 and 0714 trace GIOP requests and replies. If a reply contains a system exception the II 0132 or 0714 is followed by an II 0201 with SYSTEM_EXCEPTION in the trace interpretation.
If you cannot resolve the problem, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
dfhjjts.jar
XMEOUT Parameters:
applid,
hostname
The task with transaction token tran_token has been executing with an inflight OTS transaction for a period of time exceeding its timeout value.
The task is purged.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Investigate why the transaction exceeded the OTSTimeout value specified in the transaction definition. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHOTIS2
XMEOUT Parameters:
applid,
tranid,
X'
tran_token
'