CA VM:Secure does the following when you change a user ID in a USER or IDENTITY entry:
Updates all directory links to minidisks owned by the old user ID to reflect the new user ID except links specified on the NOLINK record in the DASD CONFIG file
If CA VM:Secure manages your SFS, then all file pools that are managed by the product must be active and available so that it can check them for file space that may be owned by the same user ID name as the new one to which you are changing this user ID name. If any file pool managed is not available for checking, or if it finds any file space in an available file pool owned by the new user ID name, the command will fail.
When the user ID being changed is enrolled in a CA VM:Secure‑controlled SFS filepool, the CHANGE command runs on a servant machine. In this case, be sure the Servant Facility is enabled; if the Servant Facility is disabled, the CHANGE command fails.
If the command tries to rename file spaces but the underlying file pool server does not support this function, the change fails.
After changing a user ID, update the following to reflect the new user ID:
You cannot change the CA VM:Secure user ID or a user ID specified on an IGNORE record in the DASD CONFIG file with the CHANGE command.
The CHANGE command uses the CMS FILEPOOL EXEC to rename an individual file space within a file pool. Ensure that CA VM:Secure has access to the MAINT 193 minidisk on which the FILEPOOL EXEC resides.
Example
To change director entry JSMITH to JSREID, enter:
vmsecure change jsmith jsreid
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |