My understand is that you lock a record any time you read it for update. The lock goes away automatically after the update is performed, or when the next record is read. Once it's locked, other processes can't read it for update. You can release the record yourself with the unlock op code in RPG, or you can read it with the no-lock (N) modifier on the chain or read operation, but once you've done that, you can't update it.

Pete Hall
http://www.pbhall.us/



Booth Martin wrote:

Last night a comment was made that startled me.  Is it possible this
statement is correct?

"If you access a physical file, even if its keyed, by its relative record
number to update it, you will never get a record lock in other programs."


---------------------------------
Booth Martin
http://www.martinvt.com
---------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.