Another thing to look at is whether the user is an administrator of the file pool. It is possible for administrators and those who have write authority to write even though they have accessed the directory in read mode.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Frank M. Ramaekers > Sent: Wednesday, August 18, 2010 11:45 AM > To: [email protected] > Subject: Re: New to SFS > > Think we need a little more detail. > > USERA "owns" the filepool (i.e. SHARED:USERA.) A subdirectory > is created, like SHARED:USERA.SUB1 USERB is granted access to > the directory (how? READ, NEWREAD, etc.) USERB can update a > file in this SHARED:USERA.SUB1 directory. Are you sure? Can > he create a new file in this subdirectory. > Show us some of the AUTHLIST screens. > > Thanks, > > Frank M. Ramaekers Jr. > > > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Casey Rhodes > Sent: Wednesday, August 18, 2010 1:33 PM > To: [email protected] > Subject: New to SFS > > New to Shared File Sytems, so up fromt please forgive me if > this is way to simplistic for some of those here. > > I have enrolled a new user in the vmsys filepool called > shared. And then > > created directories under the shared top directory. I then > granted a user read access to these lower directories. When > accessed by the user granted read access the AUTH PF6 key > shows this user only has read capabilities, > > but user is still allowed to update the files. > > Dont know where to go from here. Sorry to bring the > discussions down to basics but dont find the CMS File Pool > Planning, Administration and Operations guide all that easy to use. > > > Any direction here would be appreciated. > > Casey > > _____________________________________________________ This > message contains information which is privileged and > confidential and is solely for the use of the intended > recipient. If you are not the intended recipient, be aware > that any review, disclosure, copying, distribution, or use of > the contents of this message is strictly prohibited. If you > have received this in error, please destroy it immediately > and notify us at [email protected]. >
