×
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.
"Mike Jones" wrote
[...]
Modernizing a heritage system with SQL should not be about replacing RPG
I/O with single row SQL fetch statements. You want to incorporate design
improvements at the same time, incrementally at your pace, that leverage
SQL's advanced abilities.
Example:
I wrote an extract program which processes JDE accounting transactions at
the end of each month. It was originally spec'd to use RLA for processing
the detail records for the previous month and categorize and summarize them
based on two master tables containing the information used to
categorize/summarize the data (SETLL's, READE's, and CHAIN's).
On the first production run, we found that it took 22 hours to process the
data. ;-(
I redesigned the program using SQL to create a GLOBAL TEMPORARY table
containing an extract of the previous month's accounting transactions in
QTEMP, joining it with the two master tables, then opened a cursor over the
joined tables.
Subsequent executions of the extract program took less than one hour...
-sjl
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
