Collecting information for dead-letter queue problems on Multiplatforms

If you need assistance to resolve a problem where a IBM® MQ queue manager is placing messages on its dead-letter queue (DLQ) on Multiplatforms, you might need to collect troubleshooting information to include with your support case to help find a solution to the problem.

Before you begin

Before you start this task, answer the following questions about the problem:

What dead-letter queue problem did you observe on the system?
What time did the dead-letter queue problem start and when did it stop?
Where are the dead-letter messages coming from, and what is their intended route?

About this task

If the messages are going to the dead-letter queue right now, or if you can reproduce the problem that causes the messages to go there, you can generate data to provide more information about the problem.

After collecting the troubleshooting information, you can send it to IBM.

Procedure

Generate a trace of the queue manager while messages are going to the dead-letter queue:
Browse the messages on the dead-letter queue using a sample program such as amqsbcg just before it is retrieved by the target application.
For example, to browse messages on a queue called 'Target.Queue' on queue manager called 'QMA', enter this command:
```
amqsbcg Target.Queue QMA > Target.Queue.browse.txt
```
Place the browse output file, that is QMA.DLQ.browse.txt directly in the high-level error log directory, that is:
- var/mqm/errors on Linux.
- MQ_INSTALLATION_PATH\errors on Windows.
Both the automatic and the manual collection processes described in Step 3 collect files found in this directory.
Collect the IBM MQ data.
You can collect do this either automatically or manually:
- Collect the data automatically by using the runmqras command as described in Collecting troubleshooting information automatically with runmqras. Be sure to collect the runmqras defs, cluster, and trace sections, and to specify your case number as shown in the following example:
```
runmqras -section defs,cluster,trace -qmlist QMA -caseno TS001234567
```
- Alternatively, collect the data manually as described in Collecting troubleshooting information manually.
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 Support in the US, you can call 1-800-IBM-SERV.