Starting to collect message flow accounting and statistics data

Before you start:

You can start collecting message flow accounting and statistics data for an active broker at any time.

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.

    See Setting message flow accounting and statistics accounting origin for further details.

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

      Where, brokerName, executionGroupLabel, and messageFlowLabel are 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 # to receive both snapshot and archive).

    • SMF (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, enter:

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

    Using SDSF on z/OS, enter:

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

    Refer to the mqsichangeflowstats command for further examples.

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

Next:

Related concepts
Message flow accounting and statistics data
Message flows overview
Related tasks
Setting message flow accounting and statistics accounting origin
Stopping message flow accounting and statistics data collection
Viewing message flow accounting and statistics data collection parameters
Modifying message flow accounting and statistics data collection parameters
Resetting message flow accounting and statistics archive data
Developing message flows
Related reference
Issuing commands to the z/OS console
mqsichangeflowstats command
mqsireportflowstats command
Message flow accounting and statistics data