Data set for dump

Define the data set in either:

The JCL for the job step, for batch processing
The logon procedure for a TSO/E userid, for foreground processing

Define the data set in a DD statement with a ddname of SYSABEND, SYSMDUMP, or SYSUDUMP. The ddname for the data set determines how the dump can be printed or viewed, what the dump contains, and how the dump contents can be customized. The first two effects are discussed in the following topics.

The system writes the dump in a sequential data set using the basic sequential access method (BSAM). The dump data set can be on any device supported by BSAM. Note that the system provides a data control block (DCB) for the dump data set and opens and closes the DCB.

You can also use extended format sequential data sets as dump data sets for ABEND dumps. Extended format sequential data sets have the following features:

Have a greater capacity than sequential data sets
Support striping
Support compression

Using DSNTYPE=LARGE: In z/OS® V1R7 and later releases, sequential data sets that use DSNTYPE=LARGE are allowable for ABEND dumps when the systems that are involved in processing a DSNTYPE=LARGE data set are migrated to V1R7 prior to their use. If analysis using an earlier release is required, use z/OS V1R7 to transcribe the dump into a data set supported by the earlier release.

Placing dump data sets in cylinder-managed space: In z/OS V1R11 and later releases, extended format sequential data sets can be placed in either track-managed space or cylinder-managed space. Abend dump fully supports placement of dump data sets in cylinder-managed space.

VIO for ADDRSPC=REAL: A SYSMDUMP DD statement must specify a virtual input/output (VIO) data set if the job or step to be dumped is running in nonpageable virtual storage, that is, the JCL JOB or EXEC statement specifies ADDRSPC=REAL.