RE: Finding out which record is locked using QWCLOBJ

Most people access the record, then if the lock error occurs (using whatever
trapping scheme you want to from RPG IV) they can do a test for a record
lock. That way on the people attempting to access a locked record are
delayed the 30 seconds or so. 


-Bob Cozzi
www.RPGxTools.com
RPG xTools - Enjoy programming again.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Grizzly M
Sent: Monday, December 05, 2005 12:56 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Finding out which record is locked using QWCLOBJ

I think maybe I'm adding too much complexity to a simple problem. I
could just use the op code extender 'E' when I chain instead of checking
for a lock. The only problem with that is the job still has to wait 30
seconds(default wait time) until the error is returned. From what I
understand the default wait time parameter is ignored when reading a
database file. I'm assuming that holds true for chaining as well. 


----------------------------------------------------------------------

message: 1
date: Mon, 5 Dec 2005 11:40:25 -0500
from: rob@xxxxxxxxx
subject: Re: Finding out which record is locked using QWCLOBJ

Worse case scenario, combine that information with this?
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/apis/qdbrjbr
l.htm

Rob Berendt