On Wed, 28 Sep 2005 08:17:39 +0200, Barbara Nitz <[EMAIL PROTECTED]> wrote:
>... >I guess the message appeared for 10 seconds, after which the console got >'refreshed' with the normal display. So unless someone looked at that >console in those ten seconds and went there to read, they really wouldn't >have noticed anything. > >Now only two questions remain: >1. Is iee178i issued with the request for the message to be held? (I still >need to read the modules Jim indicated). >... I know anecdotal "evidence" is useless, but .... We had a rash (4 or 5) detected spin loops a few months ago. Nobody ever saw error messages while spin loop recovery was happening. The couple times it was noticed at all, it was poor CICS response time that got noticed, and I/O errors on VTAM CTC connections that got blamed. (Yup. A VTAM CTC I/O times out when the other side goes into a disabled spin loop. And yup, CICS performance suffers during a spin loop. Duh!) And a couple times the spin loops weren't noticed at all; the messages were noticed days later while researching something else. (Why the resulting 071 abends didn't kick off our alerting automation, I don't know.) It's hard to believe such a disruptive problem can be a stealth problem. I guess that speaks well of the spin loop recovery routines. Pat O'Keefe Pat O'Keefe ---------------------------------------------------------------------- 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
