Collect and analyze WebSphere MQ data to solve problems with C, C++, COBOL and .NET clients

Technote (troubleshooting)


Your WebSphere MQ C, C++, COBOL or .NET client application is experiencing problems connecting to a queue manager or processing messages once connected, and you need to collect data to find a solution. This document explains how to generate diagnostic data when the problem is happening, how to collect the available data from the system, and how to analyze that data and share it with IBM support.


These instructions are for WebSphere MQ on AIX, HP-UX, IBM i, Linux, Solaris, and Windows systems. Return to the WebSphere MQ MustGather index for other systems.

Resolving the problem

Step 1: Generate Data

If the problem has already happened and you cannot reproduce it reliably, proceed to Step 2 to collect the information already logged by WebSphere MQ. Otherwise, please try to generate the following diagnostic data while the problem is happening:

  1. WebSphere MQ trace on the client system showing the error.
  2. WebSphere MQ trace on the queue manager taken at the same time.

Try to start and stop trace as quickly as possible in order to limit both the overhead of tracing and the size of the trace files. On systems other than IBM i and Windows, format the trace files after stopping the trace.

Step 2: Collect Data

Collect the following data for your client problem. Use the runmqras tool if your WebSphere MQ installation is V7.0.1.8 or later, V7.1.0.1 or later, or V7.5, otherwise follow the manual instructions:

  1. WebSphere MQ data from the client system.
  2. WebSphere MQ data from the queue managers the client uses.

Collect WebSphere MQ data automatically with runmqras

WebSphere MQ includes an automated data collection tool called runmqras which you can use if you are running WebSphere MQ V7.0.1.8 or later, V7.1.0.1 or later, or V7.5.

Follow the WebSphere MQ runmqras usage instructions to gather data for your client problem:

  • Always gather object definitions on the queue manager using the section defs
  • If you generated trace files in Step 1, collect them by including the section trace


  1. To collect basic information from a client system:


  2. If you generated traces on the client, be sure to collect them:

    runmqras -section trace

  3. If your client was connecting to queue manager QMA, be sure to gather data on the queue manager system as well:

    runmqras -section defs,trace -qmlist QMA -pmrno 12345,67R,890

Collect WebSphere MQ data manually

  1. If your system has multiple WebSphere MQ installations, issue the setmqenv command to choose the right installation. On Linux and UNIX, source setmqenv using a dot. For example:

    Linux & UNIX
    sh> . /path/to/mqm/bin/setmqenv -n Installation0

    C:\> C:\Program Files (x86)\IBM\WebSphere MQ\bin\setmqenv -s

  2. Record the operating system version and maintenance level on both systems.

  3. Record the WebSphere MQ version and maintenance level on both systems.

  4. Collect the WebSphere MQ error logs as well as any WebSphere MQ FFST files. On IBM i, follow these instructions to save the necessary files and job logs.

  5. On the client system, list the environment variables which are set when you start the client application. For example, save the output of the following command just before starting the client application:


  6. Describe how your client application connects to the queue manager:

    a. If you are using the MQSERVER variable, its value should be captured by the previous command.

    b. If you are using a client channel table, provide its path and use a queue manager to display its contents:


    c. If you are using MQCONNX to specify the connection details, what values do you use?

  7. On the queue manager system only, use runmqsc to record your channels, listeners, and their status, as well as any channel authentication records. If any command gives an error, carry on to the next one.


  8. On both sides, record the IP address and hostname of the system. If the system has multiple addresses or hostnames, include them all.

  9. If you are having difficulty starting the channel, use your operating system tools to list network connections immediately before and after your attempt to start the channel.

    IBM i Command Line
    ===> NETSTAT *CNN

    Linux & UNIX
    sh> netstat -an

    C:\> netstat -an

  1. On Linux and UNIX systems, please send the output from the mqconfig script on the queue manager system in addition to the other WebSphere MQ data.

Step 3: Analyze Data

You can now analyze WebSphere MQ data with IBM Support Assistant tools such as IBM Support Assistant Team Server. Using a web browser, you can see an overview of your system based on the data you collected, review problem symptoms found in the data, and search IBM's Global Knowledge Base for relevant Fix Packs, APARs and Technotes. Follow these steps until you find a solution for your client application problem:

  1. Review the IBM Support Assistant findings.
  2. Follow the client troubleshooting guide.
  3. Use IBM Service Request to open a problem record with IBM.
  4. Send your data to IBM for further analysis.

  • Tell us what errors you saw, where you saw them, and what time they happened
  • Let us know if you made any changes to WebSphere MQ or the system before the problem
  • Share any other observations which you think will help us to better understand the problem

Please see the IBM Software Support Handbook for more information on working with IBM support.

Product Alias/Synonym

WebSphere MQ WMQ

Rate this page:

(0 users)Average rating

Add comments

Document information

More support for:

WebSphere MQ

Software version:

5.3, 6.0, 7.0, 7.1, 7.5

Operating system(s):

AIX, HP-UX, IBM i, Linux, Solaris, Windows

Software edition:

All Editions

Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation