The transactional record-lock problem is classic!

The short answer is, "don't author transactional workflows that allow an endpoint to lock and hold".

This is why the mainframe world has had CICS since the 1960's.

CICS/400 also exists but has almost completely disappeared.

There exist design patterns for creating well-behaved application workflows.

If you have bad boy applications on your system, the sage advice is, "fix them".

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of a4g atl <a4ginatl2@xxxxxxxxx>
Sent: Monday, June 10, 2024 1:15 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Is there a process that would allow me to take control of an interactive session?

From time to time, a user will be in the middle of entering something like
an order when they get distracted, walk away or go home and leave the
session at that point, locking one or more records and objects.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.