Manage Learn to apply best practices and optimize your operations.

"Real And Secure Record-Lock" Is Only For A Small Non-Distributed Environment

I am writing to reply the "Real and secure Record-Lock" article. The strategy
that the article described only works for a small non-distributed (no
replication happen on the database between servers) database. Why ? Let me
explain it. First of all, Because the entire method is depending on a "lockdoc"
which capture the unique document number of the original at the time the
document is being edited. Think about people is making change on the same
document that reside on different replica copy. The process will fail.
Secondly, if system crash during the edition of the document, then, an
un-wanted "lockdoc" will stay with the system and user will always get "lock"
message on that document all the time.

People is trying hard to do bullet-prove record locking strategy in Lotus Notes
database. But you have to remember the strength of Lotus Notes.

Dig Deeper on LotusScript

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.




  • iSeries tutorials's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...