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

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

You can use the mqsichangeflowstats command stop collecting data for message flow accounting and statistics at any time. You do not have to stop the message flow, integration server, or broker to make this change, nor do you have to redeploy the message flow.

Before you start:

You can stop collecting data for message flow accounting and statistics at any time. You do not have to stop the message flow, integration server, or broker to make this change, nor do you have to redeploy the message flow.

You can modify the parameters that are currently in force for collecting message flow accounting and statistics data without stopping data collection. See Modifying message flow accounting and statistics data collection parameters for further details.

To stop collecting data:

  1. Check the resources for which you want to stop collecting data.

    You do not have to stop all active data collection. You can stop a subset of data collection. For example, if you started collecting statistics for all message flows in a particular integration server, you can stop doing so for a specific message flow in that integration server. Data collection for all other message flows in that integration server continues.

  2. Issue the mqsichangeflowstats command with the appropriate parameters to stop collecting data for some or all resources.

    For example, to switch off snapshot data for all message flows in all integration servers for BrokerA, enter:

    mqsichangeflowstats BrokerA -s -g -j -c inactive  

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

    /F BrokerA,cs s=yes g=yes j=yes c=inactive 

    Refer to the mqsichangeflowstats command for further examples.

When the command completes successfully, data collection for the specified resources is stopped. Any outstanding data that has been collected is written to the output destination when you issue this command, to ensure the integrity of data collection.


ac18940_.htm | Last updated Friday, 21 July 2017