You can change the scope of authority, such as which skeleton files a directory manager can use or how much space a directory manager can allocate, at any time. These changes are effective the next time the manager creates a user ID or changes any aspect of the user configuration that the VMSECURE MANAGERS file controls; however, they have no effect on user IDs the directory manager has already created or is currently managing.
Before you change a directory manager’s scope of authority, you may want to check the status of the user IDs that directory manager manages. For instance, before you reduce the amount of space that a directory manager can allocate, verify that directory manager actually has some unused space that you can take back.
Most of the information you will want to review about a directory manager is available through the QUERY command. For example:
|
Directory manager’s specification |
Command that lets you review this specification |
|---|---|
|
Current space allocations and space left to allocate |
QUERY ALLOC MANAGER mgrid |
|
Current space allocations and space left to allocate for all directory managers |
QUERY MANAGERS |
|
Skeleton files available for creating user IDs |
QUERY SKELETON MANAGER mgrid |
|
Subpools available for creating user IDs |
QUERY SUBPOOLS MANAGER mgrid |
Note: For more information about these commands or about other information you can find for directory managers, see QUERY Command in the chapter "Command Reference" in the Reference Guide.
To change a directory manager’s scope of authority
vmsecure admin managers
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |