Exception data source groupings
These groups are based on the data source that BMCTRIG analyzes to identify exception conditions.
Db2 RTS specific exceptions
Exceptions in this group can only be determined by analyzing data in the Db2 Realtime Statistics (Db2 RTS) tables:
- SYSIBM.SYSTABLESPACESTATS
- SYSIBM.SYSINDEXSPACESTATS
Db2 RTS or BMCSTATS exceptions
Exceptions in this group can be determined either by analyzing the Db2 RTS tables or by analyzing data in the BMC statistics database.
This group also contains exceptions that can be determined by querying Db2 directly. The DB2RTS option determines which data source BMCTRIG uses to analyze these exceptions.
BMCTRIG will attempt to use the Db2 RTS tables to analyze the exceptions under the following conditions:
- When DB2RTS Y is specified and there are no rows for an object in the Db2 RTS tables, BMCTRIG will use BMC statistics data to analyze the exception instead.
- When DB2RTS O is specified, BMC statistics data will be ignored and only Db2 RTS data will be considered in the analysis of the exception.
If DB2RTS N is requested or if DB2RTS is not specified in the command syntax, BMC statistics data will be used to analyze exceptions in this group.
The following DASD MANAGER PLUS tables are analyzed when BMC statistics data is required:
- BMCATSnn.RS_TABLEPART
- BMCATSnn.RS_INDEXPART
There are a few exceptions that are evaluated at the space level when PARTLVL N is specified. When that happens, the following BMC statistics tables are used:
- BMCATSnn.RS_TABLESPACE
- BMCATSnn.RS_INDEXES
Exceptions related to the status of an object (such as COPYPEND) are always analyzed directly regardless of the DB2RTS option.
BMCSTATS specific exceptions
Exceptions in this group can be analyzed only by evaluating data in the BMC statistics tables the Db2 RTS or BMCSTATS exceptions group.
If DB2RTS O is specified, exceptions in this group will not be analyzed.
Related topics