Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Controlling check exception message WTOs and their automation consequences IBM Health Checker for z/OS User's Guide SC23-6843-02 |
|
By default, IBM® Health Checker for z/OS® issues DOM requests to delete any check exception message WTOs left behind from previous check iterations. It does this DOMing right before the start of the new check iteration. That means that each time the check generates an exception, it also sends a new exception WTO, which also kicks off any automation actions you've set up for your installation. So, what if you want more control over check exception WTOs and their automation consequences? For example, let's say you have a check that runs every hour. Now let's say that your check begins generating identical exceptions that you've automated on to prompt a beeper call to your favorite system programmer. You have not yet resolved the exception issue, and the installation policy is to not disable checks generating exceptions. That's just good practice, right? And yet your check might generate a lot of WTOs and beeper calls to that poor system programmer while the issue gets resolved. That's where DOM control comes in! Starting with z/OS V1R13, IBM Health
Checker for z/OS you can use
the following functions that help you control whether you want to
suppress WTOs and any automation actions they trigger for a check
that is generating exceptions:
On the other hand, if you always want to delete WTOs for your check, and never wish to suppress duplicate exception WTOs, you will want to specify or default to DOM(SYSTEM) when you add your check, and let the system take care of DOMing of check WTOs for you! |
Copyright IBM Corporation 1990, 2014
|