IEA611I   {COMPLETE|PARTIAL} DUMP ON dsname text

DUMPID=dumpid REQUESTED BY JOB (jobname)
FOR ASIDS(id,id,…)
[REMOTE DUMPS REQUESTED|
   REMOTE DUMP FOR SYSNAME: sysname]
INCIDENT TOKEN: incident-token
[SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz]
[reason-text]
[ERRORID = SEQ yyyyyy CPUzz ASIDasid
   TIMEhh.mm.ss.t] [TSOID = tsoid]
[ID = uuuuuuuuuu]

The system wrote a complete or partial SVC dump to an automatically allocated dump data set on a direct access storage device. In the message text:

COMPLETE

The SVC dump contains all of the virtual storage that was requested.

PARTIAL

Not all of the virtual storage requested was collected. However, enough storage may have been dumped to allow the debugging of the problem to be successful. The codes in the SDRSN field can be used to determine what storage was affected, or what problems were encountered while SVC dump processing was executing.

dsname

The dump was written to the data set named dsname.

dumpid

The 3-character dump identifier.

jobname

The name of the job that requested the dump.

id

The address space identifiers (ASID), in hexadecimal, for the address spaces included in the dump.

REMOTE DUMPS REQUESTED

The SDUMPX macro or DUMP command that requested this dump also requested dumps on other systems in the sysplex.

REMOTE DUMP FOR SYSNAME: sysname

This dump was requested by sysname, which is another system in the sysplex.

INCIDENT TOKEN: incident-token

The formatted incident token for the dump.

SDRSN = vvvvvvvv wwwwwwww xxxxxxxx zzzzzzzz

The system wrote a dump.

vvvvvvvv

Partial dump reason code. One of the following:

80000000

A system request block (SRB) for the dump could not be scheduled to the requested address space. Either no current address space had the requested ASID or the system was ending the address space with that ASID.

40000000

SVC dump processing could not obtain real storage manager (RSM) serialization because of a hierarchy problem.

20000000

SVC dump processing could not obtain RSM serialization because of a RSM control problem.

10000000

SVC dump processing could not obtain a central storage buffer from the real storage manager.

08000000

An error in scheduled SVC dump processing caused recovery to receive control.

04000000

An error in summary dump processing caused recovery to receive control.

02000000

An error in summary dump processing or suspend summary dump processing caused recovery to receive control.

00400000

An error caused the loss of the summary dump.

00200000

During suspend summary dump processing, the virtual storage buffer filled up.

00100000

No more summary dump data could be written because the central storage buffer was full.

00080000

While the system was writing a trace table, an error occurred. The trace table could not be written.

00008000

The dump of the data above the bar could not be written because the storage buffer was unavailable.

00004000

Option USERTOKEN is not accessible.

00002000

Some private storage above the bar was not collected because the extension range table is full.

00001000

Extended range table has filled while collecting ranges of private storage above the bar.

00000800

Extended range table has filled while collecting ranges of common storage above the bar.

wwwwwwww

Partial dump reason code. One of the following:

80000000 | 40000000

While processing SVC X'33', the system detected an error and gave recovery control.

20000000

The system detected an error in the SVC dump task and gave recovery control.

10000000

The SVC dump task failed.

08000000

The system detected an error while writing a trace table. The system could not write the trace table.

04000000 | 02000000

While processing an SVC dump, the system detected an error and gave recovery control.

01000000

The started dump task failed.

00800000

A task abnormally ended, and SVC dump processing took a partial dump. The resource manager for SVC dump processing receives control.

00400000

The system detected an error in the SVC dump writing task and gave recovery control.

00200000

An address space involved in the dump abnormally ended, and SVC dump took a partial dump. The resource manager for SVC dump processing receives control.

00100000

The DUMPSRV address space abnormally ended, and SVC dump processing took a partial dump. The resource manager for SVC dump processing receives control.

00080000

While processing the dump header, the system ran out of space to place data.

00040000

During dump processing of local storage, the system issued a PURGEDQ because a hung address space was detected. This will result in the loss of some storage related to the address space.

00020000

During dump processing of a possibly hung address space, dump processing obtained only fixed storage for the address space.

00010000

During dump processing of a possibly hung address space, the address space was found to be invalid. The dump data may not be consistent.

00008000

A partial dump was taken because a requested data space is inaccessible because ALESERV ADD failed.

00004000

No additional data spaces could be allocated for local address space data capture.

xxxxxxxx

Partial dump reason code. One of the following:

80000000

While building the address range table for global storage areas, SVC dump processing filled the table and remaining entries could not be added.

40000000

While building the address range table for local storage areas, SVC dump processing filled the table and remaining entries could not be added.

20000000

While building the address range table, SVC dump processing filled the table and remaining entries could not be added.

10000000

While dump processing was writing to the dump data set, an I/O error occurred.

08000000

The dump data set is full, but more data needs to be dumped.

04000000

An error occurred while writing the summary dump.

02000000

An error occurred while dump processing was obtaining trace data.

01000000

While dump processing was setting up the service request block (SRB) under which the dump was to be processed, an error occurred.

00800000

An error occurred in an exit routine.

00400000

An error occurred while writing the end-of-data record to the dump data set.

00200000

Some read-only ranges of data could not be added to the range table.

00100000

While dump processing was copying global storage into a data space, an error occurred.

00080000

While dump processing was copying a sub-range of common storage into a data space, an error occurred.

00040000

An error occurred in the processing of data spaces that were requested through the LISTD keyword on the SDUMPX macro, or through the DSPNAME parameter on the DUMP command.

00020000

Dump processing could not add some ranges of read/write storage to the range table.

00010000

SVC dump processing truncated the dump because the maximum amount of space was reached.

00008000

While processing the SQA SDATA option, the system filled the range table.

00004000

While processing the CSA SDATA option, the system filled the range table. Remaining entries could not be added.

00002000

While processing global subpools, the system filled the range table. Remaining entries could not be added.

00001000

While processing the LSQA SDATA option, the system filled the range table. Remaining entries could not be added.

00000800

While processing the RGN SDATA option, the system filled the range table. Remaining entries could not be added.

00000400

While processing private subpools, the system filled the range table. Remaining entries could not be added.

00000200

While processing the SWA SDATA option, the system filled the range table. Remaining entries could not be added.

00000100

While copying global data into a data space, dump processing was unable to capture some ranges of global storage.

00000080

An exit data space could not be created, or the data space was created but an ALET could not be obtained to access the data space.

00000040

A summary data space could not be created, or the data space was created but an ALET could not be obtained to access the data space.

00000020

A local data space could not be created, or the data space was created but an ALET could not be obtained to access the data space.

00000010

A global data space could not be created, or the data space was created but an ALET could not be obtained to access the data space.

00000008

SVC dump could not create or could not use the data spaces that are required to process the STRLIST request. Some data will not be included in the dump.

00000004

The extended range table has filled while collecting ranges of storage above the bar.

00000002

The exit dataspace is full.

00000001

SVC dump processing truncated the dump because a critical shortage of auxiliary storage existed.

zzzzzzzz

Dump reason code. One of the following:

Bits in the first byte indicate a result that occurred because one or more of the following conditions might exist

1. There is a shortage of central storage
2. There is a shortage of auxiliary storage
3. The DUMPSRV address space dispatching priority is too low.

80000000

Dump processing had to reset the system dispatchable. The data in some storage areas might have changed before the dump capture completed.

40000000

Dump processing had reset the tasks dispatchable in one or more address spaces involved in the SVC dump. The data in some storage areas might have changed before the dump capture completed.

20000000

Dump processing reset the caller's unit of work, which was stopped as part of suspend summary dump processing. Then dump processing failed during suspend summary dump processing, leaving the caller suspended.

10000000

IEAVTSDB released serialization for all serialized structures specified in the STRLIST because SDUMP appears to have failed or ended.

08000000

The central storage buffer containing the summary dump was released when it was determined that dump processing was hung. The summary dump was lost.

04000000

The system has been reset to be dispatchable because the duration of the system being set non-dispatchable exceeded the maximum time interval.

00800000

Facility not available. Some structures will not be dumped.

00400000

The structure is not available for one of the following reasons:

• The system detected a structure failure and the structure cannot be accessed
• The structure is not allocated

00200000

No facility dump space is allocated or no facility dump space is available because it is being used to hold structure dump tables for other structure dumps

00100000

Possible error in STRLIST parameter list for one of the following reasons:

• The structure does not exist in the active policy
• The structure type is not compatible with the specified range options
• A lock structure was requested. SDUMP does not support lock structures

00080000

Some or all of the STRLIST could not be processed.

00040000

The system released structure dump serialization before capturing all the data. The system captured the rest of the data after releasing serialization.

00020000

Recovery received control while processing STRLIST

00010000

SVC dump was unable to continue processing a structure requested in the STRLIST parameter list. This is because the operator deleted the structure dump with the SETXCF FORCE command.

00008000

Recovery received control while building the SDUMP signals for other systems in the sysplex

00004000

The capture data space for SDPX/DATA is full.

reason-text

One of the following:

SUMMARY DUMP INFORMATION WAS LOST

A problem arose where processing was unable to complete a requested summary dump. Refer to the description of the SDRSN bits that are set to determine whether the data was truncated, or completely lost.

A CRITICAL AUXILIARY STORAGE SHORTAGE EXISTED

SVC dump processing truncated the dump because a critical shortage of auxiliary storage existed.

DUMP DATA SET FULL - DUMP ENDED WHILE WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}

The dump data set is full, but more data needs to be dumped. The message indicates at what point the data set became full.

I/O ERROR - NO EOF WRITTEN - DUMP ENDED WHILE WRITING {SUMDUMP|GLOBAL|LOCAL|STRLIST}

An I/O error occurred while the system was writing to the dump data set. The message indicates the system was dumping at the time of the I/O error.

MAXSPACE LIMIT REACHED WHILE CAPTURING DUMP

Insufficient space was available to capture the complete dump. See the MAXSPACE parameter of the CHNGDUMP SET,SDUMP command in z/OS MVS System Commands.

ERROR OCCURRED IN AN SDUMP EXIT

ERROR OCCURRED IN AN SDUMP LOCAL EXIT

ERROR OCCURRED IN AN SDUMP GLOBAL EXIT

ERROR OCCURRED IN AN SDUMP EARLY GLOBAL EXIT

ERROR OCCURRED IN AN SDUMP ONE-TIME-ONLY EXIT

ERROR OCCURRED IN AN SDUMP DYNAMIC LOCAL EXIT

ERROR OCCURRED IN AN SDUMP DYNAMIC GLOBAL EXIT

Dump processing encountered an unexpected error in an SDUMP exit of the specified type.

SOME STORAGE COULD NOT BE DUMPED RC=rc

Storage could not be dumped. rc can be one of the following:

04

The system could not find the requested ASIDs.

08

Not all of the data requested in a summary dump could be contained in the central storage buffer or virtual storage buffer.

Note: Even though some summary dump records might be missing, IEA611I COMPLETE DUMP is issued when there are no other data truncation reason bits set. This indicates that the dump contains all of the virtual storage requested. Only the summary dump records are missing, and these are usually duplicated in the virtual storage dumped at a slightly later time.

12

Either (1) the internal SVC dump control blocks are full, so that some data was not dumped, or (2) dump processing received an error return code when it tried to dump the system trace.

16

SVC dump was not able to process all of the structures specified in the STRLIST parameter list.

20

SDUMP processing could not collect the local storage of at least one of the normally collected storage address spaces involved in the dump. Refer to the description of the SDRSN bits that are set for more information.

SYSTEM RESET DISPATCHABLE PRIOR TO DUMP COMPLETION

Dump processing failed or ended with the system set non-dispatchable. The system detected the error and reset dispatchable.

TASKS RESET DISPATCHABLE PRIOR TO DUMP COMPLETION

Dump processing failed or ended with tasks set non-dispatchable in one or more address spaces involved in the SVC dump. The system detected the error and reset the tasks dispatchable.

ENABLED CALLER RESET PRIOR TO DUMP COMPLETION

Dump processing failed or ended during suspend summary dump processing, leaving the caller suspended. The system detected the error and reset the caller's unit of work.

STRUCTURE DUMP SERIALIZATION RELEASED PRIOR TO DUMP COMPLETION

The SVC dump time disabled interruption exit routine released dumping serialization that was held for a structure requested in the STRLIST parameter list. Serialization was released because:

• The routine had detected that SVC dump processing was not continuing normally or had ended and left the structure serialized.
• ACCESSTIME=ENFORCE was specified on the dump request (or defaulted) and the data requested in the STRLIST parameter list for a requested structure was not completely processed within the time limit specified by the ACCESSTIME parameter on the IXLCONN macro.

ERROR OCCURRED IN SDUMP

Dump processing encountered an unexpected error.

ERRORID = SEQyyyyyy CPUzz ASIDasid TIMEhh.mm.ss.t

The error identifier.

yyyyyy

The sequence number

zz

The central processor address

asid

The ASID for the address space in which the error occurred

hh.mm.ss.t

The time in hours (00 through 23), in minutes (00 through 59), in seconds (00 through 59), and in tenths of a second (0 through 9).

TSOID = tsoid

The dump was generated for a SLIP trap that was set in a Time Sharing Option (TSO) session.

tsoid

The identifier of the TSO user who defined the trap.

ID = uuuuuuuuuu

The component or subsystem identifier that was supplied in the ID keyword on the SDUMP or SDUMPX macro.