Re: Waiting on a record lock check

Dave,

While it's possible you've found a bug...it's more likely that what
you think is happening isn't what is happening.

Base on what you've described, my guess is that either the program
isn't reading the record and you just think it is because of data left
over in the variables or whatever was locking the record released the
lock and that allowed your program to read the record.

Charles

On Fri, Jul 30, 2010 at 11:08 AM, <daparnin@xxxxxxxxxxxxxx> wrote:

The WAITRCD parameter is your friend.  You can change the default for
the file with CHGPF or CHGLF.  You can also use WAITRCD on OVRDBF to
make a change effective only while the override is in effect.

Based on the advice I tried an override in the CL using the WAITRCD
parameter.  It seems to want to be a bit too friendly.  I did:
OVRDBF     FILE(NSCHGRQFL1) WAITRCD(5)

The program dutifly waited 5 seconds but rather than returning a status
that the record was locked, it went ahead and read the record DESPITE the
fact that it was locked.  This gave me two instances of the program
accessing the same record at the same time.  I removed the override from
the CL and did a
CHGLF FILE(NSCHGRQFL1) WAITRCD(5)

The same thing happened.  This just doesn't seem right.



Dave Parnin
--
Nishikawa Standard Company
324 Morrow Street
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxx
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.