When SVC dumps are not produced

Occasionally, an SVC dump is not produced. Generally, dumps are suppressed for space, time, or security violations.

The following list summarizes other reasons why SVC dumps might not be produced:

  • No empty dump data sets were available.
  • The z/OS® serviceability level indication processing (SLIP) commands suppressed the abends.

    The z/OS initialization and tuning publication lists the defaults of these commands; however, sites can change them. More information can be found in the z/OS conversion notebook. Finally, refer to the z/OS diagnostic techniques publication for information about tailoring dumps with SLIP commands.

  • One of the following abend reason codes was issued. These reason codes do not require a dump to determine the cause of abend.
    00C90080   00C90096   00D10100   00E2002B
    00D99003   00E3000C   00E30085   00E30089
    00E30093   00E30301   00E30302   00E50013
    00E50070   00E7000C
  • Db2 subsystem percolation occurred (SDWACOMU=DSN2).
  • A dump was already provided (SDWAEAS=ON).
  • The abend was '04F', '222', '33E', 'B37', 'D37' 'E37', or 'x13' (where x is any hexadecimal digit).
  • The abend was '13E', and one or more of the following conditions was true:
    • Home address space of the failing agent (EB) was not in allied memory.
    • Termination of the execution unit TCB did not result from the z/OS CANCEL W/DUMP command.
    • Prior dumps were generated for the terminating TCB.
    • The Db2 dump work area (DMPW) is in use by another dump request:
      VRA KEY VRARRK22 X'DE') DATA ('NODMPW')