IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

mqsireporttrace command - Windows, Linux, and UNIX systems

Use the mqsireporttrace command to display the trace options currently in effect. Trace can be run only against a broker, or any of its resources.

Syntax

Report broker-wide active user and service trace settings


>>-mqsireporttrace--brokerName--+------+-----------------------><
                                +- -u -+   
                                '- -t -'

Report individual component user trace settings


>>-mqsireporttrace--brokerName-- -u -- -e --isName-------------->

>--+-------------------+--+----------------------+-------------->
   '- -f --messageFlow-'  '- -k -applicationName-'   

>--+------------------+----------------------------------------><
   '- -y -libraryName-'

Report individual component service trace settings


>>-mqsireporttrace--brokerName-- -t ---------------------------->

>--+- -b --------------------------------+---------------------->
   '- -e --isName--+-------------------+-'   
                   '- -f --messageFlow-'     

>--+----------------------+--+------------------+--------------><
   '- -k -applicationName-'  '- -y -libraryName-'

Report Trace nodes


>>-mqsireporttrace--brokerName-- -n -- -e --isName-------------->

>--+-------------------+--+----------------------+-------------->
   '- -f --messageFlow-'  '- -k -applicationName-'   

>--+------------------+----------------------------------------><
   '- -y -libraryName-'

Parameters

brokerName

(Required) The name of a broker; this name is case sensitive on Linux and UNIX systems.

-e isName

(Required for component user trace, otherwise optional) The label of the integration server for which a report is required.

-f messageFlow

(Optional) The label of the message flow for which a report is required. This option is valid only if you have specified an integration server.

-k applicationName

(Optional) This parameter specifies the name of the application that contains the message flow for which trace options are displayed.

When you set this parameter, you must also set the -f (message flow) parameter. To display trace options for a named message flow in a specific application, set the -k and -f parameters.

You can use this parameter with the -y (library name) parameter to specify that the message flow is contained in a library referenced by the application.

-u

(Required for component user trace, otherwise optional) Derive report information from the user trace.

-y libraryName

(Optional) This parameter specifies the name of the library that contains the message flow for which trace options are displayed.

When you set this parameter, you must also set the -f (message flow) parameter. To display trace options for a named message flow in a specific library, set the -y and -f parameters.

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.

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

Additional parameters exclusive to Trace nodes

-n: Report the setting of the Trace node switch. One BIP message is reported for each message flow.

Examples

To derive report information from service trace for integration server exgrp1 in broker IB9NODE, enter the command:

mqsireporttrace IB9NODE -t -e "exgrp1"

To report the setting of the Trace node switch for integration server exgrp1 in broker IB9NODE, enter the command:

mqsireporttrace IB9NODE -n -e "exgrp1"

To report all active trace settings in broker IB9NODE, enter the command:

mqsireporttrace IB9NODE

an28400_.htm |

Last updated Friday, 21 July 2017