It is highly unlikely that someone would issue an MVS or VSE MODIFY while in CMS and have that command interpreted as an attempt to change the limits for a filespace.
OTOH, it is sometimes nice to have an environment specification precede the command, something like "SFS MODIFY ...", or "CP QUERY ...'. This removes ambiguity, leaving very little for interpretation other than, perhaps, the different forms of CP commands based on privilege class. I would almost be willing to bet that your influence has increased along with your PITA index. :-) Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark > Sent: Tuesday, November 25, 2008 10:32 AM > To: [email protected] > Subject: SFS syntax (was: new VSMDCSS in z/VM 5.4) > > On Tuesday, 11/25/2008 at 01:02 EST, "Schuh, Richard" > <[EMAIL PROTECTED]> > wrote: > > > MODIFY - Needed to convey the action to be taken. > > USER - There is only one form of MODIFY, so this is a > > useless word. Furthermore, it is misleading. > > OTOH, the verb MODIFY is so useful and generic (see VSE and > MVS), it didn't make sense to consume it entirely for SFS. > We thought we might have other things to modify later (like, > MODIFY WINDOW.... };-) ) > > But I won't argue that MODIFY USER has a nice syntax. It doesn't. > > I would have MODIFY FILESPACE <filespace> BLOCKS <blockspec> > > and I wouldn't have mixed the concept of "user" with > "filespace". Shoulda, woulda, coulda. C'est la vie. I had > been with the company for about 4 years at that point and so > my "PITA Index" was considerably lower than it is now. Heh heh. :-) > > Alan Altmark > z/VM Development > IBM Endicott >
