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

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:

Ensure that you have created a message flow; for more information, see Creating a message flow.
Ensure that you have deployed a broker archive (BAR) file; for more information, see Deploying a broker archive file.
Read the concept topic, Message flow accounting and statistics collection options.

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:

Identify the broker for which you want to collect statistics.
Decide the resource for which you want to collect statistics. You can collect statistics for a specific integration server, or for all integration servers for the specified broker.
- If you indicate a specific integration server, you can request that data is recorded for a specific message flow or all message flows in that group.
- If you specify all integration servers, you must specify all message flows.
Decide if you want to collect thread-related statistics.
Decide if you want to collect node-related statistics. If you do, you can also collect information about terminals for the nodes.
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 integration servers. 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.
Decide the target destination. You can choose multiple destinations by specifying multiple comma-separated values for the output format property.
- 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/integrationServerLabel/messageFlowLabel
```
  where brokerName, integrationServerLabel, and messageFlowLabel represent the broker, integration server, 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.
- JSON publication message. Register the following topic for the subscriber:
```
$SYS/Broker/brokerName/Statistics/JSON/SnapShot/integrationServerName/applications/applicationName/libraries/libraryName/messageflows/messageFlowName
```
  where brokerName, integrationServerName, applicationName, libraryName, and messageFlowName represent the broker, integration server, application, library, and message flow on which you want to receive data.
- SMF (on z/OS® only)
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.
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 integration server 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    
```
Using 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.

Next:

You can now complete the following tasks:

ac18930_.htm |

Last updated Friday, 21 July 2017