|
|
|
Issue the ADDENTRY command to create any type of directory entry. Create a USER, IDENTITY, or SUBCONFIG entry by specifying either a skeleton file or an input file to build the directory entry. You create a directory profile by using an input file to build the directory entry.
When creating a directory entry for a USER, IDENTITY, or SUBCONFIG, CA VM:Secure first creates the entry and calls any applicable user exits. If CA VM:Secure detects errors, it does not create the entry, does not create any minidisks, and does not enroll the user ID in any file pools. If CA VM:Secure does not detect errors, it creates minidisks and enrolls the user in a file pool if specified.
If CA VM:Secure manages your SFS, then all file pools that it 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 adding. 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.
If CA VM:Secure creates a new 191 minidisk for a new user ID or enrolls the user ID in a file pool with the IPLstmt option, you can identify a sample PROFILE EXEC to copy to the minidisk or top‑level directory by placing the special comment record, *SP=, in the skeleton or input file.
When creating a directory entry for a directory profile,CA VM:Secure does not call any user exits.
Note: When adding a USER or IDENTITY entry, the ADDENTRY command ignores any password specified on the USER statement and sets the initial logon password to be the same as the user ID.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |