Gerald -
You cold perhaps try isolating this work to run in a separate subsystem with
its own dedicated memory pool.
By default, the QZDASONIT database server jobs run in QUSRWRK subsystem (or
QSERVER subsystem, on older releases of the OS) using the base memory pool
(*BASE).
Bryan Deitz prepared this tutorial:
http://wiki.midrange.com/index.php/QZDASOINIT
Another article (beginning on page 3):
http://www.centerfieldtechnology.com/PDFs/August-2005-Newsletter.PDF
-sjl
Gerald wrote:
FYI, cross posted on Midrange and WDSCi lists as not sure where this
question would be most appropriate.
I have a relatively simple SQL statement, that when run on a green screen
via STRSQL takes less than 3 seconds to complete. The result set contains
about 600,000 records.
However, if I use the Database Development perspective in RDi, or the SQL
Explorer plugin in Rdi or the standalone product AQT (advanced query too,
which supports DB2 for i), the same SQL statement takes considerably longer
and by considerably I mean upwards of 15 minutes - if it does complete at
all. (I like to use these tools because they offer options for exporting
the result set to excel which is great for ad hoc requests.)
Does anyone know of any tricks to improve the performance of these type of
odbc/jdbc connections so that they might take advantage of superior SQL
functionality available as when running sql from STRSQL?
midrange.com
