>From what I have heard, I have no direct experience with it, all VM:Secure does is act as a file pool administrator using the built-in SFS commands; it does not add any functionality. Your experience tends to support that. There may be other commands, but if there are, I am not familiar with them.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen > Sent: Wednesday, June 18, 2008 9:00 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: SFS REVOKE AUTH question > > Thanks for the reply. VM:Secure has a revoke command. If I > understand the doc correctly, it takes the command and issues > it to VM, almost verbatim. > I do get the same error message when I issue the vmsecure revoke. > Looks like it's time for Plan "B" (whatever that is). > Steve > > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard > Sent: Wednesday, June 18, 2008 11:53 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: SFS REVOKE AUTH question > > Unfortunately for you, granting authority to PUBLIC grants it > to everyone who has an id on the system. If the filepool is > listed as a Global Resource, the authority carries over to > other systems connected to your system via APPC. Yes, PUBLIC > is the problem. > > Your ESM may provide an out. I do not know the abilities of > VM:Secure and RACF in this area. SafeSFS may be another way > to control access the way you are hoping for. Whenever I > enroll a new user in our SFS, I tell them to not grant > authority to PUBLIC for any files or subdirectories that they > would not want posted on the web or printed in the Enquirer. > > Regards, > Richard Schuh > > > > > -----Original Message----- > > From: The IBM z/VM Operating System > > [mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen > > Sent: Wednesday, June 18, 2008 8:23 AM > > To: IBMVM@LISTSERV.UARK.EDU > > Subject: SFS REVOKE AUTH question > > > > I am trying to REVOKE AUTH for an SFS user. The directory, > let's call > > it VMSYS:MAINT.PUBLIC has had a GRANT AUTH PUBLIC done to > > it earlier. > > I have a specific user I do not want to access this > directory. When I > > issue the REVOKE AUTH, (specifically: > > revoke auth vmsys:maint.public from steveg) I get DMSJAU1138E File > > sharing conflict with a return code of 70. > > The user is not logged on when I issue the command. > > Is the PUBLIC authority causing this problem? > > Thanks, > > Steve > > >
