The options that you specify for message flow accounting and statistics collection determine what information is collected. You can request the following types of data collection:
An interval is prematurely expired and restarted when any of the following events occur:
This preserves the integrity of the data already collected when that event occurs.
On z/OS, you can set the command parameter to 0, which means that the interval is controlled by an external timer mechanism. This support is provided by the Event Notification Facility (ENF), which you can use instead of the broker command parameter if you want to coordinate the expiration of this timer with other system events.
You can request snapshot data collection, archive data collection, or both. You can activate snapshot data collection while archive data collection is active. The data recorded in both reports is the same, but is collected for different intervals. If you activate both snapshot and archive data collection, be careful not to combine information from the two different reports, because you might count information twice.
You can use the statistics generated for the following purposes:
Archive data provides the information that you need for a use assessment of this kind.
Snapshot data is appropriate for performance assessment.
Check the information provided by snapshot data for routing information; if this is insufficient for your needs, use archive data.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac19102_ |