>It is highly desirable to eliminate operator prompting in this situation, >because a great many outages have occurred over the years when either (1) the >operator or automation replies DOWN prematurely and data base corruption >occurs as I described earlier, or (2) no one ever replies DOWN, and the >sysplex begins to suffer from "sympathy sickness" because resources are held >or protocols of one kind or another are impeded by the unresponsive system.
We had a situation once, where our lowest priority LPAR in a SYSPLEX had the IXC102D message outstanding, and it wasn't covered by automation. OPS didn't even monitor that system. By the time we found it, all the other LPARs were down. So, whatever you do, I hope you do it quickly. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
