REVOKE ADMIN

Read syntax diagramSkip visual syntax diagram REVOKE ADMIN userid

Authorization

File Pool Operator

Purpose

Use the REVOKE ADMIN operator command to delete file pool administration authority from a user.

Operands

userid
is the virtual machine identifier from which file pool administration authority will be removed. Do not specify a nickname for userid. Nicknames are not recognized on server operator commands.

Usage Notes

  1. All messages are written to the server machine operator console.
  2. The user ID will lose administration authority after any in-process logical unit of work ends and before the user ID begins the next logical unit of work.
  3. When REVOKE ADMIN is entered, any explicit locks acquired by the specified user ID will not be automatically deleted. The user can remove them if he or she is still explicitly enrolled or if PUBLIC is enrolled. Or, another file pool administrator can delete the locks.

    When administrator authority is deleted, the user may find he or she cannot use the QUERY LOCK command to see locks he or she created. This happens if the user has no explicit authority on the object and was able to create the lock only by virtue of administration authority. After administration authority is revoked, the QUERY LOCK command does not display the locks for the user because the user has no authorization on the file or directory. Although the user cannot display the lock, the user can still enter a DELETE LOCK command to delete it.

  4. If the specified administrator is accessing other users' directories (for which he or she has no explicit authorizations), those directories remain accessed until the end of the CMS session.
    Note: All authority checking for a DIRCONTROL directory is on access. Therefore, if a user accesses a DIRCONTROL directory by his administrator authority and his administrator authority is revoked, his authority on that directory remains until access of the DIRCONTROL directory is released.
  5. For FILECONTROL directories, if a user has opened a file he has authority for because he is an administrator, and his administrator authority is revoked before his changes are committed, he can still commit the data but will be unable to reopen the file.
  6. If the revoked user ID is specified in an ADMIN startup parameter, that user ID will be given administration authority again the next time server processing is started.