With the exception of the required SAD every 3 months due to training/audit, We had to SAD roughly once a year for 'real'.
Ronald Kristel ________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Mark Zelden <m...@mzelden.com> Sent: Friday, September 29, 2017 4:05:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Last SAD (was: DLIB volume for SAD) On Fri, 29 Sep 2017 12:59:56 +0000, van der Grijn, Bart (B) <bvandergr...@dow.com> wrote: >Had to? Can't remember that far back. We've had an LPAR fail, autoipl SAD and >then autoipl z/OS in > the last couple of years, but we didn't need the actual SAD to determine the > cause/solution. >Bart That's a good point. In my post I mentioned an SAD last week I took of a sandbox LPAR when it went into a wait at IPL time. In pre-2074 / OSA-ICC days I would have seen the NIP message on a console, but with OSA-ICC the console just clears and goes back to the connection screen. I took the SADUMP just to see the wait message / module / reason code. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
