Collect IBM MQ MustGather data to solve dead letter queue problems on Linux, UNIX, Windows and IBM i

If you are running IBM MQ V9.2, V9.1, V9.0 or V8.0, IBM WebSphere MQ V7.5, V7.1.0.1 or later, or V7.0.1.8 or later collect data automatically with the runmqras command on both sides of the channel. Be sure to collect the runmqras defs, cluster and trace sections, and to specify your case number:

runmqras -section defs,cluster,trace -qmlist QMA -caseno TS001234567

1. If your system has more than one IBM MQ installation, use the setmqenv command to choose the one with the problem before proceeding:

   Linux and UNIX

   sh> . /path/to/mqm/bin/setmqenv -n InstallationX

   Windows

   C:\> "C:\Program Files\IBM\MQ\bin\setmqenv" -n InstallationX

2. Record the IBM MQ version and maintenance level on both sides of the channel. Alternatively, collect the IBM MQ data manually on both sides of the channel.

3. Record the Operating System version and maintenance level on both sides of the channel.

4. Record the IP addresses and hostnames of the systems on both sides of the channel.

5. Save the IBM  MQ configuration information, for example, registry keys and .ini files.

6. If your system has more than one IBM MQ installation, record your IBM MQ installation details:

   Linux and UNIX

   sh> dspmqinst > /tmp/dspmqinst.txt

   Windows

   C:\>dspmqinst > %TEMP%/dspmqinst.txt

7. Record the status of your queue managers:

   Linux and UNIX

   sh> dspmq -a > /tmp/dspmq.txt

   Windows

   C:\> dspmq -a > %TEMP%/dspmq.txt

   IBM i command line

   ===> WRKMQM

   IBM i Qshell

   ===> /QSYS.LIB/QMQM.LIB/DSPMQ.PGM -a > /tmp/dspmq.txt

8. Record the IBM MQ processes active on your system:

   Linux and UNIX

   sh> ps -ef | grep mq > /tmp/ps.txt

   Windows

   C:\> TASKLIST /V > %TEMP%/tasklist.txt

   IBM i command line

   ===> WRKACTJOB SBS(QMQM)

   IBM i Qshell

   ===> ps -ef | grep mq > /tmp/ps.txt

9. On IBM WebSphere MQ V7.1 and later installations, use dmpmqcfg command to record the queue manager configuration:

   Linux and UNIX

   sh> dmpmqcfg -m QMA >/tmp/QMA.config.txt

   Windows

   C:\> dmpmqcfg -mQMA>%TEMP%\QMA.config.txt

   IBM i Qshell

   ===> /QSYS.LIB/QMQM.LIB/DMPMQCFG.PGM -mQMA > /tmp/QMA.config.txt

10. Otherwise, on IBM WebSphere MQ V7.0 and earlier installations, use runmqsc to record the queue manager configuration. If any command returns an error, carry on with the others:
    
    DISPLAY QMGR ALL
DISPLAY Q(*) ALL
DISPLAY SUB(*) ALL
DISPLAY TOPIC(*) ALL
DISPLAY CHANNEL(*) ALL
DISPLAY SERVICE(*) ALL
DISPLAY PROCESS(*) ALL
DISPLAY LISTENER(*) ALL
DISPLAY NAMELIST(*) ALL

11. On all IBM MQ server installations, use runmqsc to record status information from the queue manager . If any command returns an error, carry on with the others:
    
    DISPLAY PUBSUB ALL
DISPLAY QMSTATUS ALL
DISPLAY CHSTATUS(*) ALL
DISPLAY LSSTATUS(*) ALL
DISPLAY SVSTATUS(*) ALL
DISPLAY SBSTATUS(*) ALL
DISPLAY CONN(*) TYPE(*) ALL
DISPLAY QSTATUS(*) TYPE(QUEUE) ALL
DISPLAY QSTATUS(*) TYPE(HANDLE) ALL
DISPLAY TPSTATUS('#') TYPE(PUB) ALL
DISPLAY TPSTATUS('#') TYPE(SUB) ALL
DISPLAY TPSTATUS('#') TYPE(TOPIC) ALL

12. If your channel is having difficulty connecting, use your Operating System tools to list network connections on both sides immediately before and after the connection attempt:

    Displaying network connections on Linux and UNIX

    sh> netstat -an

    Displaying network connections on Windows

    C:\>NETSTAT -AN

    Displaying IPv4 and IPv6 network connections at the IBM i command line

    ===> NETSTAT OPTION(*CNN) ===> NETSTAT OPTION(*CNN6)

13. Manually package your files for IBM , including files containing the output from the commands listed in Step 1 and Step 2.