Listlocks Example - HP T6553 D45 Reference Manual

FUP Commands

An intent lock is internally generated by a disk process to control combinations of
record and file locks on a file. When a disk process receives a requester for a
record lock, it requests and receives an intent lock on the file. If the requested
record is not already locked, the record lock is granted.
An intent lock indicates that the holder has (or intends to have) one or more
records locked in a file. If a file lock has been issued against a file, intent locks are
not granted—but multiple intent locks can be granted against the same file.

A single LISTLOCKS report can contain inconsistencies (including record locks
that have no corresponding intent lock) because the status of locks can change
while the LISTLOCKS output is being prepared.

If a file has multiple partitions, the file (F) lock indicates a file lock against that
partition, not all partitions.

The LISTLOCKS command returns Error 48 when it is executed against a file on a
remote node and an incompatibility exists between the product version of FUP and
DP2 on the network. Execute the LISTLOCKS command from a copy of FUP
running on the remote node.

If you specify the primary partition of an Enscribe partitioned file, LISTLOCKS
displays lock information (if any) for all the partitions of the file.

The user running FUP must have remote access to any system, which is implicitly
referenced by the ANSI name used in the FUP command. For example, if the ANSI
name is 'CATALOG*', the user must have access to any node on which any visible
catalogs reside, and so on. If the ANSI name is 'TABLE C.S.T', the user must have
access to any node on which partitions of table C.S.T reside, and so on. Users who
want to limit the scope of the command to all SQL/MX objects on the local machine
can use a Guardian wildcard of the form: $*.ZSD*.*.

The above explanation can be used to explain both an error 8551 from ANSI
names or error 48 from the file system, depending on the command that was used.

LISTLOCK supports SQL/MX objects, CATALOG, SCHEMA, TABLE, INDEX, and
PARTITIONS.

LISTLOCKS Example


To display all locks on files contained in subvolume $DATA.SUBVOL that end with
FILE:
-LISTLOCKS $DATA.SUBVOL.*FILE
FUP displays the locks listed for two files (KSFILE and ENTFILE):
\MYSYS.$DATA.SUBVOL.KSFILE
LOCK
TYPE STATE
R G
R G
R W
REQUESTER
ID
\MYSYS.02,132
\MYSYS.$MYPROG
\MYSYS.01,044
File Utility Program (FUP) Reference Manual—523323-014
KEY
LEN KEY/RECORD ADDRESS
10 "AT1200-659"
5 "Z0072"
5 "Z0072"
2-123
LISTLOCKS Example