Start of change

DFHOTxxxx messages

Start of changeDFHOT0001End of change
Start of changeapplid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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.

Note:
The program check may have occurred in a user program. If this is the case, the program check is usually followed by an ASRA or an ASRB transaction abend and a transaction dump.

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.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHOTxxEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeaaa/bbbb,End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changemodnameEnd of change

Start of changeDFHOT0002End of change
Start of changeapplid A severe error (code X'code') has occurred in module module.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

Investigate the cause of the problem as follows:

  1. Determine if the problem can be explained by any previous messages issued from some other CICS component.
  2. Examine the symptom string.
  3. Examine the dump.

If you cannot resolve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHOTDM, DFHOTTR, DFHOTCO, DFHOTSUEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode',End of changeStart of changemoduleEnd of change

Start of changeDFHOT0004End of change
Start of changeapplid A possible loop has been detected at offset X'offset' in module modname.End of change
Start of change
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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHOTRMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'offset', End of changeStart of changemodnameEnd of change

Start of changeDFHOT0101End of change
Start of changeapplid A severe error has occurred. The description is ' description'. The error occurred in class classname/methodname.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

Investigate the cause of the problem as follows:

  1. Determine if the problem can be explained by any previous messages issued from some other CICS component.
  2. Examine the symptom string.
  3. Examine the dump.

If you cannot resolve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHOTDM, DFHOTTR, DFHOTCO, DFHOTSU, dfhjjts.jarEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedescription, End of changeStart of changeclassname/methodnameEnd of change

Start of changeDFHOT0102End of change
Start of changeapplid Task running transaction tranid could not be purged for OTS timeout. Transaction token X'tran_token'End of change
Start of change
Explanation:

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

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

Consider making the transaction definition for tranid specify SPURGE(YES). See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHOTIS2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changetranid,End of changeStart of changeX'End of changeStart of changetran_tokenEnd of changeStart of change'End of change

Start of changeDFHOT0103End of change
Start of changeapplid A system exception has occurred while processing a GIOP request. The server that was processing the request can be identified by the hostname hostname.End of change
Start of change
Explanation:

A system exception was thrown while a GIOP request was being processed by this server. The hostname identifies the server.

End of change
Start of change
System action:

The system exception is returned to the client of the GIOP request.

End of change
Start of change
User response:

Investigate the cause of the problem as follows:

  1. Determine if the problem can be explained by any previous messages issued from some other CICS component. Look especially for DFHEJxxx or DFHIIxxx messages.
  2. If a trace is available look for OT, EJ or II exception trace points.

    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.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changedfhjjts.jarEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changehostnameEnd of change

Start of changeDFHOT0105End of change
Start of changeapplid Task running transaction tranid has been purged as it exceeded its specified OTS timeout. Transaction token X':mv.tran_token:emv.'.End of change
Start of change
Explanation:

The task with transaction token tran_token has been executing with an inflight OTS transaction for a period of time exceeding its timeout value.

End of change
Start of change
System action:

The task is purged.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

Investigate why the transaction exceeded the OTSTimeout value specified in the transaction definition. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHOTIS2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changetranid,End of changeStart of changeX'End of changeStart of changetran_tokenEnd of changeStart of change'End of change

End of change [[ Contents Previous Page | Next Page Index ]]