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 IBM problem support 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 z/OS MVS Programming: Authorized Assembler Services Reference (Volume 1) 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 z/OS MVS Programming: Authorized Assembler Services Reference (Volume 1) 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 IBM problem support for guidance on how to proceed.

Module

DFHDUMPX

Destination

Console



DFHDU0213.html | Timestamp icon Last updated: Sunday, 4 June 2017