Dumping after error

To request that the system dump the storage occupied by a failing program and other storage needed to debug the program, code one of the following:

SYSABEND, SYSMDUMP, or SYSUDUMP DD statement in the step to be dumped. The system produces the requested dump if the step terminates abnormally or if the step starts to terminate abnormally, but the system recovery procedures allow the step to terminate normally.
If there are multiple failures in the same job step, only the last failure is reported. Therefore, inspect the dump to gather information about any possible earlier failures.
DUMP in the BYTES, CARDS, LINES, or PAGES parameter of the JOB statement. The system produces the dump requested by the dump DD statement for the step if the system cancels the job because:
1. The job's output exceeds the maximum specified on the BYTES, CARDS, LINES, or PAGES parameter of the JOB statement, or
2. The job's output exceeds the maximum output specified on the JES3 //*MAIN statement, or the JES2 /*JOBPARM statement
3. The job's output exceeds the maximum defined by the installation defaults specified at initialization.
DUMP in the BYTES, CARDS, LINES, or PAGES parameter on the JES3 //*MAIN statement in the job and a SYSABEND, SYSMDUMP, or SYSUDUMP DD statement in the step to be dumped. The system produces the dump requested by the dump DD statement if JES3 cancels the job because the job's output exceeds the BYTES, CARDS, LINES, or PAGES limit or, if no limits are given, the installation default limit for the job class.

If the dump is to be printed directly on a 3800 Printing Subsystem, the SYSABEND or SYSUDUMP DD statement can request a high-density dump by specifying:

FCB=STD3 to produce dump output at 8 lines per inch.
CHARS=DUMP to produce 204-character print lines.