I just went through the exercise of looking at checks *before* we migrated to z/OS 1.8 and attempted to get alerted to exception conditions via automation (as opposed to looking at sdsf screens/serching through syslogs for temporary but recurring conditions). 1. There is no one place where you could see what the error message would be if the check trips. I think the health checker book should have that, but it doesn't. I am forced to look through different operating system levels of books to first identify what the error message *might* be (indicated by the H in 4th position) and then take guesses what checks they apply to. 2. Supposedly the hierarchy for the actual message id is severe (cc12) - HZS0003E medium (cc8) - HZS0002E low (cc4) - HZS0001I informational - HZS0004I Unfortunately, that is not necessarily true, as proven by the ASM check mentioned before. 3. We use system automation/Netview and want an exception email the minute a 'real' exception occurs. In order to trap a multiline WTO (and all checks generate multilines) you have to either use a clist/REXX in the first place (which costs you performance) or use the findline with its incantations (which performs better but as far as I know forces you to have individual message combinations). In general, not easy to set up. And based on what some of the exceptions are for - starting an hzsprint with SMTP step is exactly what we don't want - who can guarantee that SMTP is available? (We use a direct addressing of TCPIP.)
Barbara NItz -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
