Re: OVRDBF with WAITRCD(*IMMED) and Record Lock Issue.

Another option would be to catch the error on the read for update, then perform 
a READ(N) for the same record, then move forward in your loop to try to 
retrieve the next record for update.

However - the CHAIN will not be all that slow, since the record will already be 
in memory.  You won't be waiting on disk!

mp


> > One solution would be to read it with no lock first, then CHAIN out to the 
> > file for update.  If that chain > fails, read the next record.
> 
> Thanks Michael,  I dont want to go that way because this program deletes 
> millions of records and I need to keep it as fast as possible,  that is why I 
> am reading sequential and blocking records. The overhead of a chain on each 
> record might slow it down considerably.
> 
> But I will test it out to see if does return control on the 
> CHAIN and post the results.
> 
> 
> 
> Regards
> Mauricio