Troubleshooting
Problem
You are experiencing a performance problem in IBM MQ for z/OS. The IBM Software Support Handbook states that analyzing performance is one of the activities that often require some form of Advance Support Offering. If analysis reveals a suspected defect in the product, you would like to know what documentation you must collect (MustGather) so that the IBM MQ Support team can diagnose your problem.
Environment
These instructions apply only to IBM MQ for z/OS. Refer to the IBM MQ Read First page for instructions on other operating systems and to the MQ Performance Troubleshooting guide for self-help on this topic:
Resolving The Problem
Please answer these questions about the problem and then follow the steps below:
- What effect is the problem having, for instance high CPU or response delays?
- When did the problem first occur?
- Was software or hardware maintenance applied?
- Is the problem a one time failure or reoccurring?
- What are the names of the queue managers, queues, channels, or other jobs involved in the problem?
- Have you reviewed the Troubleshooting link above?
Step 1: Generate Data
If the problem is reproducible or is happening right now, generate data to provide more information about the problem:
- Generate a GTF trace while the problem is happening.
- Generate a MSTR internal trace and capture it in a dump while the problem is happening.
- Generate a CHIN trace and capture it in the same dump with the MSTR trace while the problem is happening.
- If the network performance is in question, generate a z/OS TCP/IP packet trace and an MQ CHIN trace simultaneously at the other end of the channel while the problem is happening.
Step 2: Collect Data
- Record the version, release, and maintenance levels your software:
- MQ: find the version in the CSQY000I message in the MSTR joblog
- 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 joblog for the product
- Collect the MQ MSTR and CHIN joblogs. Optionally, collect the syslog.
- Collect the z/OS dump you generated when collecting the traces.
- Collect a z/OS LOGREC report.
Step 3: Send Data to IBM
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!
- See Exchanging information with IBM Software Support for FTP and email instructions.
- Go to the IBM My Support site to open or update a case.
Note: Always update your case to indicate that data was sent
- If you need to speak with IBM Software Support, contact your country representative. If you need to speak with IBM Software Support in the US, you can call 1-800-IBM-SERV.
Related Information
[{"Type":"SW","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"ARM Category":[{"code":"a8m0z00000008LcAAI","label":"Performance"},{"code":"a8m0z0000001iitAAA","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Version(s)"},{"Type":"SW","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"ARM Category":[{"code":"a8m0z00000008LcAAI","label":"Performance"},{"code":"a8m0z0000001iitAAA","label":"Troubleshooting"}],"Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Version(s)"}]
Product Synonym
IBMMQ WMQ MQ
Was this topic helpful?
Document Information
Modified date:
10 April 2021
UID
swg21291192