![[z/OS]](ngzos.gif)
Getting a dump with IBM MQ for z/OS
Use this topic to understand the different dump types for IBM® MQ for z/OS® problem determination.
The following table shows information about the types of dump used with IBM MQ for z/OS and how they are initiated. It also shows how the dump is formatted:
| Dump type | Data set | Output type | Formatted by | Caused by |
|---|---|---|---|---|
| SVC | Defined by system | Machine readable | IPCS in conjunction with an IBM MQ for z/OS verb exit | z/OS or IBM MQ for z/OS functional recovery routine detecting error, or the operator entering the z/OS DUMP command |
| SYSUDUMP | Defined by JCL (SYSOUT=A) | Formatted | Normally SYSOUT=A | An abend condition (only taken if there is a SYSUDUMP DD statement for the step) |
| Snap | Defined by JCL CSQSNAP (SYSOUT=A) | Formatted | Normally SYSOUT=A | Unexpected MQI call errors reported to adapters, or FFST information from the channel initiator |
| Stand-alone | Defined by installation (tape or disk) | Machine readable | IPCS in conjunction with an IBM MQ for z/OS verb exit | Operator IPL of the stand-alone dump program |
IBM MQ for z/OS recovery routines request SVC dumps for most X'5C6' abends. The exceptions are listed in SVC dumps on z/OS. SVC dumps issued by IBM MQ for z/OS are the primary source of diagnostic information for problems.
If the dump is initiated by the IBM MQ subsystem, information about the dump is put into area called the summary portion. This contains information that the dump formatting program can use to identify the key components.
For more information about SVC dumps, see the z/OS MVS Diagnosis: Tools and Service Aids manual.