I'll put in my .02 cents, in case these were not thought of........ - were you able to process and see any SMF records during the 4 minute 'outage'.
- see any jobs that finished just after you came out of the 'outage' that could've caused the problem. - a notification to your users to ask if they started or did something at the time the 'outage' started. - next time it happens can you go back and look at RMF Monitor III to check for any hints. - a debugging possibility is to start GTF and let it run to trace DSP, IO, EXT, SVC, etc events but depending on activity, etc, performance could be affected. Rgrds, Joseph Sumi -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Marchant Sent: Thursday, January 08, 2009 11:14 AM To: [email protected] Subject: Re: MVS 4 minute 'outage' On Thu, 8 Jan 2009 09:57:56 -0600, Hal Merritt wrote: >... it might >be fun to try to recreate the problem by running and cancelling that >test job. Maybe. If he does, he might want to set a SLIP trap to take an SVCDUMP when the that job gets the s222. -- Tom Marchant ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
