File Utility Programming (FUP) Reference Manual
FUP Commands
File Utility Program (FUP) Reference Manual—523323-015
2-129
LISTLOCKS Example
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.
LISTLOCK command supports key-sequenced file with increased limits.
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 REQUESTER KEY
TYPE STATE ID LEN KEY/RECORD ADDRESS
R G \MYSYS.02,132 10 "AT1200-659"
R G \MYSYS.$MYPROG 5 "Z0072"
R W \MYSYS.01,044 5 "Z0072"
R G \MYSYS(1):14:3342 12 "values" ?0 ?11 ?6
\MYSYS.$DATA.SUBVOL.ENTFILE
LOCK REQUESTER KEY
TYPE STATE ID LEN KEY/RECORD ADDRESS
R G \MYSYS.$MYPROG 477184
R G \MYSYS(162):15:002314 2502656
R W \MYSYS.01,044 11264000
F WI \MYSYS.$MYPROG
The locks in this example are grouped by locked resource. A locked resource occurs
when the locks on a file are grouped together, and the locks on a record in that file are
also grouped together.
When the file-set list is a single full volume (for example, $volume.*.*), a volume
request is made to the Guardian file system to retrieve the lock information. The lock
information is retrieved quicker (but unsorted), and FUP displays it in unsorted order.