Logon would not be the right or only place to put it. DEF STOR is another possible place to err if the maximum storage was too high. Perhaps a check of virtual storage at IPL time. That is a common point that must be traversed no matter where the error occurred.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark > Sent: Wednesday, September 16, 2009 10:20 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: VM lockup due to storage typo > > On Wednesday, 09/16/2009 at 09:14 EDT, RPN01 > <nix.rob...@mayo.edu> wrote: > > I don't think, in this case, it is the user causing the > problem at all. > The > > user didn't define their storage allocation, and in > practice can't do > that > > at all. So the user didn't set up the situation which caused the > integrity > > issue, the system administrator did. > > That was my point to Marcy: Not an integrity problem. The > system is obeying the sysadmin's instructions. > > > To my mind, if this requires addressing, it should be in > the DIRECTXA > > command, so as to help the system administrator in avoiding > aiming the > gun > > at his toes. > > DIRECTXA has no context in which to make such warnings. > Placing limits at LOGON would only apply to resource > availability to hold the needed control structures. When the > guest begins to run and actually use all that memory, then > another line of defense is needed. > > Alan Altmark > z/VM Development > IBM Endicott >
