Re: Record Lock under Commitment Control

Hello Joep,

Am 25.02.2022 um 06:29 schrieb Joep Beckeringh via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

One other thing I forgot to mention and which I think is a flaw: in subroutine CHGREC you keep the record locked, while the user is looking at the screen. Or is on the phone with a friend, or is out for lunch, or has gone home without closing his session. In our code that is a definite nono.

This behavior is a deliberate decision on my behalf.

I had it once with a customer of ours
[…]
We turned to his screen, pressed Enter and everyone could continue.

I'm aware of such situations. Maybe use a piggy bank and charge the user in question, *if* he was aware about the consequences of what he was doing. :-)

So, locking a record in job in status DSPW: don’t do it.

I had this discussion in the pastime in this group multiple times. Also, see my other answer to you, where I provided some details for my decision. There are reasons to lock long and safe, and there are reasons to lock short, and confront the user with updates someone else has done meanwhile. As always "it depends" which way to go. :-)

:wq! PoC