Collect IBM MQ Mustgather data to solve logging and recovery problems on Linux, UNIX, Windows and IBM i

Technote (troubleshooting)


Problem(Abstract)

An IBM MQ queue manager is reporting errors logging data or recovering information from its logs, and you need to collect Mustgather data to find a solution.

Environment

These instructions apply only to IBM MQ 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 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:

Resolving the problem

Please answer these questions about the problem and then follow the steps below:

  • What logging or recovery problem did you observe on the system?
  • What time did the logging or recovery problem start and when did it stop?
  • What other details can you provide to help determine the cause of the problem?


Step 1: Generate Data


If the logging or recovery problem is happening right now, or if you can reproduce it, generate data to provide more information about the problem:


  1. Generate a trace of the queue manager while the problem is happening. Consider gather a high detail trace if you have plenty of disk space:



  2. On Linux, UNIX and Windows systems, dump the contents of the queue manager logs. This is particularly useful if you suspect a problem with the amount of data being logged. Please note that you must stop the queue manager in question in order to dump its logs, and you must also provide the log path for the queue manager, which is available as the "LogPath" attribute in its qm.ini file. For example:

    1. Dumping logs for queue manager QMA on Linux and UNIX


      sh> endmqm -i QMA
      sh> dmpmqlog -b -m QMA -f /var/mqm/log/QMA > /tmp/QMA.dmpmqlog.txt
      sh> strmqm QMA

      Dumping logs for queue manager QMA on Windows


      C:\> endmqm -i QMA
      C:\> dmpmqlog -b -m QMA -f "C:\ProgramData\IBM\MQ\log\QMA" > %TEMP%\QMA.dmpmqlog.txt
      C:\> strmqm QMA


  3. On Linux and UNIX systems, save the output from the mqconfig command. If you are running IBM MQ 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


  1. If you gathered these files in Step 1, place the dmpmqlog output and the mqconfig data directly in the top-level MQ errors directory. Both the runmqras automation tool and the manual collection steps below collect files found there.


  2. Collect data automatically with the runmqras command if you are running IBM MQ 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, logger and trace sections, and to specify your PMR number:

    1. Collecting runmqras output from queue manager QMA


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


  3. Alternatively, collect the MQ data manually.

    Collecting MQ data manually


    1. 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 InstallationX

      Windows


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


    2. Record the MQ version and maintenance level.


    3. Record the operating system version and maintenance level.


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


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

      Linux and UNIX


      sh> dspmqinst > /tmp/dspmqinst.txt

      Windows


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


    6. On MQ server installations, 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


    7. On MQ server installations, record the 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


    8. On Linux, UNIX and Windows systems, list the contents of the queue manager LogPath directory. For example:

      Listing logs for queue manager QMA on Linux and UNIX


      sh> ls -ltR /var/mqm/log/QMA > /tmp/QMA.logfiles.txt

      Listing log files for queue manager QMA on Windows


      C:\> DIR /s "C:\ProgramData\IBM\MQ\log\QMA" > %TEMP%/QMA.logfiles.txt


    9. On Linux, UNIX and Windows systems, make sure the file system or disk holding the logs is not full. For example:

      Displaying file systems on Linux and UNIX


      sh> df -k > /tmp/filesystems.txt

      Displaying disk usage on Windows


      C:\> DIR C: > %TEMPT/diskuage.txt


    10. On Linux, UNIX and Windows systems, run the amqldmpa program against the queue manager to gather details about the logger. The command must be run by an MQ administrator and the output file should be in a location which is writeable by the queue manager. For example:

      Dumping logger information for queue manager QMA on Linux and UNIX


      sh> amqldmpa -m QMA -c H -d 8 -f /tmp/QMA.amqldmpa.logger.txt

      Dumping logger information for queue manager QMA on Windows


      C:\> amqldmpa -m QMA -c H -d 8 -f %TEMP%\QMA.amqldmpa.logger.txt


    11. On all systems, run the amqldmpa program against the queue manager to gather details about the persistence layer. The command must be run by an MQ administrator and the output file should be in a location which is writeable by the queue manager. For example:

      Dumping persistence information for queue manager QMA on Linux and UNIX


      sh> amqldmpa -m QMA -c A -d 8 -f /tmp/QMA.amqldmpa.dap.txt

      Dumping persistence information for queue manager QMA on Windows


      C:\> amqldmpa -m QMA -c A -d 8 -f %TEMP%\QMA.amqldmpa.dap.txt

      Dumping persistence information for queue manager QMA in the IBM i Qshell


      ===> /QSYS.LIB/QMQM.LIB/AMQLDMPA.PGM -m QMA -c A -d 8 -f /tmp/QMA.amqldmpa.dap.txt


    12. On Linux, UNIX and Windows systems, collect the log file header, amqhlctl.lfh, which is found in the active subdirectory of the queue manager's LogPath. For example:

      Log file header for queue manager QMA on Linux and UNIX


      /var/mqm/log/QMA/active/amqhlctl.lfh

      Log file header for queue manager QMA on on Windows


      C:\ProgramData\IBM\MQ\Log\QMA\active\amqhlctl.lfh


    13. On IBM i only, find the "Library" attribute from the queue manager's qm.ini file and display its contents. Alternatively, display library "QM*" and select your queue manager from the the list to display its contents. For example:

      Display the library for queue manager QMA on IBM i


      ===> WRKLIB LIB(QMQMA)

      Display the library for all queue manager


      ===> WRKLIB LIB(QM*)


    14. On IBM i only,use the same "Library" value to work with the queue manager's journals. Save the output, then use F17 to display attached journal receives and save the output form those screens as well. For example:

      Display the journals and journal receivers for queue manager QMA on IBM i


      ===> WRKJRNA JRN(QMQMA/AMQAJRN)
      Then press F17=Display attachd receiver attributes


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


Step 3: Send Data to IBM


  1. Send your data to the IBM ECuRep repository by email to websphere_support@ecurep.ibm.com, by standard or secure HTTP or FTP. or by using the IBM Secure Diagnostic Data Upload Utility (SDDUU) Java application.


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



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


Product Alias/Synonym

WebSphere MQ WMQ

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere MQ
Problem Determination

Software version:

6.0, 7.0, 7.1, 7.5, 8.0

Operating system(s):

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

Software edition:

All Editions

Reference #:

1632016

Modified date:

2014-05-23

Translate my page

Machine Translation

Content navigation