SVC dump

SVC dumps are produced under these conditions:

VTAM® produces an SVC dump automatically when a program exception occurs. VTAM might be terminated as part of this process. The system log indicates the location of the dump output and whether the dump was successful.
An operator issues the MODIFY CSDUMP command without specifying any triggers, which causes an immediate dump. This action does not cause VTAM to stop.
An operator uses the CSDUMP start option or the MODIFY CSDUMP command to set the dump triggers, and an event occurs that matches one of the triggers to take the dump. This action does not cause VTAM to stop.
An operator can request a dump with the operating system DUMP command. This will not cause VTAM to stop.
An operator uses a SLIP command with ACTION=SVCD specified, and an event occurs that matches the trap indicated in the SLIP.
A macroinstruction issues an abend, and there is a DD statement with ddname=SYSMDUMP.
An SDUMP macroinstruction is issued.
System recovery routines produce an SVC dump if VTAM causes an error, such as a program exception or abend.

An SVC dump is written to a SYS1.DUMPnn data set (if allocated), the SYSMDUMP output data set, or the data set specified on the DCB operand of the SDUMP macroinstruction. An SVC dump can be formatted for viewing by IPCS. To determine what document contains more information on SVC dump, see z/OS Information Roadmap.