Re: Using a timeout with display files

Never been bitten.  The check-for-changed-data before update, fired maybe 3 times that I recall in all my time 20+ years.
Each time it was a user not following their procedures.  Each time it would not have mattered if the update happened.
I decided it was more effort than it was worth putting in check-for-changed-data before update.
Users never complained that multiple updates happened.
Sometimes as coders we dont see the job from the user perspective.
( heh heh heh an unrelated issue eg. I am minded of IBMs standard of making the constants on a display HI, I did the exact reverse)

Frank


On 19/08/2022 1:34 pm, Roger Harman wrote:

Hard to believe you've never been bitten by overlapping updates.
I would not trust that - But, if it works for you.....


Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power



-----Original Message-----
From: RPG400-L<rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Frank Kolmann
Sent: Thursday, August 18, 2022 6:53 PM
To:rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Using a timeout with display files

Interesting.  Good Stuff.
Would have been good for me to use.

Except for case 1).
I never ever coded to hold record locks not even for editing.
Always released a record immediately after read.
Read and Lock just before update, the update released the record lock.
In the beginning I coded fancy check-for-changed-data before update, but
I found this really was not needed.

Frank