|
|
|
CA VM:Secure writes permanent locks to a CMS file called PERMLOCK FILE A on the CA VM:Secure A‑disk when it creates the locks. The UNLOCK command looks for two permanent locks to clear for each user ID, profile, or CMS file being unlocked. For user IDs and profiles, the locks have the form:
SHARED DISK filename filetype filemode PRIVATE LOCKUSER userid | profid
For CMS files, the form is:
SHARED DISK filename filetype filemode PRIVATE LOCKFILE filename filetype filemode
When processing a user or profile entry, the LOCK and UNLOCK commands use the same internal locks as the GETENTRY and REPENTRY commands. Thus, UNLOCK can remove the locks that a GETENTRY command with the LOCK option creates. You may use the UNLOCK command if you decide not to update a user ID or profile after retrieving it with GETENTRY and the LOCK option.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |