Want these instructions for Windows? Read Collecting MQ Light server diagnostics on Windows.


  1. Add the MQ Light API diagnostic commands to the path.
    The following example shows an installation in opt/mqlight-production-1.0:
    sh> PATH=/opt/mqlight-production-1.0/runtime/bin:$PATH sh> export PATH
  2. Start tracing with the strmqtrc command.
    This can be found in /runtime/bin. No parameters are required.
    C:\> strmqtrc
  3. Reproduce the problem while trace is active.
  4. When the problem occurs, stop tracing immediately using endmqtrc.
    For example:
    sh> endmqtrc -a
  5. 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 AMQ*.TRC.
    sh> cd /appdata/mqm/trace sh> dspmqtrc AMQ*.TR?
  6. 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.
    For example:
    sh> cd /appdata/mqm/trace sh> rm -f AMQ*.?.TR?
  7. Specify the trace section name on the runmqras command to collect your MQ Light API traces and other data. If the traces are very large, you can use the -workdirectory option 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
  8. Clean up the /appdata/mqm/trace directory to reclaim space:
    sh> cd /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:

  • ${MQ_LIGHT_ROOT}/appdata/mqm/errors
  • ${MQ_LIGHT_ROOT}/appdata/mqm/qmgrs/DEFAULT/errors
  • ${MQ_LIGHT_ROOT}/appdata/mqm/trace
  • ${MQ_LIGHT_ROOT}/appdata/wlp/servers/defaultServer/logs

Join The Discussion

Your email address will not be published.