Hi Randy,
We wrote back in time a TOD rule that is monitoring all rule sets.
As Sal said, a simpel edit-save outside the OPS rule editor, disables the Auto-Enable flag.
A rule can also become disabled to due excessive been fired (add OPTIONS "NOFIRELIMIT").
This TOD can be scheduled at the end of the day, week or in the system shutdown command.
The rulesets to check or scan can be build in a stem. This in order to leave out or skip some dev rulesets.
The same can also be done for specific ruleset.rulename to avoid false positives.
For each ruleset we skip rules who are:
- Enabled and auto-enabled
- Disabled and not auto-enabled
All others are considered as anomaly and can be put into a mail for verification or notification WTO on console.
Kr,
Patrick Barrez.
Original Message:
Sent: 11-02-2020 10:45 AM
From: Randy Knapton
Subject: Interesting thing happened
Hello All,
Had a weird situation happen this weekend after the IPL's of systems. Not sure if anybody else had this experience, I haven't in probably 20 years working with OPSMVS, but it was a blue moon. The rule SSMEOM got auto enable got turned off, which of course caused lots of issues later when scheduled down times occurred for tasks. Does anybody do any automated checking with OPSMVS to make sure the 'Main' rules are enabled and auto-enabled? or maybe a when a auto-enable is turned off on one of these "major' rules to ask 'are you sure' question pop up? Just wonder ...
Thanks
------------------------------
Randy Knapton
------------------------------