Re: record locks

Dave,

Not a Yank, although from the same side of the pond (I'm from Venezuela).
Already somewhat awake :-).

My trusty V5R3 RPGLE Ref. Manual states that:
******************
*Note: *If the file being read is defined as update, a temporary lock on
the next record is requested and the search argument is compared to the key
of that record. If the record is already locked, the program must wait
until the record is available before obtaining the temporary lock and
making the comparison. If the comparison is unequal, an EOF condition
occurs, and the temporary record lock is removed. If no lock (’N’ operation
extender) is specified, a temporary lock is not requested.
******************

So, as Dennis stated, if a %EOF conditions exists, the lock should
disappear. Also, if a WRITE is done, being a new record I suppose that the
lock should be released. Nevertheless, this is more a gut feeling than hard
data, as most of the times I used READ/WRITE it was done using two versions
of the same file.

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries