If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
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”?
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
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