Performance Issues with iSeries Access ODBC

ouelletg

Member
We have an external application that gathers data from many sources all over the country. Then a server that gathers this data processes it periodically and makes calls to the DB2 database (JDE tables) via ODBC – while processing these requests the performance takes a big hit and goes from a few seconds to 50+ seconds each.
The question is – when using ODBC (or even .NET data providers) is there any server setting on the NIC or the DEVD or the DB2 that limits or controls or restricts traffic – especially from a single source tying to maximize the connection.
 
ouelletg,

Some questions. Is teh application that gathers the info just doing inserts or is it also doing updates? If it is doing updates, you might be able to improve performance by checking your indexing strategy over the affected files.

As far as limits or restricts traffic, there is not much that is not 'global'. But you might be able to route your ODBC traffic to a specific subsystem that is running your QZDASOINIT jobs at a low priority.

Tom Davidson
 
Tom provided you a good suggestion. I believe QZDASOINIT jobs are considered prestart jobs so you want to determine your peak load and make sure you are starting enough jobs out of the gate.
 
in the tab "performance" from ODBC configuration,
enable this options: "enable lazy close support", "enabled data compression".
DISABLE "enable pre-fetch of data for queries".
in advanced button, fields "Large objects (LOB) threshold (KB)" and "Record blocking size" put 32 insteaad of 512.

Try, post here if doesn't work.
 
Back
Top