|
|
|
The MANAGE command displays screens that let you define new USER or IDENTITY directory entries and modify existing USER, IDENTITY, or SUBCONFIG directory entries.
When you create or move a minidisk with the MANAGE command and do not specify a device type, the size you enter is interpreted as the number of 512‑byte blocks.
Directory managers are not allowed to manage their own user IDs. Changes to a directory manager user ID must be made by the CA VM:Secure system administrator or another authorized directory manager.
Use the QUERY command to determine the skeleton files and subpools you are allowed to use before you create or move minidisks or create user IDs.
If CA VM:Secure manages your SFS and you use this command to define a new user ID, then all file pools that CA VM:Secure manages must be active and available so that it can check them all for file space that may be owned by the same user ID name as the one you are defining. If any file pool managed by CA VM:Secure is not available for checking, or if CA VM:Secure finds any file space in an available file pool owned by the same user ID name, the command will fail.
For menu selection 1, Define/Reactivate a User ID, and menu selection 10, Work with Shared File System Menu, from which you answer Yes in the Update IPL record? field, you can identify a sample PROFILE EXEC to copy to the minidisk or top‑level directory. To identify the sample PROFILE EXEC, place the special comment record, *SP=, in the skeleton or input file. If a sample profile is available or specified on a *SP= special comment in the directory entry, that profile is copied to the top‑level directory for the user as PROFILE EXEC. If there is already a PROFILE EXEC file in the user’s top‑level directory, a sample profile specified on a *SP= special comment is not copied.
Note:
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |