Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Administrative tasks

The section describes different administrative tasks you can do for Rules Management.

Registry management

It is important to define the correct registry size for your Rules because if the registry becomes full, BMC AMI Ops Automation cannot function correctly. For more information, see section Implementing the Rules Registry in the Customizing-BMC-AMI-Ops-Automation-after-installation and the documentation for the RTCS registry in Customizing after installation.

In BBPARM member AAOPLXxx, the REGISTRY_WARNHWM parameter allows you to set a high-water mark percentage where a warning message is issued. The warning message AGSRY0014W is issued when either one of the following situations is true:

  • The BMC AMI OpsA PAS is being inititialized.
  • The high-water mark has increased at least one percent since the last time the AGSRY0014W message was issued and one minute has passed sine the last time the message was issued.

If the registry becomes full and unusable, BMC AMI OpsA will issue the following message:

AGSRY1221E Registry is full

Changing the registry size

If you find that you need to change the registry size, you should make a backup of the registry. The backup can be used to restore the registry. To change the size of the repository, use the following instructions.

  1. Make a backup of the BMC AMI OpsA registry.

    Use the sample JCL found in BBSAMP member AAOAGSBK, which creates a flat-file backup of the registry. The JCL has a number of comments at the top to assist in customizing the JCL. Execute the JCL to create a flat-file backup of the BMC AMI OpsA registry.

  2. Delete and reallocate the registry following the procedure 'Allocating a Registry' in the Customizing-BMC-AMI-Ops-Automation-after-installation.
  3. Specify a larger registry.

  4. Restore the old registry into the newly created registry.

    Use the sample JCL found in BBSAMP member AAOAGSRS, which loads a registry backup into the target registry.

    Note that the target registry can be a newly-created completely empty registry data set or it can be an already-populated registry data set. In the case of the already-populated registry, the restore will merge the flat-file backup into the registry, create new items as needed and replacing existing items as needed.

Chained Rules group

A chained Rules group (CRG) is a set of Rules and the Rules processor always processes all of the Rules, from head to tail, whenever the event type matches the event type of the Rules in the CRG. All, or any subset, of the Rules in the CRG can fire for a single event depending on the IF-ELSEIF logic specified by each Rule’s individual selection criteria in conjunction with the “evaluate when policy” for each rule. A Rule Set’s strategy has no effect on the Rules inside the CRG once the head rule of the CRG is evaluated by the Rules processor. However, a Rule Set’s strategy of FIRST will be satisfied if any of the Rules in the CRG, including the head Rule, fires.

This section also includes the following topics:

Related topic

Rules-Management-application


 

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