Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see DASD MANAGER PLUS for DB2 13.1.

Setting up a BMCTRIG job

Use these procedures as a guidelines for creating a BMCTRIG job to detect exceptions.

The procedures in this section show how to include BMCSTATS and BMCTRIG in the same action in worklist JCL format.

If you plan to analyze any exceptions from the DASD MANAGER PLUS statistics database, run the BMCSTATS utility before the BMCTRIG utility to ensure that you are analyzing current statistics. If you do not plan to analyze any BMCSTATS specific exceptions, this step is not necessary. For more information about the analysis of various thresholds, see BMCTRIG-rules.

To specify which objects to monitor with the BMCTRIG job

  1. Set up an object set for complex object requirements, or use a simple pattern for the service. (See Using-object-sets.)
  2. Identify which exceptions to monitor (by using system triggers or overrides).To set thresholds that apply to both table spaces and indexes, see Thresholds-in-BMCTRIG-syntax.
  3. Identify which actions to generate or specify a default action in the BMCTRIG syntax. (To generate actions that differ based on exceptions, use system triggers.)

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*