Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Storing a dump z/OS MVS JCL Reference SA23-1385-00 |
|
If you wish to store a dump instead of having it printed, code
the following parameters on the dump DD statement:
Tip: SYSABEND, SYSUDUMP, and SYSMDUMP can use extended format sequential data sets to exploit striping, compression, or both. Striping speeds the writing process and compression reduces the space consumed and speeds the I/O bound dump process. Extended format sequential data set hold more than 64K tracks per volume making it an attractive destination for dumps. DSNAME=LARGE also allows data sets to use more than 64K tracks per volume. Note: Do not use VSAM for dump data sets.
SYSMDUMP Requirements: The SYSMDUMP DD statement must specify a magnetic tape unit or a direct access device. Do not direct SYSMDUMP to SYSOUT. With the exception of the following facility, the system processes
dump data sets according to the disposition to which they are allocated.
To keep only the first SYSMDUMP dump written to a dump data set,
specify the following on the SYSMDUMP DD statement:
Note: This restriction is not enforced. If SYSOUT is
used, the resulting dump will be unusable for diagnosis.
See z/OS MVS Diagnosis: Tools and Service Aids for a description of the SYS1.SYSMDPxx naming convention and an explanation of how the system manages the dump data sets. |
Copyright IBM Corporation 1990, 2014
|