What has changed about Rules in BMC AMI Ops Automation version 8.4
We recommend that you always use the same level of TS to update Rules and Rule Sets. Features added to newer releases are not supported by the earlier releases.
Rules Management Rules
If you have a mix of product versions running in the same AOPLEX_NAME, ensure that you use only version 8.4 Rules functionality running in a PAS that has version 8.4 of BMC AMI OpsA installed. In a mixed version environment, we recommend that you administer changes to Rules using the context of a PAS that matches the version where the Rule will be deployed.
If you deploy Rules that contain functionality that is not supported in the PAS (for example to a earlier version or mismatched level PAS), those Rules will fail to load when the PAS is started.
Classic Rules
If you are using a terminal session (TS) from BMC AMI Ops Automation version 8.4 and you change the target in the TGT field to connect to an AMI OpsA version 8.3.xx (or earlier) BBI-SS PAS, you can view and edit the AMI OpsA version 8.3.xx Rules and Rule Sets.
If you are using a TS from BMC AMI Ops Automation version 8.3.xx (or earlier) and you change the target in the TGT field to connect to a BMC AMI OpsA version 8.4 (or later) BBI-SS PAS, on the Automation Control panel you can view and edit the BMC AMI OpsA version 8.4 (or later) Rules and Rule Sets but you cannot see or use any of the newly added options.
The following table describes changes made to Rules for this release:
| Enhancement | Description | |
| Rules API | Haitam: can you supply some words for why users are going to use the Rules API For more information, see xxx | |
| Issue multiline write-to-operator (MLWTO) | Rules Management Rules can issue a MLWTO. For more information, see xxx | |
| Send Email to users when the maximum number of abends threshold is reached | When the maximum number of abends specified with the DMABTIM parameter, you can now create automation where BMC AMI OpsA will send an Email warning you of this situation. For more information, see | |
| Display the fired count for Rule Set members | You can now hyperlink from the Ruleset Name field on the RSETR view to display the RULESR view and see the Fired count for the Rule Set members. You can also use the new BRR line command from the RSETR view to display the RSETRMBR view. For more information, see Differences between Rules Management Rules and classic Rules. | |
Mixed-case variable values
| The Advanced Set Variables and Set Variables fields of the Set Variables (AV) dialog box in Rules Management now support mixed-case variable values. This eliminates scheduling an EXEC to use mixed-case variable values. For more information, see Differences between Rules Management Rules and classic Rules. | |
Deploy Rules, Rule Sets, and PASDefs in MainView Explorer and BMC AMI Ops UI
| We support a new Deploy option for the selected Rule/Rule Set/PASDef option in MainView Explorer (MVE) and the BMC AMI Ops User Interface. For more information, see Deploy Rules, Rule Sets, or PASDefs. | |
Place Rules Management Rules into test mode
| Use the new BBPARM member AAOPRM00 parameter, RULETEST=NO|YES, to change all enabled Rules in a PAS into test mode. When the Rules fire in test mode, AMI OpsA writes their automation actions as messages to the Automation Logger. For more information, see BBPARM member AAOPRM00 parameters. | |
Extended free-form User Notes for Rule Definition
| In Rules Management you can enter extended free-form user notes for a Rule. You can now enter up to an additional 10 extended free-form user notes (per Rule) in addition to Rule's 512-character User Notes field. For more information, see Differences between Rules Management Rules and classic Rules. | |
New variables for Rules Management Rules
| Rules Management ALRM-initiated Rules now support two new variables that contain the Alarm Message ID and name of the Alarm created by the Alarm Management application:
For more information, see BMC AMI Ops Automation-supplied EVENT variables and TSO variables and USS variables supplied by BMC AMI Ops Automation. | |
Clear or remove write-to-operator (WTO) route or descriptor codes with Rules
| You can to clear (or remove) the route or descriptor codes for incoming WTO messages with MSG initiated Rules Management Rules. In the Event Type Actions dialog in Rules Management, use the following values in the Update R/D field:
For more information, see the online help. | |
Updated ARAUTO view for Rules Management Rules actions
| The Automation Reporter view ARAUTO now tracks and displays a Total Rules Actions Counter for Rules Management Rules actions that occur in the PAS. For more information, see List of windows mode Automation Reporter views | |
Simplified EZAORUL view
| The EZAORUL view is simplified and includes links to two new sub menus:
For more information, see Accessing the Rules Management application. | |
BRC event Rules support REST API calls from the Common REST API (CRA)
| We provide support for Rules to be triggered by events from the Common REST API (CRA). The CRA can create and send BAROC messages to BMC AMI OpsA, which processes them as BRC events. For more information, see the following topics: | |
Access USS event variables | Event variables are now available to USS processes that are spawned from Rule Action: Command Type USS. For more information, see TSO variables and USS variables supplied by BMC AMI Ops Automation. | |
Dynamically switch the Rules Management application from ADMIN to FULL mode
| You can now dynamically switch the BBPARM member AAOPLXnn parameter USAGE_MODE_RULES setting from ADMIN to FULL, without requiring that you restart the BBI-SS PAS. This is useful especially when you use the AutoLoad facility to migrate from classic Rules to Rules Management Rules. For more information, see Migrating Rules to Rules Management application  . | |
| Issue IBM Z Open Automation Utilities (ZOAU) commands | You can access the IBM Z Open Automation Utilities (ZOAU) and issue ZOAU commands using a USS script scheduled from the Rules Management Rule Action Specification field Command: Type USS. For more information, see the discussion "Issuing ZOAU commands from a Rules Management action" in the topic Differences between Rules Management Rules and classic Rules. | |
| New Selection Criteria attribute for EOS-initiated Rules | You can specify a greater than (>) or less than (<) value for the new Step CC Selection Criteria attribute, where Rules automation can fire based on the condition code of an EOS event. For more information, see the discussion "Enhanced Selection Criteria option for EOS-initiated Rules" in the topic Differences between Rules Management Rules and classic Rules. | |
Improved handling of different versions of Rules
| This release provides better handling of Rules Management Rules deployed to target PASs that are not running at the same product version or maintenance level. For more information, see Differences between Rules Management Rules and classic Rules. | |