Re: Record locking

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

Hmm.. let me make sure I get this straight.  The order of events is:
Chain to record
Change data (Add 'D' to status field)
Update Record
Change Data (User readds record)
Chain to Record (This is where lock problem occurs)

Is that correct?

In this scenario, if all reads and writes are done from the same program, I 
don't
see any reason you should be getting  a lock conflict on the second chain.  I am
assuming you made sure this is an actual lock conflict by working with the job,
working with locks, and seeing a WAIT by the file you are trying to chain to.

The only thing I can think to do, or what I would do in this case, is to 
attempt to
reposition the file to a record other than the deleted record after the update 
to
see if that "fixes" the problem.  I would do that for testing to see if that is 
what is
occuring.  How about setting a "SETLL" and "READ" right after the Update and
then running the program and seeing if the problem is gone?

Regards,

Jim Langston

Quazy wrote:

> Well I looked at the call stack and no previous program uses the file, and
> nobody else could be using the file because I am the only person with access
> to these files and they are in test.
>
> The record is locked by the previous update and it just won't let go for
> anything.
>
> I am not updating any logical files so it is not that.
>
> Chris

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