John,

 

The QUERY AUTH command does not list all administrators of the pool, just the one issuing the query command. It shows that user, the owner, and any explicitly granted authorities. Your first possibility is not it. An owner of a space is always authorized for it. You can only get rid of that authorization via DELETE USER.

 

Regards,

Richard Schuh

 

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED]On Behalf Of John Hall
Sent: Wednesday, January 25, 2006 5:49 AM
To: [email protected]
Subject: Re: SFS REVOKE command

 

 

On 1/25/06, Steve Gentry <[EMAIL PROTECTED] > wrote:


I'm trying to revoke authority for a userid to an SFS directory.  My userid is an SFS administrator. I originally Enrolled the user in this filepool.
I issue the revoke command and it appears to work successfully.  I then issue a Query Authority and the use I just revoked is still
listed as having access to this specific directory.  I issue the revoke command again and it says that I have already revoked
authority for this user.  Why is the user still showing up when I do the Query Authority command?

 

A couple of possibilities come to mind:

 

- userid is an SFS Administrator, meaning it has authority to access and update any file and directory in that file pool. ("QUERY ENROLL ADMIN filepool" will show you the list of SFS Administrators for a file pool)

 

- SFS directory is DIRCONTROL (QUERY DIRATTR dirid) and the userid has the directory accessed.  When they release the directory, they will be unable to access it again.  (DIRCONTROL directories behave similarly to minidisks)

 

- If you are doing this from DIRLIST or FILELIST, I have found that in some cases the REVOKE AUTH command truncates the target userid by one character.  Try putting a trailing "(" on the REVOKE AUTH command to see if this changes the behavior (and, if so, please report to the support center)
 

--
John Hall   (+1) 727-397-6373      Safe Software, Inc.
JohnHall (at) SafeSoftware.Com  http://www.SafeSoftware.Com
JohnBeachFL (at) gmail.com

Reply via email to