× 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.

So in an intel environment you would simply “add another pizza box” with
multiple cores and mesh them together without a thought, but you won’t add
a core to the IBM i environment?

What you are describing would work better on Maria or other database?

It seems to me to be as much of an architectural problem as anything.
Maybe some 2nd Normal form tables maintained with triggers and such might
make the queries run faster? Other techniques are available too.

On Mon, Aug 22, 2022 at 12:26 AM Steve Richter <stephenrichter@xxxxxxxxx>

On Sun, Aug 21, 2022 at 7:44 PM Larry "DrFranken" Bolhuis <
midrange@xxxxxxxxxxxx> wrote:

ABSOLUTELY Agree with Brad here and DISagree with Steve.

Check out www.grar.com as one example.

Hi Larry,

That is a very nice web site. Most of the apps I write are behind the
firewall, business apps. The equivalent of an AS400 batch report where the
report is loaded into the browser and the user can interact with all of the
printed values. Batch jobs which print reports can sometimes run for
minutes. Even longer. The system can handle this kind of on demand web
code. But once you hit the limits of the system there is no way of putting
the web users on the job queue.

A good example is a PO worksheet web app. The user wants to see all the
items in the item class and sub class. There are multiple values that have
to be summarized for each item. And the company purchases item A, but sells
that item A as item B, C, and D. So YTD sales and inventory of item A have
to be summarized as an SQL join from the purchase item to the sold as
item number table. The SQL procedure that produces the PO worksheet is
really very nice to look at. SQL functions return what is on hand, what is
available for sale, sales within a date range, etc. Then the code uses
correlated queries to process the data in multiple passes. The first pass
calculates a bunch of columns. Then on the next pass through the data
those calculated columns are input to SQL functions which calculate more
columns. Really very nice in that the code is doing a ton of work, but it
is still fairly readable. Only problem being that we only have a single CPU


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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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-2023 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.