Interesting ... Is this "single image system" connected via CTC or shared DASD to another system or LPAR (Test system, perhaps)? If so, did somebody IPL or shut down this Test system at the time of your 'outage'? (This could have caused a DASD Reserve lockout or a disruption in GRS and/or CTC-communication.)
Do you remotely mirror your DASD to an off-site DASD box? If so, did something happen with the communications link between local and remote DASD? Did someone start or stop or make changes to mirroring procedures? Is your DASD control unit accessed by / shared with non-z/OS systems? Did somebody perform any DASD - control unit - intensive task (initialize disk, reconfigure arrays, etc.) at the time of your outage? Did your DASD box suffer any internal hardware problems during that time? This also applies to any virtual or real automated tape library ... anything happen there? Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of JE Thinnes Sent: Wednesday, January 07, 2009 09:03 To: [email protected] Subject: MVS 4 minute 'outage' 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? ---------------------------------------------------------------------- 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
