IBM Support

Collect troubleshooting data for a shared queues problem in IBM MQ for z/OS

Troubleshooting


Problem

You are experiencing a shared queues problem in IBM MQ for z/OS. You would like to know what documentation you must collect (MustGather) so that the IBM MQ Support team can diagnose your problem. If you gather this documentation before you contact support, it expedites the troubleshooting process and saves you time.

Environment

These instructions apply only to IBM MQ on z/OS. Refer to the IBM MQ Read First page and the Shared Queues Troubleshooting guide for self-help on this topic:


 

Resolving The Problem

Answer these questions about the problem and then follow the steps to generate, collect, and send data to IBM:

  • What is the name of the Shared Queue having a problem?
  • What is the name of the IBM MQ Coupling Facility structure(CFSTRUCT) associated with the problematic Shared Queue?
  • What is the error message associated with the problem?
  • What is the name of the Queue Sharing Group?
  • What time did the problem occur?
  • Which queue manager in the queue sharing group is involved?

Step 1: Generate Data

If the Shared Queue problem is reproducible or is happening right now, generate data to provide more information about the problem:
  1. Generate a GTF trace while the problem is happening.
     
  2. Generate a MSTR internal trace while the problem is happening.
     
  3. Generate a CHIN trace while the problem is happening.

Step 2: Collect Data

The following steps include an example of dumping both application structure and the IBM MQ Administration structure.

  1. Record the version, release, and maintenance levels your software:
    • IBM MQ: find the version in the CSQY000I message in the MSTR job log
    • The z/OS operating system: find the version in the output of /D IPLINFO in SDSF
    • Any other products involved with the problem: look for the version in the job log for the product
       
  2. Collect the IBM MQ MSTR and CHIN joblogs. Optionally, collect the syslog.
     
  3. Collect a z/OS LOGREC report.
     
  4. Save any z/OS dumps you generated from IBM MQ.
     
  5. Collect Coupling Facility Structure dumps for the application Structure and the IBM MQ Administration Structure:
/DUMP COMM=(title)
/R nnn,SDATA=(ALLNUC,LPA,PSA,RGN,SQA,LSQA,TRT,CSA,XESDATA,COUPLE,GRSQ),CONT
/R nnn,JOBNAME=(ssidMSTR),CONT
/R nnn,STRLIST=(STRNAME=QSGnameStructurename,(LISTNUM=ALL,
ADJUNCT=CAPTURE,ENTRYDATA=UNSER),EVENTQS,(EMCONTROLS=ALL),
/R nnn,STRNAME=QSGnameCSQ_ADMIN,(LISTNUM=ALL,ADJUNCT=CAPTURE,
ENTRYDATA=UNSER),EVENTQS,(EMCONTROLS=ALL)),END


where "ssid" is the subsystem ID for the queue manager.
An example of "QSGnameStructurename" is QSG1APPLICATION where QSG1 is the queue sharing group name.
An example of "QSGnameCSQ_ADMIN" is QSG1CSQ_ADMIN

Following is an example of dumping the application structure solely.

/DUMP COMM=(title)
/R xx,STRLIST=(STRNAME=QSGnameStructurename,(LISTNUM=ALL,
ADJUNCT=CAPTURE,ENTRYDATA=UNSER),EVENTQS,(EMCONTROLS=ALL))

An example of "QSGnameStructurename" is QSG1APPLICATION where QSG1 is the queue sharing group name.
 

Step 3: Send Data to IBM

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"ARM Category":[{"code":"a8m0z0000001iitAAA","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"ARM Category":[{"code":"a8m0z0000001iitAAA","label":"Troubleshooting"}],"Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]

Product Synonym

IBM MQ WebSphere MQ WMQ

Document Information

Modified date:
01 May 2023

UID

swg21177414