Thanks for the command syntax. I did not know about the SADMP option. As I mentioned earlier, we first 'exercised' the auto IPL scenario when one LPAR ran out of real storage. System was IPLed around 05:00. No one else even noticed. Like you, I was sure someone had done it, but no, it was actually self-induced. It happened several times. Even with SAD the cause was elusive.
With a PMR open, I posted on this list. One esteemed List contributor recalled having made a change to z/OS (!) that could be the culprit. We mirror DASD to our DR site. Occasionally an XRC action would delay an OS I/O operation, causing the I/O to be redriven. However, real storage acquired for the first I/O was not freed, causing a real storage leak that gradually reduced the available frame count to zero. One PTF fixed the problem. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Beesley, Paul Sent: Tuesday, March 24, 2015 6:56 AM To: [email protected] Subject: Re: Unscheduled automatic reIPL on z10 Thanks to all who shared tips and experiences both off- and on-list. A PMR has been opened and I have changed AUTOIPL to take a standalone dump, which I have tested. By the way for the sake of completeness, the command to trigger a SAD is V XCF,sysname,OFF,SADMP Regards and thanks Paul ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
