>O.k, but I hope a customisation and a message processing exit can work >together. Here we are 2 or 3 on the mainframe, a week can pass and nobody notice >that a sever exception occurred
Then one might say that you have not completed your job of customizing health checker to meet your needs. I disagree a bit with Barbara N. HZS0003E is an indication of what messages the customer has chosen to be treated as high severity, whether that is because they accepted a high severity default if so identified by the check owner or because the updated the check to change the severity. Thus monitoring for HZS0003E is indeed a way to look for HC situations that the customer feels are of high severity. If you have an automation program, you can customize it to look for HZS0003E. You can also change the routing and descriptor codes for checks so that they go to a console that you have set up specifically for that purpose. Many will set things up to get the message sent somewhere that can send an email. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
