Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (L)
Guardian Procedure Calls Reference Manual—522629-013
8-19
LOCKINFO Procedure
(Superseded by FILE_GETLOCKINFO_ Procedure )
21 buffersize is less than the minimum.
22 The address of
ctlwds or buffer is out of bounds.
41 Checksum error on
ctlwds. The ctlwds parameter has been altered
between calls to LOCKINFO or was not initialized before the first call.
45 Information for one locked resource was returned, but the supplied buffer
was too small to hold all available lock accessors information (the number
of holders/waiters that could be returned is always found in
LIB.NUMLABS). More locks may exist, so continue calling LOCKINFO
(with
ctlwds unchanged).
Other file-system errors may be returned; these are documented in the
Guardian
Procedure Errors and Messages Manual.
•
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.
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.