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 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).
An exception entry is made in the trace table.
For module DFHDUDT, a system dump is taken unless you have specifically suppressed the dumps (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing continues unless you have specified in the dump table that CICS should terminate.
For module DFHDUTM, a system dump is taken. This dump cannot be suppressed. CICS processing continues.
For module DFHDUDU, a system dump cannot be taken as doing so could cause CICS to loop. CICS processing continues.
For other modules, a system dump is taken.
CICS processing continues.
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.
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.
Then look up the CICS alphanumeric code in this manual. This tells you, for example, whether the error was a program check, an abend, a runaway or a recovery percolation, 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.
If the abend occurred in modules DFHDUDT or DFHDUTM, the dump table is not available. Therefore, any EXEC API commands relating to dump codes fail and any dumps taken are processed using default information (for example, whether to terminate CICS or not) rather than information you may have put on the dump table for specific dump codes.
You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHDUDT, DFHDUTM, DFHDUDU, DFHDUXD, DFHDUIO, DFHDUSU, DFHDUXW, DFHPCXDF, DFHSAXDF, DFHDLXDF, DFHXDXDF, DFHXRXDF, DFHTCXDF, DFHTRXDF, DFHFCXDF
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
An error has been detected in module modname. The code 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.
For module DFHDUDT, a system dump is taken unless you have specifically suppressed the dumps (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing continues unless you've specified in the dump table that CICS should terminate.
For module DFHDUTM, a system dump is taken. This dump cannot be suppressed. CICS processing continues.
If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller. 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.
If the error occurred in modules DFHDUDT or DFHDUTM, the dump table may not be available. Therefore, any EXEC API commands relating to dump codes may fail and any dumps taken may be processed using default information (for example, whether to terminate CICS or not) rather than information you may have put on the dump table for specific dump codes.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHDUDT, DFHDUTM
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 happened to be executing at the time when the error was detected.
An exception entry is made in the trace table.
For module DFHDUDT, a system dump is taken unless you have specifically suppressed the dumps (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing continues unless you have specified in the dump table that CICS should terminate.
For module DFHDUTM, a system dump is taken. This dump cannot be suppressed. CICS processing continues.
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 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, 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
DFHDUDT, DFHDUTM, DFHDUXD, DFHDUIO, DFHDUSU, DFHDUXW, DFHPCXDF, DFHSAXDF, DFHDLXDF, DFHXDXDF, DFHXRXDF, DFHTCXDF, DFHTRXDF, DFHFCXDF
XMEOUT Parameters: applid, X'offset', modname
An MVS GETMAIN was issued 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) and a system dump is taken. This dump cannot be suppressed. CICS processing continues.
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.
As the problem is in module DFHDUTM, EXEC API commands for browsing the dump tables may not work, or additions to the dump tables may not work.
You can get diagnostic information about the MVS return code by consulting the relevant MVS codes manual which is listed in the book list at the front of this book.
Try decreasing the size limit 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 need to bring CICS down to do this.
Console
DFHDUTM
CICS could not locate module DFHDUIO during initialization.
An exception trace entry is produced, and CICS continues with the transaction dump facility inoperative.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the exception trace entry and any other relevant messages to determine why module DFHDUIO was not available.
Console
DFHDUDM
XMEOUT Parameter: applid
A dump domain has failed to initialize.
CICS terminates.
An exception trace and a kernel dump are issued by the dump domain. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHDUDU
XMEOUT Parameter: applid
An error, possibly signalled by a previous message, has caused a call to the CICS dump (DU) domain. Dump domain will issue this message immediately before calling the MVS SDUMP facility if the following conditions are satisfied:
The dump code dumpcode is an 8-character system dump code identifying the CICS problem. However some of these characters may be blanks. A system dump code is a CICS message number with the DFH prefix removed.
The dumpid dumpid is the unique 9-character string identifying this dump.
When the dump is complete, message number DFHDU0202 is issued.
Inform the system programmer, who should refer to the CICS message indicated by dumpcode to resolve the problem.
Console
DFHDUDU
This message is issued on successful completion of an SDUMP.
Processing continues unless a CICS shutdown is requested by either the dump table entry for this dump or the dump call to the dump (DU) domain.
Print off the system dump if required. A previous MVS message identifies in which SYS1.DUMP data set this dump can be found.
Console
DFHDUDU
A CICS transaction has abnormally terminated, possibly signalled by a previous message, and the CICS dump (DU) domain has taken a transaction dump.
The dump code dumpcode is normally the 4-character CICS transaction abend code if the dump was requested as a result of a transaction abend. It may also be the value of the DUMPCODE operand on an EXEC CICS DUMP TRANSACTION request.
The dump ID dumpid is the unique 9-character string identifying this dump
A transaction dump is written to the current CICS dump data set, either DFHDMPA or DFHDMPB.
CICS may terminate if the dump table entry for the specified abend code specifically requests it.
Print off the transaction dump if required.
CDUL
DFHDUDU
XMEOUT Parameters: date, time,applid, dumpcode, dumpid
An error, possibly signalled by a previous message, has caused a call to the CICS (DU) dump domain, which failed to take a system dump for reason reason. Reason reason indicates what has caused dump suppression.
The dump code dumpcode is an 8-character system dump code identifying the CICS problem. However some of these characters may be blanks. A system dump code is a CICS message number with the DFH prefix removed.
A system dump is not produced. However, CICS is terminated if the dump table entry for this dump code or the caller of the dump domain requests CICS termination.
If a system dump is required for this dump code, perform the user action appropriate to the reason reason given in the message.
The SIT DUMP option can be over-ridden by using CEMT or the system programming interface for SET SYSTEM DUMPING (NOSYSDUMP|SYSDUMP).
Console
DFHDUDU
A CICS transaction has abnormally terminated, possibly signalled by a previous message, and the CICS dump (DU) domain has failed to take a transaction dump for the reason reason. Reasons reason indicates the reason for dump suppression.
The dump code dumpcode is the 4-character CICS transaction abend code.
A transaction dump is not produced. However, CICS is terminated if the dump table entry for this dump code or the caller of the dump domain specifically requests such.
If a transaction dump is required for this dump code, perform the user action appropriate to the reason reason given in the message.
CDUL
DFHDUDU
XMEOUT Parameters: date, time,applid, dumpcode, reason
Either an EXEC CICS DUMP TRANSACTION DUMPCODE command has been issued, or a CICS transaction has abnormally terminated, possibly signalled by a previous message, and the CICS dump (DU) domain has failed to take a transaction dump nor a system dump for reason reason. Reasons reason indicates what caused dump suppression.
The dump code dumpcode is the 4-character CICS transaction abend code.
Neither a transaction nor a system dump is produced. However, CICS is terminated if the dump table entry for this dump code or the caller of the dump domain makes such a request.
If a transaction dump and/or a system dump is required for this dump code, perform the user action appropriate to the reason reason given in the message:
CDUL
DFHDUDU
XMEOUT Parameters: date, time,applid, dumpcode, reason
At the time of the MVS SDUMP request issued by CICS, another address space in the same MVS system was in the process of taking an SDUMP. This caused MVS to reject the new request. A non-zero value for the DURETRY parameter on the SIT means that CICS is waiting for five seconds before reissuing the SDUMP request.
CICS issues an MVS STIMERM macro which caused CICS to stop for five seconds. The request is reissued when the delay interval has expired. CICS will delay and retry every five seconds for a total time equal to the number of seconds specified on the DURETRY SIT parameter.
None.
Console
DFHDUDU
At the time of the MVS SDUMP request issued by CICS, another address space in the same MVS system was in the process of taking an SDUMP. This caused MVS to reject the new request. CICS has waited for five seconds (as indicated by message DFHDU0208) and is now about to reissue the SDUMP request.
CICS reissues the SDUMP request.
None.
Console
DFHDUDU
An MVS SDUMPX request from CICS signalled by message DFHDU0201 has failed to complete successfully. The possible reasons, (reason) for the failure are as follows:
CICS proceeds as if the dump had been successful.
The user response depends on the reason, (reason), for the failure.
Console
DFHDUDU
Because of a severe system error, the XDUREQ user exit (which allows you to suppress system dumps) has not been called for system dump dumpcode.
The XDUREQ user exit is not called.
DFHDU0211 is followed either by message DFHDU0201, indicating that dump dumpcode was taken, or by message DFHDU0205, indicating that dump dumpcode was suppressed. Message DFHDU0201 or DFHDU0205 is followed by message DFHDU0309 if CICS terminates.
The XDUREQ user exit is called for subsequent system dumps.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHDUDU
A requested transaction dump code has unprintable characters, or has leading or imbedded blanks.
A transaction dump is produced unless suppressed by the user exit XDUREQ. However, no dump statistics are committed. The transaction dump is complete when message DFHDU0203 is issued. The invalid dump code is shown in dump domain (DU) trace points X'0600' and X'0601'.
Print off the transaction dump and determine how an abend or EXEC CICS request was issued with an invalid dump code.
Console
DFHDUDU
XMEOUT Parameters: applid, dumpcode
A remote MVS SDUMPX request from CICS has failed to complete successfully. The possible reasons, (reason) for the failure are as follows:
Alternatively, unexpected data has been input, or storage has been overwritten.
CICS adds diagnostic data to the MVS SDWA and makes an entry in SYS1.LOGREC.
CICS proceeds as if the dump had been successful.
The user response depends on the reason, (reason), for the failure.
If you do get this reason, there was probably an error during CICS initialization.
Notify the system programmer.
You will need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the IWMWQWRK return code and reason.
See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the IWMWQWRK return code and reason.
Notify the system programmer.
To resolve the problem, collect any data from SYS1.LOGREC, any dumps and any relevant messages. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHDUMPX
DFHDUMPX is called under the MVS IEASDUMP.QUERY exit and determines whether a remote dump should be taken.
DFHDUMPX issues this message immediately before returning to MVS if the following conditions are satisfied:
Processing continues.
None.
Console
DFHDUMPX
DFHDUMPX is called under the MVS IEASDUMP.QUERY exit and determines whether a remote dump should be taken.
DFHDUMPX issues this message immediately before returning to MVS if it has found that a remote dump should be suppressed.
The remote dump is suppressed under the following conditions :
The remote dump is also suppressed if an error occurred during the DFHDUMPX processing. Look for a previous DFHDU0213 message to find the reason for the error.
Processing continues.
To determine whether action is necessary refer to any DFHDU0213 message preceding this one.
Console
DFHDUMPX
DFHDUMPX is called under the MVS IEASDUMP.QUERY exit and determines whether a remote dump should be taken.
DFHDUMPX issues this message if it has found that the SDUMPX PROBDESC parameters do not contain CICS data. It is probable that this is not an error and that the remote dump was requested by a product other than CICS. However, if you were expecting a CICS remote dump it could be that the PROBDESC parameters were accidentally overwritten.
DFHDUMPX will request that MVS suppresses the remote dump and then processing continues.
You need to take the action only if you were expecting a remote CICS dump.
Notify the system programmer.
To resolve the problem, collect any data from GTF trace, any dumps and any relevant messages. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHDUMPX
An MVS SDUMPX request from CICS signalled by message DFHDU0201 may have resulted in a complete or partial SVC dump. Even though the request completed with an SDUMPX return code x'04', it is possible that sufficient information has been dumped to enable successful diagnosis of the problem that caused the dump to be taken. The accompanying message(s) IEA611E/IEA911E should be used to determine the suitability of the dump for successful diagnosis.
CICS proceeds as if the dump had been successful.
See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the SDUMPX return code X'04'.
Console
DFHDUDU
A remote MVS SDUMPX request has failed to complete successfully because there were no SDUMPX PROBDESC parameters supplied.
MVS invokes DFHDUMPX under the IEASDUMP.QUERY exit and without the SDUMPX PROBDESC parameters DFHDUMPX cannot determine whether to take or suppress a remote dump.
This is only an error if the remote SDUMPX request was made by CICS for a system dump code that included the RELATED option, or if the operator entered a remote SDUMPX request that included PROBDESC parameters. This is not an error if another non-CICS component intentionally calls DFHDUMPX without PROBDESC.
CICS proceeds as if the dump had been successful.
If you believe this is an error you will require further assistance from IBM to resolve this problem. Collect data from GTF trace, dumps, and any relevant messages. Then see Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHDUMPX
This message is output when attempting to write a record to the transaction dump data set. text-descr is one of the following:
None unless text-descr is DCB ABEND, in which case an exception entry is made in the trace table and a system dump is taken.
Notify the system programmer.
In the case of DCB ABEND, there will normally be an accompanying MVS error message to help identify the problem with the data set.
If the problem is not due to a major corruption of CICS, successful switching of dump data sets will reinstate the transaction dump environment. Otherwise, the transaction dump environment will be available only if the XDUOUT user-exit is active.
Console
DFHDUIO
XMEOUT Parameters: applid, dataset,text-descr
This message is issued in one of the following situations:
The insert dataset indicates the name of the data set being closed.
Processing continues.
If autoswitching of the transaction dump data set is not active, the transaction dump environment is available only if the XDUOUT user-exit is active.
If autoswitching is enabled, this message is followed by DFHDU0304 and DFHDU0305 to indicate that the data set switch is successful.
If the switch is unsuccessful, this message is followed by DFHDU0306.
None.
Console
DFHDUSU
XMEOUT Parameters: applid, dataset
This message is output when any of the following situations occur:
dataset in the message indicates the name of the data set being opened.
Processing continues.
None.
Console
DFHDUSU
XMEOUT Parameters: applid, dataset
This message is issued when one of the following situations occurs:
This message is always preceded by message DFHDU0304 and also, if the old dump data set was open, by message DFHDU0303.
ddname in the message indicates the ddname of the active transaction dump data set (either DFHDMPA or DFHDMPB).
Processing continues.
Print or copy the completed dump data set, and if required, reissue the command CEMT SET DUMP AUTO.
Console
DFHDUSU
XMEOUT Parameters: applid, ddname
This message occurs when attempting to open a transaction dump data set.
text-descr is one of:
An exception entry is made in the trace table.
In both cases, the transaction dump data set is not open, and unless the XDUOUT exit is active, the transaction dump is inoperative.
Message DFHME0116 is normally produced containing the symptom string for this problem.
See any associated MVS messages for further guidance.
Console
DFHDUIO
XMEOUT Parameters: applid, dataset,text-descr
This message is issued either when an attempt is made to open or close a dump data set, or when switching between dump data sets, to remind the user that CICS could not locate module DFHDUIO during initialization. CICS will have issued message DFHDU0102 during initialization to warn the user of this condition.
CICS continues with the transaction dump facility inoperative.
If necessary, refer to the user response for message DFHDU0102.
Console
DFHDUSU
XMEOUT Parameter: applid
This message is issued when a transaction dump has been requested for the transaction dump code dumpcode and the associated dump table entry specifies that CICS should be terminated.
This message records that it was a transaction dump table entry which requested the termination of CICS.
CICS is terminated.
Process any transaction dump in the normal way.
On a warm or emergency start, explicitly defined dump table entries are restored from the catalog. If the dump table entry for dumpcode was explicitly defined, it can be modified to prevent CICS from terminating, if desired, using CEMT or EXEC API commands.
Implicitly defined dump table entries are not recorded on the catalog
and are therefore not restored. On a cold or initial start,
CICS
does not restore the dump table from the catalog.
Console
DFHDUDU
XMEOUT Parameters: applid, dumpcode
This message is issued when a system dump has been requested for the system dump code dumpcode and the associated dump table entry specifies that CICS should be terminated.
This message records that it was a system dump table entry which requested the termination of CICS.
CICS is terminated.
Print off any system dump if required.
On a warm or emergency start, explicitly defined dump table entries are restored from the catalog. If the dump table entry for dumpcode was explicitly defined, it can be modified to prevent CICS from terminating using CEMT or EXEC API commands.
Implicitly defined dump table entries are not recorded on the catalog
and are therefore not restored. On a cold or initial start,
CICS
does not restore the dump table from the catalog.
Console
DFHDUDU
This message is issued when
CICS can not write the transaction dump to a transaction dump data set because the data sets are too small. CICS closes the data sets and processing continues.
Inform the system programmer.
You need to bring CICS down and increase the space allocation for the transaction dump data sets to resolve this problem.
You may decide to delay terminating CICS until a convenient time. You can issue the command CEMT SET DUMP OPEN to reinstate the transaction dump environment but you will continue to lose any dumps that are too large to be written to the data sets.
Console
DFHDUSU
XMEOUT Parameter:
applid
The access method has indicated a read error. The dump data set may not have been opened during the most recent CICS execution.
The record is skipped.
Either ensure that the JCL is correct, or determine the reason for the read errors.
Console
DFHDU640
An identification record has an incorrect code or format. The most common reasons for this error include the following.
In the latter case, the error would arise because no dumps were produced in the current execution or because the data sets had been switched.
Records are skipped and execution is terminated with a return code of 8.
Ensure that the correct data set is being processed. Alternatively, check for a possible error in the dump control program, DFHDCP.
If two dump data sets are being used, check that the data set being processed has been used before in the current CICS execution.
Console
DFHDU640
A dump or a print data set was not successfully opened.
If it was a dump data set that failed to open successfully, the system prints the message on the print data set and terminates execution with a return code of 12.
If it was the print data set that failed to open successfully, the system terminates execution with a return code of 16.
If the JCL is correct with the stated ddnames as in the message, determine why the data set cannot be opened. The return codes are issued by DFHDU640. They only identify whether a dump or print data set failed.
Console
DFHDU640
The dump data set has been filled.
The dump utility program DFHDU640 terminates.
Check that the dump is complete and that no incomplete message is at the end of it. If there is an incomplete message at the end of the dump, the last dump in the data set may not contain all the information required. You should recreate the problem to try and get a complete dump. If dump data set auto-switching was active at the time the dump was taken, a complete version of the dump is present on the alternate dump data set.
SYSPRINT
DFHDU640
The access method has indicated 36 invalid records
in
the dump data set. The most probable cause of this problem is an invalid
end-of-file marker which caused the access method to attempt to read
beyond the last record in the data set. This problem may also have
been caused if:
The dump utility execution is terminated with a return code of 8 from DFHDU640.
Determine and correct the reason for the access failure. Recreate the dump if necessary.
Console
DFHDU640
The dump utility program, DFHDU410, has detected an error while copying trace records from the trace data set. Trace records may be omitted from the formatted output.
DFHDU410 attempts to read the next trace block and continues formatting trace records.
To resolve the problem, keep the dump and contact your IBM Support Center. Further guidance on how to prepare information for IBM support is given in the CICS Problem Determination Guide. If you are not familiar with this process, refer to the guide before contacting IBM.
Console
DFHDU640
Due to an error in the MVS NOTE macro, the dump utility program, DFHDU640 was unable to note the position on the data set at which the trace data started. It is therefore not possible to return to the start of the trace data after the abbreviated trace has been formatted in order to print the trace with format FULL.
Transaction dump formatting continues with only abbreviated trace for this dump.
If only the full trace is required, rerun the DFHDU410 job with the NOABBREV parameter. Otherwise attempt to recreate the dump. If the problems recurs, keep the dump and contact your IBM Support Center. Further guidance on how to prepare information for IBM support is given in the CICS Problem Determination Guide. If you are not familiar with this process, refer to the guide before contacting IBM.
Console
DFHDU640