Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Examples of the SYSABEND, SYSMDUMP, and SYSUDUMP DD statements z/OS MVS JCL Reference SA23-1385-00 |
|
Example 1
The SYSUDUMP DD statement specifies that you want the dump routed to system output class A. Example 2
The SYSMDUMP DD statement specifies that the dump is to be stored on a tape. Because the LABEL parameter is not coded, the tape must have IBM® standard labels. Example 3
Both SYSABEND DD statements specify that the dump is to be stored. The space request in STEP1 is ample and will not inhibit dumping due to insufficient space. If STEP1 does not abnormally terminate but STEP2 does, the system writes the dump for STEP2 in the space allocated in STEP1. In both steps, an abnormal termination disposition of KEEP is specified so that the dump is stored if either of the steps abnormally terminates. If both of the steps successfully execute, the second DISP subparameter, DELETE, in STEP2 instructs the system to delete the data set and free the space acquired for dumping. Example 4
The SYSMDUMP DD statement allocates dump data set MDUMP to a direct access device. Example 5
Only the SYSMDUMP dump written by the first job will be in data set SYS1.SYSMDP00. All subsequent jobs receive message IEA849I, indicating that the data set is full. Note: When you specify a DSNAME of SYS1.SYSMDPxx with DISP=SHR, the
system writes the first SYSMDUMP dump on the data set. You must offload
this first SYSMDUMP dump and write an EOF mark at the beginning of
the SYS1.SYSMDPxx data set before subsequent dumps can be written
to that data set.
|
Copyright IBM Corporation 1990, 2014
|