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

Starting collection of message flow accounting and statistics data with the mqsichangeflowstats command

You can use the mqsichangeflowstats command to start collecting message flow accounting and statistics data for an active broker at any time. You can specify what type of statistics you want to collect, and where to send the data.

Before you start:

Select the granularity of the data that you want to be collected by specifying the appropriate parameters on the mqsichangeflowstats command. You must request statistics collection on a broker basis. If you want to collect information for more than one broker, you must issue the corresponding number of commands.

To start collecting message flow accounting and statistics data:

  1. Identify the broker for which you want to collect statistics.
  2. Decide the resource for which you want to collect statistics. You can collect statistics for a specific execution group, or for all execution groups for the specified broker.
    • If you indicate a specific execution group, you can request that data is recorded for a specific message flow or all message flows in that group.
    • If you specify all execution groups, you must specify all message flows.
  3. Decide if you want to collect thread-related statistics.
  4. Decide if you want to collect node-related statistics. If you do, you can also collect information about terminals for the nodes.
  5. Decide if you want to associate data collection with a particular accounting origin. This option is valid for snapshot and archive data, and for message flows and execution groups. However, when active, you must set its origin value in each message flow to which it refers. If you do not configure the participating message flows to set the appropriate origin identifier, the data collected for that message flow is collected with the origin set to Anonymous.

    For more information, see Setting message flow accounting and statistics accounting origin.

  6. Decide the target destination.
    • User trace log (the default setting). The output data can be processed using mqsireadlog and mqsiformatlog.
    • XML format publication message. If you chose this target destination, register the following topic for the subscriber:
      $SYS/Broker/brokerName/StatisticsAccounting/recordType/executionGroupLabel/messageFlowLabel

      where brokerName, executionGroupLabel, and messageFlowLabel represent the broker, execution group, and message flow on which you want to receive data. recordType is the type of data collection on which you want to receive publications (snapshot, archive, or the number sign (#) to receive both snapshot and archive). The value that you specify for record type is case sensitive; therefore, if you choose to receive snapshot data, set the record type to SnapShot.

    • z/OS platformSMF (on z/OS® only)

  7. Decide the type of data collection that you want:
    • Snapshot
    • Archive

    You can collect snapshot and archive data at the same time, but you have to configure them separately.

  8. Issue the mqsichangeflowstats command with the appropriate parameters to reflect the decisions that you have made.

    For example, to turn on snapshot data for all message flows in the default execution group for BrokerA, and include node data with the basic message flow statistics, use the following command:

    mqsichangeflowstats BrokerA -s -e default -j -c active -n basic    

    z/OS platformUsing SDSF on z/OS, enter:

    /F BrokerA,cs s=yes,e=default,j=yes,c=active,n=basic    

    For more examples, see mqsichangeflowstats command.

When the command completes successfully, data collection for the specified resources is started:

  • If you have requested snapshot data, information is collected for approximately 20 seconds, and the results are written to the specified output.
  • If you have requested archive data, information is collected for the interval defined for the broker (on the mqsicreatebroker or mqsichangebroker command, or by the external timer facility ENF). The results are written to the specified output, the interval is reset, and data collection starts again.
Notices | Trademarks | Downloads | Library | Support | Feedback

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

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:09


Task topicTask topic | Version 8.0.0.7 | ac18930_