Collect WebSphere MQ MustGather data to solve triggering problems on HP NonStop Server

Resolving The Problem

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

• What triggering problem did you observe on the system?
• What time did the triggering problem start and when did it stop?
• Which queue did not trigger, and which channel or processs should have been started?

Step 1: Generate Data

If the triggering problem is reproducible or is happening right now, generate data to provide more information about the problem:

1. Generate a trace of the queue manager when the triggering problem occurs.

Step 2: Collect Data

1. Record the MQ version and maintenance level.



2. Record the operating system version and maintenance level.



3. Use runmqsc to display the queue manager, its queues, process definitions, channels, and their status. If any command gives an error, carry on with the others:



Displaying queues, channels and process objects


DISPLAY QMGR ALL
DISPLAY QLOCAL(*) ALL
DISPLAY QALIAS(*) ALL
DISPLAY QREMOTE(*) ALL
DISPLAY PROCESS(*) ALL
DISPLAY CHANNEL(*) ALL
DISPLAY CHSTATUS(*) ALL




4. Use the sdcp script to 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, or by standard or secure HTTP or FTP.



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.




A good description of the problem and the data is the most important information you can provide to IBM. Please do not send data without providing a description!



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.

Back to top