Permanent locks are used to prevent updating of an entry or file by one user while another user has a copy of the same entry or file. They are retained during a shutdown and restart of CA VM:Secure.
All permanent locks are written to a CMS file called PERMLOCK FILE, located on the CA VM:Secure A‑disk. The locks persist until a command clears them or you issue the UNLOCK command on them. If CA VM:Secure terminates before a lock is cleared, CA VM:Secure reads the PERMLOCK file at initialization and re‑establishes all of the previously existing permanent locks.
Example
Your operator has issued the END command, but the CA VM:Secure shutdown process has not completed. To determine which virtual machine is preventing the shutdown process from completing, enter the QLOCK command from the CA VM:Secure service virtual machine console:
qlock
CA VM:Secure responds with a one‑line message for each outstanding lock:
THE MANAGE PROCESS HAS A PRIVATE DISK‑U‑MAINT‑ABC LOCK. THE MANAGE PROCESS HAS A SHARED VMNUC‑MACRO‑VMSECURE‑MANAGE LOCK.
Then issue the QPCB command to determine which user ID has issued the MANAGE command.
Note: For more information, see QPCB Command.
|
Copyright © 2014 CA.
All rights reserved.
|
|