×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Rob,
You are barking up the wrong tree.
Activation groups have nothing to do with "threads" per se.
Also, those locks are normally scoped to the *JOB, and not to the "activation group."
Mark S. Waterbury
On Wednesday, May 26, 2021, 03:34:44 PM EDT, Rob Berendt <rob@xxxxxxxxx> wrote:
Well another problem is that it could be a five program deep call stack. Get's an error and aborts. Bet money that the user will take the option to abort it all the way so that it skips any DLCOBJ in PGMA. It won't matter if the program which died was PGMB, PGMC, PGMD, PME. Now they are sitting fat dumb and happy on their command line but still hold the lock. That's why I'd look at the activation group idea. See if that qualifies as a separate thread.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: need ALCOBJ type lock released when program ends, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com 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.
midrange.com
