IBM Support

Collect IBM MQ MustGather data to solve Microsoft Cluster Server (MSCS) problems on Windows



An IBM MQ queue manager is not failing over properly under Microsoft Cluster Server (MSCS), and you need to collect MustGather data to find a solution.


These instructions apply only to IBM MQ V9.1, V9.0 and V8.0, and WebSphere MQ V7.5, V7.1, V7.0 and V6.0 on Windows:

Resolving The Problem

Please answer these questions about the problem and then follow the steps below:
  • What MSCS problem did you observe on the cluster?
  • What time did the MSCS problem start and when did it stop?
  • What are the names and addresses of the cluster members?
  • Is this a new cluster, or were there any changes made to either cluster member before the problem started?

Step 1: Generate Data


It is essential to generate data at the time of the cluster failure to provide more information about the problem:


  1. Generate an MSCS cluster log after the problem occurs.  On one of the cluster members:
    1. Start PowerShell (or run the 'PowerShell' command in a DOS prompt).
    2. Go to the MQ top-level errors directory, for example:

      PS C:\> CD $env:ProgramData\IBM\MQ\Errors
    3. Run the Get-ClusterLog cmdlet to generate cluster logs for the nodes in the cluster:

      PS C:\ProgramData\IBM\MQ\Errors> Get-ClusterLog -Destination . 

  2. Generate a high detail MQ trace on both members of the cluster during the problem. For example:

    1. C:\> strmqtrc -e -t all -t detail
      C:\> endmqtrc -a


Step 2: Collect Data

  1. Run the MQ amqmsysn utility to display information about all MQ executables and libraries on both members of the cluster. Use the "To File..." button to save this information to a file, for example %TEMP%\MQ.exeinfo.txt:

    Collecting MQ executable information from both cluster members


  2. Show the registry checkpoints on both members of the cluster:
    1. C:\> CLUSTER RESOURCE /CHECKPOINTS > %TEMP%\Cluster.checkpoints.txt
  3. Checking registry checkpoints on both cluster members

  4. Save all three Event Viewer logs (System, Application and Security) on both members of the cluster.

  5. Place the cluster logs, error logs and command outputs from Steps 1 and 2 directly in the top-level MQ errors directory on each member of the cluster. Both the runmqras automation tool and the manual collection steps below collect files found there.
  6. Collect data automatically with the runmqras command on both cluster members if you are running IBM MQ V9.0 or V8.0, or WebSphere MQ V7.5, V7.1.0.1 or later, or V7.0.1.8 or later. Be sure to collect the runmqras trace section, and to specify your PMR number:

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

  7. Alternatively, collect the MQ data manually on both cluster members.

    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:


      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:

      C:\> dspmqinst > %TEMP%/dspmqinst.txt
    6. 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, 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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Component":"Problem Determination","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.1;9.0;8.0;7.5;7.1;7.0;6.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym


Document Information

Modified date:
19 February 2019