Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Database I/O data
BMC AMI Ops Monitor for IMS Offline
collects all database activity indicators per transaction at the database level.
A separate segment is appended to the BMC AMI Ops Monitor for IMS Offline transaction record per accessed database to hold the counts (see Log-record-layouts). This process allows later reporting by transaction, by user (for accounting), and by database, which is always true for the DL/I calls. Each call is counted by type (GU, ISRT, and so on) and per DBD.
These database segments also contain fields for several I/O-related counts. I/O activity is split into categories according to whether the I/O was a read or write, key or non-key access. One additional count, called NO I/O, is unique to BMC AMI Ops Monitor for IMS Offline. This count is a measure of IMS overhead and is the number of requests to the IMS buffer handler that do not result in I/O. These counts can be affected by the Event Collector parameters.
The following topics discuss the use of the DBIO Event Collector parameter:
For more information about the Event Collector parameters, see Customizing-after-installation.
Related topic