WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

mqsireportflowmonitoring command - Windows, Linux and UNIX systems

Use the mqsireportflowmonitoring command on Windows, Linux and UNIX systems to display the current options for monitoring that have been set by the mqsichangeflowmonitoring command.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-mqsireportflowmonitoring--BrokerName------------------------->

>--+-| SingleFlow |----+---------------------------------------><
   '-| MultipleFlows |-'   

SingleFlow

|-- -e--ExecutionGroupName-- -f--MessageFlow-------------------->

>----+-----------------------------+----------------------------|
     +- -n-------------------------+     
     +- -a-------------------------+     
     |      .-,------------------. |     
     |      V                    | |     
     +- -s----EventSourceAddress-+-+     
     +- -x-- -p--File--------------+     
     +- -k --applicationName-------+     
     '- -y --libraryName-----------'     

MultipleFlows

|--+- -e --ExecutionGroupName--+- -f --MessageFlow-+-+---------->
   |                           '- -j --------------' |   
   '- -g --------------------------------------------'   

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

Parameters

BrokerName
(Required) Specify the label of the broker, for which monitoring options are to be reported.
-a
(Optional) Report the flow-level monitoring properties and the properties of all event sources within the flow, whether configured or not.
-e ExecutionGroupName
(Required) Specify the name for the execution group, for which monitoring options are to be reported.

You must specify either -e or -g. If you do not specify one of these arguments you receive an error message.

-f MessageFlow
(Required) Specify the label for the message flow, for which monitoring options are to be reported.

You must specify either -f or -j. If you do not specify one of these arguments you receive an error message.

-g
(Required) Specifies that the command applies to all execution groups that belong to the broker.

You must specify either -e or -g. If you do not specify one of these arguments you receive an error message.

-j
(Required) Specifies that the command applies to all message flows that belong to the execution group.

You must specify either -f or -j. If you do not specify one of these arguments you receive an error message.

Note: If you set the -g option for all execution groups, you must use -j instead of -f.
-k applicationName
(Optional) This parameter specifies the name of the application that contains the message flow being monitored.

When you set this parameter, you must also set either the -f (message flow) parameter, or the -j (all message flows) parameter. To display monitoring options for a named message flow in a specific application, set the -k and -f parameters. To display monitoring options for all message flows in an application, set the -k and -j 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.

-n
(Optional) Report the flow-level monitoring properties and the properties of any configured event sources within the flow.
-p
(Optional unless -x is specified.) The file name to which the monitoring profile will be written, in XML format.
-s EventSourceAddress
(Optional) Report the flow-level monitoring properties and the properties of the specified event sources within the flow, whether configured or not.
You must provide a comma-separated list of the event source addresses for which monitoring options are to be reported. An event source address takes the form <node name>.<event source>, where <event source> is one of the following values:
  • 'terminal.<terminal name>'
  • 'transaction.Start'
  • 'transaction.End'
  • 'transaction.Rollback'

If a message flow contains two or more nodes with identical names, the event sources on those nodes cannot be accurately addressed. If this is attempted, behavior is undefined.

Note: <node name> is the label of the node as known by the broker runtime components. If the node is in a subflow the label reflects this. For example, flow A contains an instance of flow B as a subflow labeled 'myB'; flow B contains an instance of a Compute node labeled 'myCompute'. The <node name> for the Compute node is 'myB.myCompute'.
-x
(Optional; if you specify -x you must also specify the -p parameter.) Outputs the current monitoring properties for the specified message flow as a monitoring profile XML file.
-y libraryName
(Optional) This parameter specifies the name of the library that contains the message flow being monitored.

When you set this parameter, you must also set either the -f (message flow) parameter, or the -j (all message flows) parameter. To display monitoring options for a named message flow in a specific library, set the -k and -f parameters. To display monitoring options for all message flows in a library, set the -k and -j parameters.

Note:
  • If all flags are omitted, only the flow-level properties are reported.
  • Flags -n, -a, -s and -x can be used only when -f is present.
  • Flags -n, -a, -s and -x are alternatives and cannot be used together.

Examples

Request a report of the monitoring options for message flow "MyFlow1" in the execution group "default" for broker "BrokerA":
mqsireportflowmonitoring BrokerA -e default -f MyFlow1
Request a report of the current monitoring options for all message flows in all execution groups for broker "BrokerA" :
   mqsireportflowmonitoring BrokerA -g -j
Display monitoring options for all message flows in application application1 in execution group default:
mqsireportflowmonitoring MB8BROKER -e default 
     -k application1 -j 
Display monitoring options for message flow myflow1 in library library1, referenced by application application1, in execution group default:
mqsireportflowmonitoring MB8BROKER -e default 
     -y library1 -k application1 -f myflow1
For more examples, see Reporting monitoring settings.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:23


Reference topicReference topic | Version 8.0.0.7 | an37930_