Dump suppression

The system requests dumps you might not need. To keep from using your system's resources on unneeded dumps, you should suppress them. The reasons for the unneeded dumps and ways to suppress them are:

Duplicate dumps: The system can request a dump for a problem that recurs. The dump written when the problem first occurs can be used for diagnosis; additional dumps are unneeded. Also, sometimes a system can request several dumps for one instance of a problem. A recurring problem may have been diagnosed, but the fix has not yet been incorporated into the system.
To eliminate the duplicate dumps, use dump analysis and elimination (DAE). See Using DAE to suppress dumps.
Dumps for certain abend codes: For some abend codes, the accompanying messages provide the needed problem data. To eliminate the dumps for these abend codes, use a SLIP command. See Using a SLIP command to suppress dumps.
A dump for an abend in an application program: if the dump is not needed. See Using an ABEND macro to suppress dumps.
Dumps the installation decides are not needed: If you decide that certain dumps are not needed, you can code a routine for an installation exit to suppress these dumps. See Using installation exit routines to suppress dumps.

This topic lists the ways that an expected dump can be suppressed, so that you can determine why you did not receive an intended dump. See Determining why a dump was suppressed.