DFHKE0210    applid SDUMP REQUEST FAILED. (MODULE modname) - reason.

Explanation

An MVS SDUMP request from CICS signalled by message DFHKE0201 has failed to complete successfully. The possible reasons reason for the failure are detailed below.

SDUMP RETURN CODE X'04' ONLY PARTIAL DUMP

The SYS1.DUMP data set to which the dump was written was not large enough to contain all of the dumped storage.

SDUMP RETURN CODE X'08' REASON X'02' SDUMP BUSY

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.

If a nonzero value has been specified for the DURETRY SIT parameter, CICS will have retried the SDUMP request every five seconds for the specified period. This message is issued if SDUMP is still busy after the final retry.

SDUMP RETURN CODE X'08' REASON X'03' SUPPRESSED BY INSTALLATION.

The dump was suppressed by a request by the installation (for example: DUMP=NO at IPL; or CHNGDUMP SET,NODUMP).

SDUMP RETURN CODE X'08' REASON X'04' SUPPRESSED BY SLIP.

The dump was suppressed by a SLIP NODUMP command.

SDUMP RETURN CODE X'08' REASON X'05' NO DATA SET AVAILABLE

No data set is available for the SDUMP request.

SDUMP RETURN CODE X'08' REASON X'0B' SUPPRESSED BY DAE.

The dump was suppressed by the Dump Analysis and Elimination feature (DAE).

SDUMP RETURN CODE X'08' REASON X'3E' MAXSPACE EXCEEDED.

SVC dump is already using the maximum amount of virtual storage (as determined by the installation, using the MAXSPACE parameter on the CHNGDUMP command) to process other dumps.

SDUMP RETURN CODE X'08' REASON X'46' INSUFFICIENT DISK SPACE.

SVC dump stopped the dump because the System Resources Manager (SRM) detected a critical shortage of auxiliary storage.

SDUMP RETURN CODE X'nn' REASON X'mm'

MVS rejected the SDUMP request for some other reason than those listed above. X'nn' gives the hexadecimal SDUMP return code and X'mm' gives the hexadecimal SDUMP reason.

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 SDUMP request. The GETMAIN was rejected by MVS.

STIMERM FAILED

In order to delay for five seconds before retrying SDUMP after an SDUMP busy condition, CICS issues an MVS STIMERM macro request. MVS has indicated that the STIMERM request has failed.

DFHDUSVC FESTAE FAILED

CICS issued an MVS FESTAE request from DFHDUSVC during the processing of the SDUMP request. The FESTAE has been rejected by MVS.

DFHDUSVC FUNCTION INVALID

CICS called DFHDUSVC during the processing of the SDUMP request. The function passed to DFHDUSVC was invalid.

During initialization, CICS does not have access to the user's applid coded in the SIT. If CICS produces this message in these circumstances, it uses the default applid value DBDCCICS.

System action

CICS proceeds as if the dump had been successful.

User response

The user response depends on the reason for the failure. For:

SDUMP RETURN CODE X'04' ONLY PARTIAL DUMP

Examine the reason code that explains why the partial dump was taken. This code is contained in the MVS message IEA911E. See the z/OS MVS System Messages, Volume 1 (ABA-ASA) for a description of this reason code.

SDUMP RETURN CODE X'08' REASON X'02' SDUMP BUSY

Cause the SDUMP to be reissued by increasing the DURETRY value on the SIT.

SDUMP RETURN CODE X'08' REASON X'03' SUPPRESSED BY INSTALLATION

No action is required if the dump was suppressed deliberately.

SDUMP RETURN CODE X'08' REASON X'04' SUPPRESSED BY SLIP.

Delete the relevant SLIP trap with the SLIP DEL command and then cause the SDUMP request to be reissued.

SDUMP RETURN CODE X'08' REASON X'05' NO DATA SET AVAILABLE

Clear a SYS1.DUMP data set and then cause the SDUMP request to be reissued.

SDUMP RETURN CODE X'08' REASON X'0B' SUPPRESSED BY DAE.

Stop the Dump Analysis and Elimination service by issuing the command SET DAE=xx, where xx is the suffix of an ADYSETxx member of SYS1.PARMLIB that contains DAE=STOP. See the z/OS MVS Initialization and Tuning Reference for information about ADYSETxx. When DAE is stopped, cause the SDUMP request to be reissued.

SDUMP RETURN CODE X'08' REASON X'3E' MAXSPACE EXCEEDED.

Increase the amount of virtual storage that SVC dump can use to capture data by issuing the command CHNGDUMP SET,DUMP,MAXSPACE=xxxM, where xxxM specifies the number of megabytes of storage to be used. Then cause the SDUMP request to be reissued.

SDUMP RETURN CODE X'08' REASON X'46' INSUFFICIENT DISK SPACE.

Increase the amount of disk space available for recording system dumps. Then cause the SDUMP request to be reissued.

SDUMP RETURN CODE X'nn' REASON X'mm'

No action is required if the dump was suppressed deliberately. If the dump 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 z/OS MVS Programming: Authorized Assembler Services Reference (Volume 1) for an explanation of the SDUMP return code X'nn' and reason X'mm'.

NOT AUTHORIZED IN CICS

This reason should not appear, because an SDUMP 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.

STIMERM FAILED

Use MVS problem determination methods to fix the STIMERM failure and then cause the SDUMP request to be reissued.

DFHDUSVC FESTAE FAILED

Use MVS problem determination methods to fix the FESTAE failure and then cause the SDUMP to be reissued. See the z/OS MVS Programming: Authorized Assembler Services Reference (Volume 1) for an explanation of the FESTAE macro.

DFHDUSVC FUNCTION INVALID

The CICS DAFPB (dump authorized function parameter block) has probably been accidentally overwritten.

Notify the system programmer. If CICS is still running, it will be necessary to decide whether to terminate CICS.

You may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

To resolve the problem, collect any dumps and any relevant messages and contact your IBM Support Center.

Further guidance on how to prepare information for IBM support is given in the Troubleshooting and support section If you are not familiar with this process, refer to the guide before contacting IBM support.

Module

DFHKEDD, DFHKEDS, DFHKEGD, DFHKEIN, DFHKESTX

Destination

Console



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