DFHDUxxxx messages

DFHDU0001
applid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.
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, 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).

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHDUDT, DFHDUTM, DFHDUDU, DFHDUXD, DFHDUIO, DFHDUSU, DFHDUXW, DFHPCXDF, DFHSAXDF, DFHDLXDF, DFHXDXDF, DFHXRXDF, DFHTCXDF, DFHTRXDF, DFHFCXDF

XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname

DFHDU0002
applid A severe error (code X'code') has occurred in module modname.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHDUDT, DFHDUTM

XMEOUT Parameters: applid, X'code',modname

DFHDU0004
applid A possible loop has been detected at offset X'offset' in module modname.
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 happened to be executing at the time when the error was detected.

System action:

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.

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.

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.

Destination:

Console

Modules:

DFHDUDT, DFHDUTM, DFHDUXD, DFHDUIO, DFHDUSU, DFHDUXW, DFHPCXDF, DFHSAXDF, DFHDLXDF, DFHXDXDF, DFHXRXDF, DFHTCXDF, DFHTRXDF, DFHFCXDF

XMEOUT Parameters: applid, X'offset', modname

DFHDU0006
applid Insufficient storage to satisfy Getmain (code X'code') in module modname. MVS code mvscode.
Explanation:

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.

System action:

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.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUTM

DFHDU0102
applid DFHDUIO could not be loaded. Transaction dump is inoperative.
Explanation:

CICS could not locate module DFHDUIO during initialization.

System action:

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.

User response:

Use the exception trace entry and any other relevant messages to determine why module DFHDUIO was not available.

Destination:

Console

Modules:

DFHDUDM

XMEOUT Parameter: applid

DFHDU0103
applid An abend has occurred during initialization of dump domain in module DFHDUDM.
Explanation:

A dump domain has failed to initialize.

System action:

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.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHDUDU

XMEOUT Parameter: applid

DFHDU0201
applid About to take SDUMP. Dumpcode: dumpcode, Dumpid: dumpid.
Explanation:

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.

System action:

When the dump is complete, message number DFHDU0202 is issued.

User response:

Inform the system programmer, who should refer to the CICS message indicated by dumpcode to resolve the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

DFHDU0202
applid SDUMP complete.
Explanation:

This message is issued on successful completion of an SDUMP.

System action:

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.

User response:

Print off the system dump if required. A previous MVS message identifies in which SYS1.DUMP data set this dump can be found.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

DFHDU0203I
date time applid A transaction dump was taken for dumpcode: dumpcode, Dumpid: dumpid.
Explanation:

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

System action:

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.

User response:

Print off the transaction dump if required.

Destination:

CDUL

Modules:

DFHDUDU

XMEOUT Parameters: date, time,applid, dumpcode, dumpid

Start of change
DFHDU0205
applid A system dump for dumpcode: dumpcode was suppressed by the reason.
Explanation:

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.

System action:

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.

User response:

If a system dump is required for this dump code, perform the user action appropriate to the reason reason given in the message.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

End of change
Start of change
DFHDU0206I
date time applid A transaction dump for dumpcode: dumpcode was suppressed by the reason.
Explanation:

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.

System action:

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.

User response:

If a transaction dump is required for this dump code, perform the user action appropriate to the reason reason given in the message.

Destination:

CDUL

Modules:

DFHDUDU

XMEOUT Parameters: date, time,applid, dumpcode, reason

End of change
Start of change
DFHDU0207I
date time applid Transaction and system dumps for dumpcode: dumpcode were suppressed by the reason.
Explanation:

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.

System action:

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.

User response:

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:

Destination:

CDUL

Modules:

DFHDUDU

XMEOUT Parameters: date, time,applid, dumpcode, reason

End of change
Start of change
DFHDU0208
applid SDUMP busy - CICS will retry in five seconds.
Explanation:

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.

System action:

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.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

End of change
Start of change
DFHDU0209
applid Retrying SDUMP.
Explanation:

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.

System action:

CICS reissues the SDUMP request.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

End of change
Start of change
DFHDU0210
applid SDUMPX REQUEST FAILED - reason.
Explanation:

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:

SDUMPX RETURN CODE X'nn' REASON X'mm' SDUMPX BUSY
At the time of the MVS SDUMPX request issued by CICS, another address space in the same MVS system was in the process of taking an SDUMP. This causes MVS to reject the new request. If a nonzero value is specified for the DURETRY SIT parameter, CICS retries the SDUMPX request every five seconds for the specified period. This message is only issued if SDUMPX is still busy after the final retry.
SDUMPX RETURN CODE X'nn' REASON X'mm' NO DATA SET AVAILABLE
No SYS1.DUMP data sets were available at the time the SDUMPX request was issued.
SDUMPX RETURN CODE X'nn' REASON = X'mm'
MVS has rejected the SDUMPX request for some other reason than those listed above. X'nn' gives the SDUMPX return code and X'mm' gives the SDUMPX reason code.
STIMERM FAILED
In order to delay for five seconds before retrying SDUMPX after an SDUMPX BUSY condition, CICS issues an MVS STIMERM macro request. MVS has indicated that the STIMERM request has failed.
NOT AUTHORIZED IN CICS
SDUMP is not authorized for this CICS run.
INSUFFICIENT STORAGE
CICS issued an MVS GETMAIN for Subpool 253 storage during the processing of the SDUMPX request. The GETMAIN has been rejected by MVS.
DFHDUSVC FESTAE FAILED
CICS issued an MVS FESTAE request from DFHDUSVC during the processing of the SDUMPX request. The FESTAE has been rejected by MVS.
IWMWQWRK RETURN CODE X'xx' REASON X'yy' REMOTE DUMPS NOT TAKEN
CICS issued an MVS IWMWQWRK request during the processing of the SDUMPX request for dumps of related CICS systems. The IWMWQWRK request has been rejected by MVS return code X'xx' and reason X'yy'. In this case CICS was unable to dump related CICS address spaces but has attempted to dump the local address space.
DFHDUSVC INVALID PROBDESC
The SDUMPX PROBDESC parameters, created by DFHDUSVC, contain invalid data.
System action:

CICS proceeds as if the dump had been successful.

User response:

The user response depends on the reason, (reason), for the failure.

SDUMPX RETURN CODE X'nn' ONLY PARTIAL DUMP.
See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the SDUMPX return code X'nn'. Use MVS problem determination methods to determine why a partial dump was taken.
SDUMPX RETURN CODE X'nn' REASON X'mm' SDUMPX BUSY
Cause the SDUMP to be reissued after, if appropriate, increasing the value of the DURETRY system initialization parameter. See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the SDUMPX return code X'nn' and reason X'mm'.
SDUMPX RETURN CODE X'nn' REASON X'mm' NO DATA SET AVAILABLE
Clear a SYS1.DUMP data set and then cause the SDUMP request to be reissued. See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the SDUMPX return code X'nn' and reason X'mm'.
SDUMPX RETURN CODE X'nn' REASON X'mm'
No action is required if the dump was suppressed deliberately. If the dump has failed because of an error in the MVS SDUMP routine, use MVS problem determination methods to fix the error and then cause the SDUMP request to be reissued. See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the SDUMPX return code X'nn'. and reason code X'mm'
STIMERM FAILED
Use MVS problem determination methods to fix the STIMERM failure and then cause the SDUMP request to be reissued.
NOT AUTHORIZED IN CICS
This reason is unlikely to occur because SDUMPX is unconditionally authorized during CICS initialization, and should be authorized throughout the CICS run. If you do get this reason, the CICS AFCB (authorized function control block) has probably been accidentally overwritten.
INSUFFICIENT STORAGE
Ensure sufficient storage is available to MVS for subpool 253 requests.
DFHDUSVC FESTAE FAILED
Use MVS problem determination methods to fix the FESTAE failure and then cause the SDUMP request to be reissued. See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the FESTAE macro.
IWMWQWRK RETURN CODE X'xx' REASON X'yy'.
CICS issued an MVS IWMWQWRK request during the processing of the SDUMPX request. The IWMWQWRK request has been rejected by MVS return code X'xx' and reason X'yy'. See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the return and reason codes.
DFHDUSVC INVALID PROBDESC
The SDUMPX PROBDESC parameters, created by DFHDUSVC during the processing of the SDUMPX request, are invalid. The PROBDESC parameters have probably been accidentally overwritten.
Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

End of change
Start of change
DFHDU0211
applid THE XDUREQ USER EXIT IS NOT CALLED FOR DUMPCODE dumpcode.
Explanation:

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.

System action:

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.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

End of change
Start of change
DFHDU0212
applid Requested transaction dump code dumpcode is invalid.
Explanation:

A requested transaction dump code has unprintable characters, or has leading or imbedded blanks.

System action:

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

User response:

Print off the transaction dump and determine how an abend or EXEC CICS request was issued with an invalid dump code.

Destination:

Console

Modules:

DFHDUDU

XMEOUT Parameters: applid, dumpcode

End of change
Start of change
DFHDU0213
REMOTE SDUMPX REQUEST FAILED - reason.
Explanation:

A remote MVS SDUMPX request from CICS has failed to complete successfully. The possible reasons, (reason) for the failure are as follows:

DFHDUMPX AUTOMATIC STORAGE GETMAIN FAILED.
CICS issued an MVS GETMAIN for Subpool 253 storage during the processing of the SDUMPX request. The GETMAIN has been rejected by MVS.
DFHDUMPX NOT RUNNING IN THE MASTER ADDRESS SPACE.
DFHDUMPX must run in the MASTER address space. CICS stops processing the remote SDUMPX request if it detects that DFHDUMPX is running in another address space.
IWMWQWRK FOUND NO ADDRESS SPACES TO DUMP.
The MVS IWMWQWRK service found no CICS address spaces with work relating to the remote SDUMPX request.
IWMWQWRK FAILED WITH A WARNING.
CICS issued an MVS IWMWQWRK request from DFHDUMPX during the processing of the remote SDUMPX request. MVS has rejected the IWMWQWRK request with a warning return code.
IWMWQWRK FAILED WITH AN ERROR.
CICS issued an MVS IWMWQWRK request from DFHDUMPX during the processing of the remote SDUMPX request. MVS has rejected the IWMWQWRK request with an error return code.
DFHDUMPX OUTPUT WORKAREA GETMAIN FAILED
CICS issued an MVS GETMAIN for Subpool 253 storage during the processing of the SDUMPX request. The GETMAIN has been rejected by MVS.
DFHDUMPX RECOVERY ROUTINE ENTERED
An abnormal end (abend) or program check has occurred in DFHDUMPX. This implies that there is an error in CICS code.

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.

System action:

CICS proceeds as if the dump had been successful.

User response:

The user response depends on the reason, (reason), for the failure.

DFHDUMPX AUTOMATIC STORAGE GETMAIN FAILED.
Ensure sufficient storage is available to MVS for subpool 253 requests.
DFHDUMPX NOT RUNNING IN THE MASTER ADDRESS SPACE.
This reason is unlikely to occur because CICS requests that the MVS CSVDYNEX service adds DFHDUMPX as an IEASDUMP.QUERY exit in the MASTER address space.

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.

IWMWQWRK FOUND NO ADDRESS SPACES TO DUMP.
This is unlikely to be an error. DFHDUMPX is invoked on all the MVS images in a SYSPLEX for a remote SDUMPX request. Some of the images may not have any CICS address spaces with work relating to the CICS system which originated the remote SDUMPX request.
IWMWQWRK FAILED WITH A WARNING.
The IWMWQWRK return code and reason are included in a CICS trace entry which is written to the GTF data set. The trace entry is not written to the CICS internal trace or in the CICS auxiliary trace data set because DFHDUMPX does not execute under a CICS TCB.

See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the IWMWQWRK return code and reason.

IWMWQWRK FAILED WITH AN ERROR.
The IWMWQWRK return code and reason are included in a CICS trace entry which is written to the GTF data set. The trace entry is not written to the CICS internal trace or in the CICS auxiliary trace data set because DFHDUMPX does not execute under a CICS TCB.

See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the IWMWQWRK return code and reason.

DFHDUMPX OUTPUT WORKAREA GETMAIN FAILED
Ensure sufficient storage is available to MVS for subpool 253 requests.
DFHDUMPX RECOVERY ROUTINE ENTERED

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUMPX

End of change
Start of change
DFHDU0214
DFHDUMPX IS ABOUT TO REQUEST A REMOTE SDUMP.
Explanation:

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:

System action:

Processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUMPX

End of change
Start of change
DFHDU0215
DFHDUMPX IS ABOUT TO SUPPRESS A REMOTE SDUMPX.
Explanation:

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.

System action:

Processing continues.

User response:

To determine whether action is necessary refer to any DFHDU0213 message preceding this one.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUMPX

End of change
Start of change
DFHDU0216
PROBDESC DOES NOT CONTAIN CICS DATA.
Explanation:

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.

System action:

DFHDUMPX will request that MVS suppresses the remote dump and then processing continues.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUMPX

End of change
Start of change
DFHDU0217
applid SDUMPX request completed with a return code of X'04'. A complete or partial dump has been taken.
Explanation:

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.

System action:

CICS proceeds as if the dump had been successful.

User response:

See the OS/390 MVS Programming: Authorized Assembler Services Reference for an explanation of the SDUMPX return code X'04'.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

End of change
Start of change
DFHDU0218
No PROBDESC parameters supplied to DFHDUMPX.
Explanation:

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.

System action:

CICS proceeds as if the dump had been successful.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUMPX

End of change
Start of change
DFHDU0302I
applid Transaction Dump Data set dataset to be closed due to text-descr
Explanation:

This message is output when attempting to write a record to the transaction dump data set. text-descr is one of the following:

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHDUIO

XMEOUT Parameters: applid, dataset,text-descr

End of change
Start of change
DFHDU0303I
applid Transaction Dump Data set dataset closed.
Explanation:

This message is issued in one of the following situations:

The insert dataset indicates the name of the data set being closed.

System action:

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.

User response:

None.

Destination:

Console

Modules:

DFHDUSU

XMEOUT Parameters: applid, dataset

End of change
Start of change
DFHDU0304I
applid Transaction Dump Data set dataset opened.
Explanation:

This message is output when any of the following situations occur:

dataset in the message indicates the name of the data set being opened.

System action:

Processing continues.

User response:

None.

Destination:

Console

Modules:

DFHDUSU

XMEOUT Parameters: applid, dataset

End of change
Start of change
DFHDU0305I
applid Transaction Dump Data set switched to ddname
Explanation:

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

System action:

Processing continues.

User response:

Print or copy the completed dump data set, and if required, reissue the command CEMT SET DUMP AUTO.

Destination:

Console

Modules:

DFHDUSU

XMEOUT Parameters: applid, ddname

End of change
Start of change
DFHDU0306
applid Unable to open Transaction Dump Data set dataset - text-descr
Explanation:

This message occurs when attempting to open a transaction dump data set.

text-descr is one of:

OPEN ERROR
An attempt was made to open the dump data set, and an abend exit was invoked. This condition is usually accompanied by MVS system messages.
INSUFFICIENT STORAGE
An MVS GETMAIN was issued to obtain storage below the 16MB line. This request was unsuccessful.
System action:

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.

User response:

See any associated MVS messages for further guidance.

Destination:

Console

Modules:

DFHDUIO

XMEOUT Parameters: applid, dataset,text-descr

End of change
Start of change
DFHDU0307
applid Module DFHDUIO is unavailable. Transaction dump is inoperative.
Explanation:

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.

System action:

CICS continues with the transaction dump facility inoperative.

User response:

If necessary, refer to the user response for message DFHDU0102.

Destination:

Console

Modules:

DFHDUSU

XMEOUT Parameter: applid

End of change
Start of change
DFHDU0308I
applid CICS will terminate because the Dump Table entry for the transaction dump code: dumpcode specifies shutdown.
Explanation:

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.

System action:

CICS is terminated.

User response:

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. Start of changeOn a cold or initial start,End of change CICS does not restore the dump table from the catalog.

Destination:

Console

Modules:

DFHDUDU

XMEOUT Parameters: applid, dumpcode

End of change
Start of change
DFHDU0309I
applid CICS will terminate because the Dump Table entry for the system dump code: dumpcode specifies shutdown.
Explanation:

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.

System action:

CICS is terminated.

User response:

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. Start of changeOn a cold or initial start,End of change CICS does not restore the dump table from the catalog.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDUDU

End of change
Start of changeDFHDU0310End of change
Start of changeapplid XDUCLSE auto-switch request overridden. Transaction dump data sets are too small.End of change
Start of change
Explanation:

This message is issued when

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDUSUEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of change
DFHDU1601
DATA SET READ ERROR.
Explanation:

The access method has indicated a read error. The dump data set may not have been opened during the most recent CICS execution.

System action:

The record is skipped.

User response:

Either ensure that the JCL is correct, or determine the reason for the read errors.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDU640

End of change
Start of change
DFHDU1602
36 CONSECUTIVE UNIDENTIFIABLE RECORDS, DUMP UTILITY TERMINATED.
Explanation:

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.

System action:

Records are skipped and execution is terminated with a return code of 8.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDU640

End of change
Start of change
DFHDU1603
NO {DUMP | PRINT} DATA SET DD CARD {DFHDMPDS | DFHPRINT}, DUMP UTILITY TERMINATED.
Explanation:

A dump or a print data set was not successfully opened.

System action:

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.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDU640

End of change
Start of change
DFHDU1604
END OF FILE ENCOUNTERED, LAST DUMP MAY BE INCOMPLETE.
Explanation:

The dump data set has been filled.

System action:

The dump utility program DFHDU640 terminates.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHDU640

End of change
Start of change
DFHDU1609
36 READ ERRORS ENCOUNTERED. DUMP UTILITY TERMINATED.
Explanation:

Start of changeThe access method has indicated 36 invalid recordsEnd of change 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:

System action:

The dump utility execution is terminated with a return code of 8 from DFHDU640.

User response:

Determine and correct the reason for the access failure. Recreate the dump if necessary.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDU640

End of change
Start of change
DFHDU1610
DUMP FORMATTING HAS ENCOUNTERED AN INVALID TRACE BLOCK. TRACE ENTRIES MAY BE LOST.
Explanation:

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.

System action:

DFHDU410 attempts to read the next trace block and continues formatting trace records.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDU640

End of change
Start of change
DFHDU1611
FILE ERROR, FULL TRACE FAILED. DUMP FORMATTING WILL CONTINUE WITH ABBREVIATED TRACE.
Explanation:

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.

System action:

Transaction dump formatting continues with only abbreviated trace for this dump.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDU640

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