Keeping those ids in place does nothing to protect the file space if your statement, "A user with the same name as an SFS filespace (whether it is BFS or not) has ownership rights of the filespace," is true. There is nothing that says that the name of the filespace is the same as the userid of the file server. This is demonstrated quite nicely by VMSERVS being the server for the VMSYS pool. If you are trying to protect the file pool names, then you need to create ids with matching names.
You have just given me one more set of names that I need to protect in my directory creation process. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark > Sent: Wednesday, July 21, 2010 2:48 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: TCP/IP Server > > On Wednesday, 07/21/2010 at 04:47 EDT, Michael > Donovan/Endicott/i...@ibmus > wrote: > > If you are using the OpenExtensions Shell & Utilities (S&U) code on > > CMS, > then > > you want to leave those ids in the CP directory. If you > are not using > the S&U > > code, then feel free to remove these ids. They are place > holders for > certain > > functions used by the S&U. > > I beg to differ with my learned colleague and suggest that > these user IDs be kept in place. They are there to help you > avoid accidental creation of user IDs that map to BFS > filespaces created by IBM during installation of z/VM. A > user with the same name as an SFS filespace (whether it is BFS or > not) has ownership rights of the filespace. > > Alan Altmark > z/VM Development > IBM Endicott >
