Collect and analyze WebSphere MQ data to solve problems with logging

Technote (troubleshooting)


Problem(Abstract)

Your WebSphere MQ queue manager is reporting errors logging data or recovering information from the logs 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.

Diagnosing 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 queue manager showing the error.

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

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


Examples

  1. To collect information from queue manager QMA:

    runmqras -section defs,logger -qmlist QMA


  2. If you generated traces of the queue manager, be sure to collect them too:

    runmqras -section defs,logger,trace -qmlist QMA


  3. If you also wish to send the data to IBM by standard FTP under your PMR number:

    runmqras -section defs,logger,trace -qmlist QMA -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. Collect the qm.ini and qmstatus.ini files for the queue manager.

  6. Except on IBM i, recursively list the contents of the "LogPath" directory named in the qm.ini file and save the output, for example:

    Linux & UNIX
    sh> ls -ltR /var/mqm/log/MY!QMGR > logfiles.txt

    Windows
    C:\> DIR /S "C:\Program Files (x86)\IBM\WebSphere MQ\log\MY!QMGR" > logfiles.txt

  7. Except on IBM i, collect the log file header located in the "LogPath" directory from Step 6, for example:

    Linux & UNIX
    /var/mqm/log/MY!QMGR/active/amqhlctl.lfh

    Windows
    C:\Program Files (x86)\IBM\WebSphere MQ\log\MY!QMGR\active\amqhlctl.lfh

  8. Except on IBM i, make sure the drive or filesystem holding the WebSphere MQ logs is not full, especially if you are using linear logs:

    Linux & UNIX
    sh> mount > mount.txt

    Windows
    C:\> DIR C: > disk.txt

  9. Except on IBM i, run the WebSphere MQ amqldmpa program to gather details about the logger. Make sure the output file location is writeable to the queue manager:

    Linux & UNIX
    sh> amqldmpa -m MY.QMGR -c H -d 8 -f /tmp/logdmpa.txt

    Windows
    C:\> amqldmpa -m MY.QMGR -c H -d 8 -f C:\TEMP\logdmpa.txt

  10. On IBM i only, use the mqs.ini file to find the "Library" value for the queue manager and display its contents. Alternatively, display library "QM*" and select your queue manager from the list in order to display its contents:

    IBM i Command Line
    ===> WRKLIB LIB(QMMY.QMGR)

    ===> WRKLIB LIB(QM*)

  11. On IBM i only, use the Library name from the previous step to work with your queue manager journals. Save the output, then use PF17 to display attached journal receivers and save the output from those screens. For example, if your queue manager library is QMMY.QMGR:

    IBM i Command Line
    ===> WRKJRNA JRN(QMMY.QMGR/AMQAJRN)
    Then press F17=Display attached receiver attributes


  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.

  2. On platforms other than IBM i, you may optionally print the contents of a linear log in order to determine why the logs are filling or to observe the sequence of events logged inside them. The log dump utility requires that you stop the queue manager. You must also provide the path to the logs, which is available in the qm.ini file as the "LogPath" value:

    Linux & UNIX
    sh> endmqm -i MY.QMGR
    sh>
    dmpmqlog -b -m MY.QMGR -f /var/mqm/log/MY!QMGR > /tmp/dmpmqlog.txt

    Windows
    C:\> endmqm -i MY.QMGR
    C:\> dmpmqlog -b -m MY.QMGR -f "C:\Program Files (x86)\IBM\WebSphere MQ\log\MY!QMGR" > %TEMP%\dmpmqlog.txt



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

  1. Review the IBM Support Assistant findings.
  2. Search the WebSphere MQ Support Portal for more information.
  3. Review the advice on managing log files if you use linear logging.
  4. Use IBM Service Request to open a problem record with IBM.
  5. 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
Recovery

Software version:

6.0, 7.0, 7.1, 7.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, UNIX

Software edition:

All Editions

Reference #:

1632016

Modified date:

2014-04-18

Translate my page

Machine Translation

Content navigation