Avoid Record Lock Errors

[MQueue]

** This thread discusses the article: Avoid Record Lock Errors **
** This thread discusses the Content article: Avoid Record Lock Errors0

[bill_ledford]

Re:Avoid Record Lock Errors

** This thread discusses the article: Avoid Record Lock Errors **
One thing I would suggest is instead of just unlocking the file and ending the program, I would redisplay the screen with the new values and a message saying that the record was changed since recording the values and the screen needs to be submitted again.

[B.Hauser]

Re:Avoid Record Lock Errors

** This thread discusses the article: Avoid Record Lock Errors **
Hi, I'd suggest to use 2 files, one that is defined as insert and the other one that is defined as update file, because neiter the enhancement (N) nor the opcode UNLOCK will release a record that is read from an update file under commitment control. In this way using an insert file for the first chain will avoid a lock and immediately for updating the file the update file gets read. Birgitta