Invoking new alert deactivate remotely (fr mainframe)

[Peter Heggie]

The 5.8.4 update includes the ability to deactivate an alert without deleting it, and there is a matching update to the command line to provide this capability in batch.

What are the drawbacks to embedding these commands in nightly batch, or special maintenance procedures, to deactivate monitors when some threads may behave differently (which is expected for the maintenance, but may cause the monitor to fire), followed by a matching activation of the monitors at the end of the procedures?

I’m thinking this could be useful for planned outage maintenance, where the (re) activation would be run automatically at the end of the maintenance, without having someone waiting to manually activate a monitor. This may be especially useful when the maintenance process may run longer than anticipated and the new batch command allows this monitor activation to be decoupled from a specific time.

Also, has anyone done anything like this where the batch or maintenance jobs are scheduled on the mainframe, but Cloverleaf is on a midrange server? How do you get this remote command capability without opening up a security exposure? We don’t have an enterprise job scheduler, just one on the mainframe.

Thanks,

Pete

Peter Heggie
PeterHeggie@crouse.org

Topic