I would suggest that some very high priority task got in a loop - something that runs at dispatching priority x'FF'. But then if it were truly in a loop, why did it stop after 4 minutes?
Do you just have 1 processor? Good luck in finding the problem. Let us know if it happens again. I'm sure you have IBM involved - that sure sounds like a Sev 1 to me. Eric ---- JE Thinnes <[email protected]> wrote: > We just experienced a 4 minute 'outage' on our z/OS system. (single image > z/OS 1.9 system). > > By 'outage', I mean we could not communicate with MVS through TSO or the > z/OS consoles. There is a 4 minute gap in SYSLOG. The same for CICS, IMS > and DB2 logs. > > There were no system dumps or other indicators. > > We reviewed SYSLOG for the 15 minutes that preceeded the 'outage' and did > not find anything. TMONMVS had a 4 minute gap in the collector during > the 'outage'. > > Any suggestions how we can determine what happened?-- Eric Bielefeld Systems Programmer Washington University St Louis, Missouri 314-935-3418 ---------------------------------------------------------------------- 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
