Re: Automatically Kill job that Lock record

["James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>]

On 6/16/25 7:25 AM, Charles Wilt wrote:
> You really need to fix the program(s) holding the record lock.
>
> Read with lock
> Display
> Update
>
> Has been a bad idea since RPG existed.
>
> Read w/o lock (and save)
> Display
> Read with lock
> Compare to Saved version
> If unchanged, update with users changes

That, and also set up your program so that it will eventually time out.

Our client-server applications are set up with the client sending a 
"heartbeat" request every thirty seconds, when otherwise idle, to verify 
that it's active, and the child-server job handling the connection 
timing out if it goes for two minutes without a request.

--
JHHL