Collecting information for abend problems on z/OS

If you need assistance from IBM® Support to resolve an abend problem on IBM MQ for z/OS®, you first need to collect troubleshooting information to send to IBM Support to help find a solution.

Procedure

Collect the following general information:
- IBM MQ version, release, and maintenance level
- Operating system version, release, and maintenance level
- Related products version, and release levels if applicable
Collect the following troubleshooting (MustGather) information for this problem:
1. Collect the following required information:
  
  Job logs
  
  You can find the IBM MQ for z/OS job logs in the Syslog, MSTR job log, and CHIN job log. The job logs are named xxxxMSTR and xxxxCHIN, where xxxx is the IBM MQ subsystem identifier (SSID). For more information, see Creating a print data set containing the JES2 joblog for the IBM MQ for z/OS jobs.
  
  Dumps generated at point of failure
  
  IBM MQ dumps are located in a system dump data set (see Step 4).
2. Optionally also collect the z/OS LOGREC report (see SYS1.LOGREC information on z/OS).
Search the IBM Support site for known problems.
You can search by using symptoms like the message number and error codes.
Review the dumps generated at point of failure.
IBM MQ dumps are located in a system dump data set and can be identified by their title. The title for a dump requested by IBM MQ starts with the four-character subsystem name of the queue manager. For example:
```
CSQ1,ABN=5C6-00E20016,U=SYSOPR ,C=MQ900.910.DMC -CSQIALLC,M=CSQGFRCV,LOC=CSQSLD1 .CSQSVSTK+00000712
```
The dump title might provide sufficient information in the abend and reason codes to resolve the problem. For more information, see Analyzing the dump and interpreting dump titles on z/OS.
For more information about the two system abend completion codes X'5C6' and X'6C6' that IBM MQ for z/OS uses, see IBM MQ for z/OS abends. You can also search for known problems at the IBM support site by using abend codes, reason codes, and program names listed in the dump.
Check the system log (syslog).
Comm dumps might not contain the queue manager name, depending on the comment specified in the dump command. Check the syslog for an IEA611I or IEA911E message to determine the dump data set name and also to see whether the dump is complete or partial. For example:
```
IEA611I COMPLETE DUMP ON DUMP.MQT1MSTR.DMP00074
DUMPID=074 REQUESTED BY JOB(MQT1MSTR)
FOR ASID(005E)

IEA911E PARTIAL DUMP ON SYS1.MCEVS4.DMP00039
DUMPID=039 REQUESTED BY JOB(DMSGTODI)
FOR ASID(00D2)
```
If insufficient disk space is the reason for the problem, there might not be sufficient information in the dump to diagnose the problem.
Dumps might be suppressed by Dump Analysis and Elimination (DAE). In this case, some symptoms might not appear in the system log (syslog) or joblog, but they appear in Logrec (see SYS1.LOGREC information on z/OS). For more information about management of DAE, see Generating a suppressed dump.
Send the information that you have collected to IBM.
A good description of the problem and the data is the most important information you can provide to IBM. Do not send data without providing a description!

For FTP and email instructions, see Exchanging information with IBM Software Support.

To open or update a case, go to the IBM My Support site.
Note: Always update your case to indicate that data was sent.

If you need to speak with IBM Software Support, contact your country representative. If you need to speak with IBM Software Support in the US, you can call 1-800-IBM-SERV.