Both Page and Spool space!!! When you get to the end of spool, there is nothing further that can be done. This ought to be considered a bug. Surely CP has the information it needs to determine that the virtual storage size is way too big to be accommodated and should reject the logon. This ought to be reported. If the logon is not rejected, CP ought to keep enough storage in reserve so that the operator can still get in and force the offender.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes > Sent: Tuesday, September 15, 2009 9:03 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: VM lockup due to storage typo > > See a thread on this list with subject "Sanity check?" from > Oct 2007 for what happened when I did the same thing ;) > > You probably filled page space. > > I still think IBM should refuse to IPL a guest that will > cause such harm. > > > Marcy > > "This message may contain confidential and/or privileged > information. If you are not the addressee or authorized to > receive this for the addressee, you must not use, copy, > disclose, or take any action based on this message or any > information herein. If you have received this message in > error, please advise the sender immediately by reply e-mail > and delete this message. Thank you for your cooperation." > > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Lee Stewart > Sent: Tuesday, September 15, 2009 8:39 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: [IBMVM] VM lockup due to storage typo > > Does anyone have an idea of how we might have gotten out of > this without an IPL? > > VM LPAR has 175G of memory and a flock of Linux Oracle guests... > Several guests needed more memory added so the directory was > updated and one by one the guests shutdown, logged off and > back on. So far, so good. > > But... In changing the memory for many guests, and it being > late at night after a long day, while meaning to set a > guest's memory to 9728M, it got set to 9728G. When that > guest was cycled we see the message on the console that it's > memory was limited to 8TB (HCPLGN093E), then the VM system > appeared to freeze. > > We couldn't get in via TCP/IP, or the HMC Operating System > Messages screen, or the HMC Integrated 3270. > > Finally had to IPL. Even that was wierd as I'd have > expected the Load > Normal to shutdown, it just IPLed. We did NoAutolog, fixed the typo > and all came back up ok... > > I suspect CP was scrambling paging everything in the world > out as Linux > tried to initialize that 8TB of memory... But I'm surprised > I couldn't > even get into the HMC consoles (to kill just that one guest > as opposed to all of them).. > > Any thoughts? > Lee > -- > > Lee Stewart, Senior SE > Sirius Computer Solutions > Phone: (303) 996-7122 > Email: lee.stew...@siriuscom.com > Web: www.siriuscom.com >
