Comments on: Records lock error http://itknowledgeexchange.techtarget.com/itanswers/records-lock-error/ Tue, 21 May 2013 07:47:26 +0000 hourly 1 By: yorkshireman http://itknowledgeexchange.techtarget.com/itanswers/records-lock-error/#comment-97490 yorkshireman Thu, 06 Oct 2011 07:16:38 +0000 #comment-97490 You need a design level standard

Don’t lock the record.

Don’t ever write anything that locks a record – ever.

Except just before you update it.

read and display
read and display
decide an update is needed

read the record for update (lock)
check it hasn’t changed since you displayed it ( tell the user if so)
update it
release the lock

read and display
read and display
blahblah

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/records-lock-error/#comment-81510 tomliotta Wed, 15 Sep 2010 01:53:20 +0000 #comment-81510 You will get a ‘lock’ error if you try to update a record that is currently locked by another program. You cannot turn that off. You can read locked records; but if you later try to execute an update against that record, the lock in the other program will prevent DB2 from obtaining the lock for your program (which is beyond your control).

So, as Phil asked, what are you saying with “change the setting to no records lock”?

Tom

]]>