What is the Rules Management editor
With the Rules Management application, Rules are no longer stored as members of a data set organized by Rule Set as they are with classic Rules.
With Rules Management, you can associate a Rule with more than one Rule Set. This eases maintenance by eliminating unnecessary duplication and allows you to have more precise Rules-based automation.
Rule pools
Rules Management Rules are collected into Rule pools that you can set up in any grouping that makes sense for your enterprise. This could be by:
- Geographical location
- By application
- By responsible department
- By sysplex
- Or any grouping that makes sense for your automation
Setbases
The same is true for Rule Sets. Rule Sets are now organized into Setbases that can, like a Rule pool, represent any organization model. A Rule Set can be defined as a generic Rule Set when the Rule Set does not have individual Rules as members but instead, identifies an entire Rule pool as automatic members of the Rule Set.
You can add new Rules to the Rule pool and deploy the Rules without having to add the Rule to a Rule Set. Because the Rule is a member of a Rule pool, it is automatically a member of any generic Rule Set that uses that Rule Pool.
More functions
Starting with version 8.1 of MainView AutoOPERATOR (now known as BMC AMI Ops Automation), the Rules Management application will include additional or extended functionality that is not supported in the classic full-screen Rules Processor editor.
One example is that beginning with version 8.1 MainView AutoOPERATOR, you can use a variable name as the value of the DELAY( ) keyword. This makes it possible to set up standard delay values using variables and, alter those delays by changing the variable's value instead of having to edit all of the Rules individually.