Use trace for problem determination on z/OS
There are different trace options that can be used for problem determination with IBM MQ . Use this topic to understand the different options and how to control trace.
The trace facilities available with IBM MQ for z/OS are:
- The user parameter (or API) trace
- The IBM internal trace used by the support center
- The channel initiator trace
- The line trace
Use the following links to find out how to collect and interpret the data produced by the user parameter trace, and describes how to produce the IBM internal trace for use by the IBM support center. There is also information about the other trace facilities that we can use with IBM MQ.
- Control the GTF for the z/OS system
- Control the IBM MQ trace for each queue manager subsystem for which we want to collect data
- Formatting and identifying the control block information on z/OS
- Interpreting the trace information on z/OS
If trace data is not produced, check the following:
- Was the GTF started correctly, specifying EIDs 5E9, 5EA, and 5EE on the USRP option?
- Was the START TRACE(GLOBAL) command entered correctly, and were the relevant classes specified?
For more information about other trace options available on z/OS, see Other types of trace on z/OS.
- The MQI call and user parameter, and GTF on z/OS
Use this topic to understand how to control the z/OS generalized trace facility (GTF) and IBM MQ trace. - Other types of trace on z/OS
There are other trace facilities available for problem determination. Use this topic to investigate channel initiator trace, line trace, CICS adapter trace, SSL trace, and z/OS trace.
Parent topic: Use trace
Related concepts
- Use trace on UNIX and Linux systems
- Use trace with IBM MQ server on IBM i
- Tracing TLS: runmqakm, strmqiqm, and runmqckm functions
- Tracing additional IBM MQ Java components
Related reference