When a dump is not suppressed

When DAE is active but does not suppress a dump, DAE adds the reason that the dump is not suppressed to the dump header record. When viewing a dump online or printing a dump, specify the IPCS VERBEXIT DAEDATA subcommand to see the reason that a dump was not suppressed.

Some reasons for not suppressing a dump are:
  • The dump is unique. DAE found no match for the symptom string.
  • The current ADYSETxx member does not specify SUPPRESS or SUPPRESSALL for the type of dump being requested.
  • A SLIP operator command specifies that the dump is not to be suppressed. A SLIP command with ACTION=SVCD, ACTION=SYNCSVCD, ACTION=STDUMP, ACTION=RECOVERY, or ACTION=TRDUMP always produces a dump. ACTION=NOSUP stops suppression.
  • DAE could not find all required symptoms.
  • DAE could not find the minimum number of symptoms.
  • The symptom string built by DAE was shorter than the minimum length.
  • DAE found certain errors. For example, a required symptom had a key that was not valid.
  • The VRADAE key in the SDWA is absent, signifying that the dump should not be suppressed, and the DAE parameter of the ADYSETxx parmlib member does not specify SUPPRESSALL.
  • The VRANODAE key is present in the SDWA, specifying that the dump should not be suppressed.
Parent topic: Suppressing dumps that duplicate previous dumps