Rule changes are not recognized after modifying OPS rules on multiple different systems LPARs.

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

I have made changes to some ops rules but the changes don't seem to be recognized.  The rules are shared by numerous different MSF connected LPARS

Environment

OPS/MVS

Cause

Required follow up actions to the rule change were not completed.

Resolution

In order for a change in the rule to be picked up in OPS/MVS, the rule will need to be disabled and then enabled with that code change.   Otherwise, OPS/MVS is not aware of the change.

Go to the AOF Rule List page (=4.5.1, select the involved Rule Set).  From here, use the D line command to disable the currently loaded version of the rule.   Once the screen shows that it is disabled, use the E line command to Enable the new version of the rule.   

For changes made to multiple MSF connected systems, use the MD (Multi-system Disable) line command, which will then provide a list of the available systems that you can then select to disable the old rule on those systems.    Once the Deactivated shows up on the screen for all of the systems, the ME (Multi-system Enable) line command may be used, which will again provide a list of the MSF connected systems, where you may choose which systems you want the rule enabled on.   

Once the disable and enable action is completed, the new rule code will be in effect.