Re: Record Lock under Commitment Control

On Thu, Feb 24, 2022 at 12:45 PM Patrik Schindler <poc@xxxxxxxxxx> wrote:

I noticed that Patrik didn't say anything about whether he did an update in the first session before attempting to access the same record in the second session.

The answer would have been: The screen was still just sitting there in the EXFMT for CHGREC.

This issue shows to me: Things are often not that easy as they look at a first glance. ;-)

True. However, my take on RPG and display file mechanics is that
they're designed to be straightforward to use for straightforward
cases.

When one user has a database record open on their screen, and that
user has the capability to update that record, then it seems to me
that the simplest, safest, and most obvious thing to do is to not let
any other user open that record for update. And that is exactly the
behavior you described.

It's fairly unsophisticated, but effective. And if you stick to this
model, it *is* about as easy as it looks.

John Y.