Re: Shared member lock API

[Ed_DeRyder@xxxxxxxxxxxxxx]

Simon,

>>I am using the QWCLOBJL API to retrieve object locks for files.  I've run into
a
>>small roadblock with shared member locks.  The data retrieved from the user
>>space identifies a lock as a shared member lock but it does not identify which
>>file is actually locked.  WRKOBJLCK permits you to expand member locks with "9
-
>>Work with shared member locks" from the "Work with Member Locks" screen.  The
>>documentation for QWCLOBJL implies that this information is retrievable (it
>>refers to shared files and libraries) but

>You're just not reading the manual properly.  Don't assume the list section is
the only
>part containing the data you need.

>>Is there an API that duplicates that feature?  I could not locate any for V4R4
>>of OS/400.  If there is no API, has anyone written any utilities to do this?

>The API is the one you are already using.  You need to check the values in the
header
>section of the API.  The locks all relate to a single object so there is no
need to
>repeat the file name in the list.

Thanks for the help.  You're right.  I was just looking in the list section.  Of
course, this leads me to another question.  The file that is giving me the most
difficulty is a multi-format logical file that is built over 8 separate physical
files.  While users will rarely have an object lock on the logical file, there
will be numerous locks on each of the physical files, thus the origin of the
shared member locks.

The header section's shared file and library name identify only one of these
physical files (from the manual - "When this field has a value, it applies to
all entries in the list").  I assume it's not a coincidence that the file name
is the first physical file listed in WRKOBJLCK's "Work with Shared Member Locks"
screen.  However, that screen allows you to see all of the physical files
involved in the shared member lock by hitting Enter repeatedly.  I would like to
do the same with my program.  I tried reloading the user space with another call
to QWCLOBJL (using the same logical file name and library), but the shared file
and library name did not change (I didn't think it would, but I tried it anyway
just to make sure.).  Do you have any advice on that problem?

Thanks again,

Ed De Ryder
Ed_DeRyder@kleintools.com



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---