/ALL
Specifies a display of all current LOCKs in all regions and information about the state of processes owning these LOCKs. The /ALL qualifier is compatible with all other qualifiers. When /ALL is combined with /PID or/ REGION the other qualifier prevails. SHOW / ALL and /WAIT displays both /ALL and / WAIT information.
/LOCK=PID and region
Allows you to specify a single lock. This provides a precise way to examine specific locks. The resource_name is enclosed in double quotations. Because M resource_names are formatted the same as global nodes with punctuation characters, in this context they are usually enclosed in sets of double quotations with string subscripts enclosed in sets of two double quotations.
show -lock="^a"(""b"")"
This command shows lock ^a("b") in the default region.
/[NO]C[RIT]
Allows LKE SHOW to work even if another process is holding a critical section. Use this qualifier only when normal operation is unsuccessful, as NOCRIT may cause LKE to report incomplete or inconsistent information.
/O[UTPUT]=file-spec
Directs the reporting of the current LOCKs. When you specify an existing file, LKE overwrites that file.
By default, SHOW directs all messages to SYS$OUTPUT.
/P[ID]=process-identification
Displays all LOCKs owned by the specified process identification number (PID).
By default, SHOW displays the LOCKs for all PIDs.
/R[EGION]=region-name
Displays LOCKs for the specified region.
The emphasis>/REGION qualifier is compatible with all other qualifiers.
By default, SHOW displays the LOCKs for all regions.
/W[AIT]
Displays the LOCK resource name and the process state information of all processes waiting for the LOCK to be granted. SHOW /WAIT does not display the owner of the LOCK. SHOW /ALL /WAIT displays both /ALL and /WAIT information.
When a process abandons a "wait" request, that request may continue to appear in LKE SHOW /WAIT displays. This appearance is harmless, and is automatically eliminated if the GT.M lock management requires the space which it occupies.
Use the following procedure to display all LOCKs active in the database(s) defined by the current Global Directory. For information on displaying specific LOCKs, refer to the section on the SHOW command and its qualifiers.
LKE> SHOW /ALL /WAIT
Information similar to the following displays:
%GTM-I-NOLOCKIN, No locks were found in $DEFAULT
AREG
^a Owned by PID= 208000E3 which is HIB
BREG
^b(2) Owned by PID= 208978F2 a nonexistent process
^b(1) Owned by PID= 309800G3 which is CUR
Request PID= 20400630 which is HIB
%GTM-I-NOLOCKIN, No locks were found in CREG
SHOW displays the region and resource name of the LOCK as well as the process identification number (PID) and status of the process that holds the LOCK. For more information, refer to the subsequent section "OpenVMS Process Status Codes." LKE examines all REGIONs listed in the Global Directory.
If there are no LOCKs in a particular REGION, LKE displays an informational message.
When you use the SHOW command to display all LOCKs on the system, LKE also displays the status of the process that owns the LOCK.
^a Owned by PID= 209874F2 which is CUR
The most common OpenVMS process status codes and their meanings are described below.
|
CUR |
OpenVMS process status indicating that the LOCK is held by a "current" process. |
|
COM |
OpenVMS process status indicating that the LOCK is held by a process ready to use the processor. |
|
HIB |
OpenVMS process status indicating that the LOCK is held by a process in "hibernation" (that is, waiting for time to pass). Such a process may be waiting to LOCK a resource name presently LOCKed by another process. |
|
LEF |
OpenVMS process status indicating that the LOCK is held by a process waiting for an asynchronous event (local event flag). A process waiting for terminal input waits in a LEF state. |
|
A nonexistent process |
The process that set the LOCK no longer exists. |
|
A process on a remote node |
The LOCK exists on a remote node so the system is unable to determine its exact status. |
|
A GT.CM server |
The LOCK was set on behalf of a process on another node via the GT.CM software. |
|
No privilege |
You do not have the OpenVMS privilege required to view the status. |
For additional information on these and other OpenVMS process status categories, refer to the OpenVMS System Management Utilities Reference Manual.