Want these instructions for Windows? Read Collecting MQ Light server diagnostics on Windows.
- Add the MQ Light API diagnostic commands to the path.
The following example shows an installation in
sh> PATH=/opt/mqlight-production-1.0/runtime/bin:$PATH sh> export PATH
- Start tracing with the
This can be found in
. No parameters are required.
- Reproduce the problem while trace is active.
- When the problem occurs, stop tracing immediately using
sh> endmqtrc -a
- The trace files generated by the MQ Light API are binary, and must be formatted before they can be read. The binary trace files are named
/appdata/mqm/trace sh> dspmqtrc AMQ*.TR?
- Save a copy of the binary trace files while you are working with IBM support, but do not send both binary and formatted traces to IBM. IBM will only require the formatted trace files.
/appdata/mqm/trace sh> rm -f AMQ*.?.TR?
- Specify the trace section name on the
runmqrascommand to collect your MQ Light API traces and other data. If the traces are very large, you can use the
-workdirectoryoption to package the files in a directory with plenty of free space.
The following example collects data about queue manager QMA for an IBM Problem Management Record 12345,67R,890:
sh> runmqras -section trace,defs -pmrno 12345,67R,890 -workdirectory /var/bigdata
- Clean up the
directory to reclaim space:
/appdata/mqm/trace sh> rm -f AMQ*.TR? AMQ*.FMT
What to do next
For reference, the MQ Light API outputs diagnostic information to the following locations: