Collect troubleshooting data for a performance problem in WebSphere MQ for z/OS

Gather this MustGather data before contacting IBM Support:

Collecting general data for all problems
Collecting troubleshooting data for this problem
Troubleshooting hints and tips
Exchanging data with IBM Support

Go back to: WebSphere MQ (MustGather) Read First

Collecting general data for all problems

A complete description of the problem, including the following:

• WebSphere MQ version, release, and maintenance level
• Operating system version, release, and maintenance level
• Related products version, and release levels if applicable

  Back to top

Collecting troubleshooting data for this problem

Required (MustGather) data:

• Job logs.
• Dumps generated at point of failure.
• Logrec (JCL to get software LOGREC report).
• Dumps taken at the point of failure.
• Provide topology details for all distributed queueing related problems. Include the following information for the queue managers that are having the failure:
  • A general description of the distributed queueing environment.
  • Operating system version and release.
  • WebSphere MQ version and release.
  • WebSphere MQ Fix Pack level.
  • Detailed description of the testcase. It is important that the WebSphere MQ team completely understand your environment, the application, and the circumstances in which the performance degradation occurs. Provide a complete listing of the details regarding the failure.

Optional (MustGather) data:

• GTF Trace
• MSTR Internal Trace
• CHIN Trace
• REXX utility to do compact LISTCAT for WebSphere MQ datasets and report the size and number of DASD stripes -- this information will be useful if I/O to active logs is a factor in the problem.

Back to top

Troubleshooting hints and tips

• Review Webcast replay: WebSphere MQ for z/OS - Performance Topics
• Search the WebSphere MQ support site for known problems using symptoms like the message number and error codes or using the term "performance".
• Check for CSQP020E messages logged in the MQ MSTR joblog. This would indicate a problem with the buffer pool.
• Set the INDXTYPE for queues if appropriate. See Performance issues getting messages from a queue with a large CURDEPTH.
• Avoid large units of work with many uncommitted gets or puts.
• Apply TCP/IP fix PM73355 for throughput problems if you are using z/OS 1.13.
• Review WebSphere MQ Family - Performance Reports.
• Review RMF reports to look for CPU, I/O, or storage constraints.
• Review SMF data to look for problem areas or narrow down the scope of the problem. See Monitoring performance and resource usage. Use a performance monitor or SupportPac MP1B to interpret accounting (SMF 116) and statistics (SMF 115) data. Documentation provided with the SupportPac provides assistance with interpretation.
• Higher CPU may be seen in the getting job's address space after migration from WebSphere MQ for z/OS V5 to V6 or higher.

Learn more about this component

• SupportPac MP16: WebSphere MQ for z/OS - Capacity planning & tuning
• SupportPac MP1B: WebSphere MQ for z/OS V7.0 - Interpreting accounting and statistics data
• WebSphere MQ Family - Performance Reports
• WebSphere MQ for z/OS Concepts and Planning Guide
• Library and Information centers

  Back to top

Exchanging data with IBM Support

• See Exchanging information with IBM Technical Support for FTP and email instructions using the IBM Enhanced Customer Data Repository (ECuRep). Use the /toibm/mvs directory for uploading files.
• Go to the Service Request page to open or update a problem.
  Note: Always update your Service Request (problem record) to indicate that data has been sent.

If you need to speak to an IBM technical support representative call your country representative. If you need to speak to an IBM technical support representative in the US call 1-800-IBM-SERV.

Back to top