×
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.
Girish
There are a number of things to do. Performance with ODBC, as with any SQL
process, is helped most by having appropriate indexes to support the query.
There is a setting on recent versions of the ODBC driver, to turn on STRDBG
when you run ODBC. Also, to create a joblog in the ODBC server job
(QZDASOINIT). When you STRDBG, optimizer messages are put into the job log,
and some of those messages tell you what index the system may have tried to
use, and other things. The place to find out more about this is the
Database Performance and Optimization manual, listed under manuals under
the Database section of InfoCenter.
There's also a manual from some time ago, on ODBC in Client Access for Win
95, that has lots of good info on this. For example, if the VB app is using
the Jet engine with ODBC, you are dead in the water - it takes the
absolutely worst assumptions for ODBC. Go to
<www.iseries.ibm.com/clientaccess> and click on the "IBM Library" link on
the left. I found
<
http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QBKADE01/CCONTENTS>.
Some of the newer stuff is not there, but it's still the best resource I
know of for ODBC.
OpsNav (recent versions) has some advisory stuff. <COMMERCIAL COMING> And
we specialize in products for optimizing & controlling SQL access. You
could get a demo of one, sql/OPTIMIZER, and see if it'd help you.
<COMMERCIAL OVER>
HTH
Vern - <www.centerfieldtechnology.com>
At 01:07 PM 1/28/2003 -0500, you wrote:
I am working with a 'legacy' type application that interfaces a VB
application (using ODBC) with an AS/400 system file with a trigger on it
to process the data to update yet another set of files.
The problem being experienced is a huge performance hit on the AS/400 - I
had heard that ODBC was slow but bringing the system to it's knees is
another issue.
Is there any tuning I could investigate to make this more efficient..or is
there a way to direct the VB job as it signs on to the 400 to a separate
subsystem or some such..
I'd appreciate the help..
Girish
midrange.com
