Re: user record updates via a cobol program: how to deal with record locks and data changes

I use the exact same technique I do in RPG.

Read the record with no lock and keep a copy of the record image.

Present the record for update

Input the user updates.

Re-read the record with lock and compare the record image with the stored one.

If they match go ahead and do the update. If not … error/retry/whatever of your choice.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Aug 5, 2016, at 12:45 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:

What is a good way to handle record locks when a user changes a DB record via a cobol pgm?

Also how to avoid one user's changes from overlaying another user's recent changes.

Is the best way to read with no lock, wait until user enters data into screen, then re-read with a record lock?

And only update the record if there were no changes between the two reads by comparing the entire record strings?


Any other methods that work well?

Maybe read the journal to ensure no one else has changed that particular RRN during the users input?

Thanks!

Joel

--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.