Guardian Procedure Calls Reference Manual

The LABINFO structure is defined for TAL as:
STRUCT LABINFO ( * );
BEGIN
INT
MISC, ! ID type, lock and grant state
! (see below)
USERID[ 0:3 ], ! Process ID or TRANSID (see below)
RESERVED; ! Reserved for future use.
END;
Definitions for the MISC word of the LABINFO structure (the remaining bits are reserved for future
use):
DEFINE
IDTYPE=MISC.<0> #, ! If set: USERID is a process
! ID
GRANTSTATE=MISC.<1:3> #, ! 0=Waiting; 1=Granted
INTENTFLAG=MISC.<4> #; ! Indicates the lock is an
! intent. (an intent is a lock
! internally established by
! DP2 to prevent interference
! from file lockers.)
Considerations
• Obtaining lock information for remote resources
LOCKINFO accepts the designation of a remote resource in searchid and attempts to obtain
the information.
• High-PIN considerations
You cannot specify the process ID of a high-PIN process in the searchid parameter of
LOCKINFO because the identifier does not fit.
If the holder (or waiter) of a lock is a high-PIN process, the LABINFO.USERID field returned
in buffer contains a PIN value of 255 for that process.
• Support for HP NonStop Storage Management Foundation (SMF) objects
The LOCKINFO procedure supports single SMF logical files but does not support entire SMF
virtual volumes. If the name of a SMF logical file is supplied to this procedure, the system
queries the disk process of the appropriate physical volume to obtain information about current
lock holders and lock waiters on the file. If the name of a SMF virtual volume is supplied, but
not a full logical file name, an error is returned.
If you call the LOCKINFO procedure and supply the name of a physical volume, lock
information is returned for any file on that volume that was opened under a SMF logical file
name, but the returned file name is that of the physical file supporting the logical file.
• Increased key limits for format 2 key-sequenced files not supported
The LOCKINFO procedure is not extended for the increased key limits or format 2
key-sequenced files (in H06.28/J06.17 RVUs with specific SPRs and later RVUs) because of
limitations in the returned LIB structure. In particular, the LOCKLEN field in the returned LIB
structure limits the returned locked key length to 255. When a locked key length greater than
255 is encountered, 255 is stored in the LOCKLEN field, and only 255 bytes of the key value
are returned in the KEYVALUE field.
OSS Considerations
This procedure operates only on Guardian objects. OSS files cannot have Guardian locks, so there
is no information to be returned. If an OSS file is specified, error 0, indicating no error, is returned;
the result is the same as calling LOCKINFO on a Guardian file that has no locks.
774 Guardian Procedure Calls (L)