mqsireporttrace command

Supported platforms

  • Windows
  • Linux and UNIX systems
  • z/OS

Purpose

Use the mqsireporttrace command to display the trace options currently in effect. This command is valid for:
  • User trace. Specify the -u option.

    On z/OS, user trace is run against a specific execution group for a broker. You can narrow the command down further to trace a specific message flow.

  • Service trace. Specify the -t option. Use this option only if directed to do so by the action described in a BIPxxxx message, or by your IBM Support Center.

    On z/OS, service trace can be run for a specific execution group (like user trace). Unlike user trace, service trace can also be run against an active agent (that is, a broker or User Name Server).

If you specify a broker, or any of its resources (execution group or message flow), you must have deployed them before you can query trace settings.

Syntax

Windows platforms, Linux, and UNIX systems

User trace

Service trace

z/OS

User trace

Service trace

Parameters

component
(Required - Windows platforms, Linux, and UNIX systems) The name of the broker for which options are reported, or the fixed value UserNameServer. Both values are case sensitive on Linux and UNIX systems.
-u
(Required for user trace) Derive report information from the user trace.
-e egroup
(Required for user trace, otherwise optional) The label of the execution group for which a report is required. This is valid only if you have specified a broker as the component.

On z/OS this name is case sensitive. Include the name in single quotes if it contains mixed-case characters.

-f mflow
(Optional) The label of the message flow for which a report is required. This is valid only if you have specified both a broker as the component and an execution group.

On z/OS this name is case sensitive. Include the name in single quotes if it contains mixed-case characters.

Additional parameters exclusive to service trace

Use these options only when directed to do so by your IBM Support Center or by a BIPxxxx message.

-t
(Required for service trace) Derive report information from the service trace.
-b
(Alternative to -e on all platforms) Request a report for agent function.

Authorization

The user ID used to issue the command must have mqbrkrs authority.

Responses

  • BIP8002 Selected flags incompatible (z/OS only)
  • BIP8003 Duplicate flag detected (z/OS only)
  • BIP8013 Component does not exist
  • BIP8020 Unable to access database
  • BIP8029 Broker not configured
  • BIP8032 Unable to connect to queue (Windows platforms, Linux, and UNIX systems only)
  • BIP8033 Unable to send XML message
  • BIP8035 Response not received within time-out
  • BIP8036 Negative response received
  • BIP8037 Unsupported flag selected
  • BIP8038 Unsupported command option
  • BIP8039 Execution group not available
  • BIP8040 Unable to connect to database
  • BIP8045 Message flow not available
  • BIP8158 Invalid format for command (z/OS only)
  • BIP8159 Unknown parameter "..." (z/OS only)

Examples

Windows platforms, Linux, and UNIX systems:
mqsireporttrace BrokerA -t -e "exgrp1"
z/OS:
F MQP1BRK,reporttrace t=yes,e='exgrp1'
Related tasks
Using trace