Troubleshooting
Problem
A IBM MQ queue manager is experiencing a problem with cluster queues, topics or channels, and you need to collect MustGather data to find a solution.
Environment
These instructions apply only to IBM MQ V9.0 and V8.0, and WebSphere MQ V7.5, V7.1, V7.0 and V6.0 on AIX, HP-UX, Linux, Solaris and Windows, and to IBM MQ V9.0 and V8.0, and WebSphere MQ V7.1, V7.0 and V6.0 on IBM i. Refer to the IBM MQ Read First page for instructions on other operating systems and to the MQ Cluster Troubleshooting guide for self-help on this topic:
Resolving The Problem
Please answer these questions about the problem and then follow the steps below:
- What cluster problem did you observe on the system?
- What time did the cluster problem start and when did it stop?
- What does your cluster topology look like, and where are the full repositories?
- Which cluster queue managers, channels, queues and topics are involved in the problem?
Step 1: Generate Data
If the cluster problem is reproducible or is happening right now, generate data to provide more information about the problem:
- Generate a trace of the queue manager while the cluster problem is happening.
- If the problem involves other queue managers in the cluster, such as the cluster full repositories, generate MQ trace simultaneously on those queue managers:
- On Linux and UNIX systems, save the output from the mqconfig command. If you are running IBM MQ V9.0 or V8.0, WebSphere MQ V7.5.0.2 or later, or V7.1.0.3 or later, the mqconfig command is already available as part of the MQ server installation.
Step 2: Collect Data
- On UNIX and Linux, place the mqconfig data from Step 1 directly in the top-level MQ errors directory. Both the runmqras automation tool and the manual collection steps below collect files found there.
- Collect data automatically with the runmqras command from the systems involved in the cluster problem if you are running IBM MQ V9.0 or V8.0, WebSphere MQ V7.5, V7.1.0.1 or later, or V7.0.1.8 or later. Be sure to collect the runmqras defs, cluster and trace sections, and to specify your PMR number. The runmqras output will include all of your cluster definitions as well as the contents of your cluster repository cache:
- Alternatively, collect the MQ data manually from the systems involved in the cluster problem.
- If your system has more than one 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 InstallationXWindows
C:\> "C:\Program Files\IBM\MQ\bin\setmqenv" -n InstallationX - Record the MQ version and maintenance level for queue managers involved in the cluster problem.
- Record the operating system version and maintenance level for queue managers involved in the cluster problem.
- Save the MQ configuration information, for example registry keys and ini files.
- If your system has more than one MQ installation, record your MQ installation details:
Linux and UNIX
sh> dspmqinst > /tmp/dspmqinst.txtWindows
C:\> dspmqinst > %TEMP%/dspmqinst.txt - Record the status of your queue managers:
Linux and UNIX
sh> dspmq -a > /tmp/dspmq.txtWindows
C:\> dspmq -a > %TEMP%/dspmq.txtIBM i Command Line
===> WRKMQMIBM i Qshell
===> /QSYS.LIB/QMQM.LIB/DSPMQ.PGM -a > /tmp/dspmq.txt - Record the MQ processes active on your system:
Linux and UNIX
sh> ps -ef | grep mq > /tmp/ps.txtWindows
C:\> TASKLIST /V > %TEMP%/tasklist.txtIBM i Command Line
===> WRKACTJOB SBS(QMQM)IBM i Qshell
===> ps -ef | grep mq > /tmp/ps.txt - On MQ V7.1 and later installations, use dmpmqcfg to record the queue manager configuration:
Linux and UNIX
sh> dmpmqcfg -m QMA > /tmp/QMA.config.txtWindows
C:\> dmpmqcfg -m QMA > %TEMP%\QMA.config.txtIBM i Qshell
===> /QSYS.LIB/QMQM.LIB/DMPMQCFG.PGM -m QMA > /tmp/QMA.config.txt - Otherwise, on MQ V7.0 and earlier installations, use runmqsc to record the queue manager configuration. If any command gives 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 - On all MQ installations, use runmqsc to record status information from the queue manager. If any command gives 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 - On MQ installations, use runmqsc to record information about cluster objects known to the queue manager. If any command gives an error, carry on with the others:
DISPLAY CLUSQMGR(*) ALL
DISPLAY QCLUSTER(*) ALL
DISPLAY TCLUSTER(*) ALL - Dump the contents of the cluster repository cache using the amqrfdm utility. Be sure to use the correct input file for your platform from the files attached to the bottom of this page. For example:
Dumping the cluster repository cache for queue manager QMA on Linux or UNIX
sh> amqrfdm -m QMA < cluster-unix.txt > /tmp/QMA.cluster.txtDumping the cluster repository cache for queue manager QMA on Windows
C:\> amqrfdm -m QMA < %TEMP%\cluster-win.txt > %TEMP%\QMA.cluster.txtDumping the cluster repository cache for queue manager QMA in the IBM i Qshell
===> /QSYS.LIB/QMQM.LIB/AMQRFDM.PGM -m QMA < cluster-IBMi.txt > /tmp/QMA.cluster.txt - Manually package your files for IBM, including files containing the output from the commands listed in Step 1 and 2.
- If your system has more than one MQ installation, use the setmqenv command to choose the one with the problem before proceeding:
Collecting runmqras output from queue managers QMA and REPOS1
runmqras -section defs,cluster,trace -qmlist QMA,REPOS1 -pmrno 12345,67R,890
Step 3: Send Data to IBM
- Send your data to the IBM ECuRep repository by email to [email protected], by standard or secure HTTP or FTP. or by using the IBM Secure Diagnostic Data Upload Utility (SDDUU) Java application.
- While the data is transferring, send an email or use the IBM Service Request tool to update your PMR with your description of the problem and of the data you are sending.
- Contact your country representative if you need to speak to an IBM technical support representative, or in the US call 1-800-IBM-SERV. Refer to the IBM Software Support Handbook for more information on working with IBM.
A good description of the problem and the data is the most important information you can provide to IBM. Please do not send data without providing a description!
[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Problem Determination","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.0;7.5;7.1;7.0;6.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]Product Synonym
IBMMQ WebSphere MQ WMQ
- If the problem involves other queue managers in the cluster, such as the cluster full repositories, generate MQ trace simultaneously on those queue managers:
Was this topic helpful?
Document Information
Modified date:
22 June 2018
UID
swg21293315