Thank you, I appreciate the extra detail, especially about the DTAQ.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Saturday, December 06, 2014 11:03 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: User Space question

On 06-Dec-2014 10:42 -0600, Gary Thompson wrote:
On Saturday, December 06, 2014 9:26 AM D*B wrote:

... one journaled table with table_name and table_lib as key and one
function getKey could replace all these userspaces, data areas and
all problems could be solved better.

+1


Yet there is potential for a great amount of resources required for an implementation via TABLE [any database *FILE] as contrasted with other potential implementations including a simple space object such as a Data Area (DTAARA) or User Space (USRSPC), to store\update what is perhaps effectively just a few bytes; a pre-loaded Data Queue (DTAQ) is one of my favorites, as explicit locking is reduced to only when concurrently reloading the queue during run-time, but that might be generally avoided by having sufficiently filled the queue while the application was off-line. What is "better" really depends on what are the needs and what are the costs for the overall solution; system-wide, not just the app.

--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].