Collect and analyze WebSphere MQ data to solve problems with channels

Technote (troubleshooting)


Problem(Abstract)

Your WebSphere MQ system is having problems with channels, 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.

Environment

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 sending queue manager.
  2. WebSphere MQ trace on the receiving 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 channel 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 sending queue manager.
  2. WebSphere MQ data from the receiving queue manager.


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 channel problem:

  • Always gather object definitions using the section defs
  • If the problem is with a cluster channel, include the section cluster
  • If you generated trace files in Step 1, collect them by including the section trace


Examples

  1. To collect basic information for a channel problem on queue manager QMA:

    runmqras -section defs -qmlist QMA


  2. If the problem is with a channel on queue manager QMB and you generated traces:

    runmqras -section defs,trace -qmlist QMB


  3. If the problem is with a cluster channel on queue manager QMC, and you want to send the data directly to IBM by standard FTP:

    runmqras -section defs,cluster,trace -qmlist QMC -pmrno 12345,67R,890 -ftp IBM

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

    Windows
    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 sending side only, use runmqsc to record your queues, channels and channel status information:

    DISPLAY QREMOTE(*) ALL
    DISPLAY QLOCAL(*) ALL
    DISPLAY CHANNEL(*) ALL
    DISPLAY CHSTATUS(*) ALL


  6. On the receiving side only, use runmqsc to record your channels, listeners, and their status:

    DISPLAY CHANNEL(*) ALL
    DISPLAY CHSTATUS(*) ALL
    DISPLAY LISTENER(*) ALL
    DISPLAY LSSTATUS(*) ALL


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

  8. 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

    Windows
        C:\> netstat -an


  1. On Linux and UNIX systems, please send the output from the mqconfig script from the sending and receiving systems 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 channel problem:

  1. Review the IBM Support Assistant findings.
  2. Follow the channel 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
Channels LU62 / TCP

Software version:

6.0, 7.0, 7.1, 7.5

Operating system(s):

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

Software edition:

All Editions

Reference #:

1292924

Modified date:

2014-04-18

Translate my page

Machine Translation

Content navigation