Re: Help with a file allocation problem

["Chris Devous" <cdevous@xxxxxxxxxxx>]

Just to add my 2.7 cents in 1979 dollars adjusted for inflation:

Since you are in batch, you would have to WRKOBJLCK with output *PRINT.

In response to a question I had asked, Scott also posted a few days ago an 
example
of using the QWCLOBJL (list object locks) API in ILE RPG.  This went to 
RPG400-L.
It might be useful for you to adapt Scott's example to message the locks to a
message queue rather than wrkobjlck *all to a printer file.  This would let you 
control
exactly what information comes back, and how it is presented.  This could also 
be
particularly useful if you use SNAPSHOT or something like it to monitor message
queues for a particular message....

Or, if you want to be able to tell a user who has a specific object, with a 
simpler
return than the WRKOBJLCK command...

--Chris

On 21 Feb 2002 at 10:53, Scott Klement wrote:

>
> I generally use a CL program that does something like this:
>
>      1)  call ALCOBJ with a reasonable timeout period to make sure
>              I'll have the necessary access to the file.
>      2)  use MONMSG, in case the ALCOBJ fails.   If it fails, I
>              do a WRKOBJLCK with MBR(*ALL) so that the user can see who is
>              locking the file, then go back to the ALCOBJ.
>      3)  Once successfully allocated, do the CPYF
>      4)  DLCOBJ so that other people can use the file again.
>
> This way, you're in control over the allocation situation (as opposed to
> not finding out about it until the CPYF bombs)
>
>