[z/OS]

Collecting information for performance problems on z/OS

If you need assistance to resolve a performance problem on IBM® MQ for z/OS®, you might need to collect troubleshooting information to include with your support case to help find a solution to the problem.

Before you begin

Before you start this task, answer the following questions about the problem:
  • 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 information in Troubleshooting MQ performance problems.

About this task

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 and you can reproduce the performance problem or the problem is happening right now, you can generate data to provide more information about the problem so that the IBM MQ Support team can diagnose your problem.

After collecting the troubleshooting information, you can send it to IBM.

Procedure

  1. If you can reproduce the performance problem or the problem 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 and capture it in a dump while the problem is happening.
    3. Generate a CHIN trace and capture it in the same dump with the MSTR trace while the problem is happening.
    4. 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.
  2. Collect the data.
    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.
      • For 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 and, optionally, collect the syslog.
    3. Collect the z/OS dump that you generated when collecting the traces.
    4. Collect a z/OS LOGREC report.
      See A LOGREC report and SYS1.LOGREC information on z/OS.
  3. Use the AMATERSE utility before uploading to ECUREP, and ensure you specify the case number with which the data is associated.

    For more information, see Using AMATERSE in the z/OS Communications Server: IP Diagnosis Guide.

  4. Send the information that you have collected to IBM.

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

    For FTP and email instructions, see Exchanging information with IBM Software Support.

    To open or update a case, go to the IBM My Support site.
    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 Support in the US, you can call 1-800-IBM-SERV.