True enough, Darryl - but that doesn't stop you from writing code anew that does what you want - briefly, read a record without a lock, preserve its value (using a DS for I/O is nice here), show the update screen, after enter pressed, read record again with lock (probably?), compare to saved state, if the same, update it, if not the same, notify user appropriately.

How's that, Jack, close enough for government work? I'm sure there are foibles lurking in that description, but it's maybe a start.


On Mon, 10 Jun, 2024 at 5:13 PM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:

To: midrange systems technical discussion

In the world of SOX, your solution is not possible. The user management has
the last say and will not justify spending time on modifying code, Just too

So the only solution is to access the job and respond on behalf of the user.


On Mon, Jun 10, 2024 at 5:50 PM Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:

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

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

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> on behalf of a4g
atl <a4ginatl2@xxxxxxxxx<mailto:a4ginatl2@xxxxxxxxx>>
Sent: Monday, June 10, 2024 1:15 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx> <midrange-l@xxxxxxxxxxxxxxxxxx<mailto: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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related

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.