Moves the USER directory entries listed in the specified control file from the CA VM:Secure HOLD minidisk to the CA VM:Secure DRCT minidisk and the CP object directory. This move activates the user IDs.
Moves the USER directory entries listed in the specified control file from the CA VM:Secure DRCT minidisk to the CA VM:Secure HOLD minidisk and removes them from the CP object directory. This move deactivates the user IDs, putting them on hold.
Creates USER or IDENTITY directory entries using disk space allocation and format information in the specified control file. Through console prompts, you can specify an alternative skeleton file or subpool name. If in the specified skeleton file, there is a *ENROLL special comment with the IPLstmt option, and if a sample profile is available or specified on a *SP= special comment in the skeleton file, CA VM:Secure copies that sample profile to the top‑level directory for the user ID 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.
The new user’s directory entry is not written to the BKUP minidisk when using the MULTIPLE command with the NEWUSER parameter.
Removes the USER or IDENTITY directory entries listed in the specified control file from the CA VM:Secure DRCT minidisk and the CP object directory, and formats any minidisks in those entries. An IDENTITY entry can only be removed if it contains no BUILD statements.
Note: When CA VM:Secure deletes a minidisk that is on a pack that is under its control, it deletes links to that deleted minidisk from the directory.
Is the CMS filename and filetype of the control file to use. The file can reside on any of your accessed minidisks.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |