The performance architecture of the iSeries Access for Windows ODBC driver

For the iSeries™ Access for Windows^® ODBC driver, all of the internal data flows between the client and the server are chained together, and transmit only when needed.

This reduces server utilization because communications-layer resources are allocated only once. Response times improve correspondingly.

These types of enhancements are transparent to the user. However, there are some enhancements which are exposed on the iSeries Access for Windows ODBC Setup dialog. Look at the online help on the Peformance tab of the setup GUI or refer to the Performance options on the Connection String keywords descriptions for more information. A few of these performance options are also discussed in more detail at the following links:

Select a stringent level of commitment control
Do not use commitment control unnecessarily. The overhead that is associated with locking not only increases utilization, but also reduces concurrency. However, if your application is not read-only, commitment control may be required.
Fine-tune record-blocking
Record-blocking is a technique that significantly reduces the number of network flows.
Use Extended Dynamic SQL
Use the ODBC call level interface to dynamically run your SQL statements.

Parent topic: Performance-tuning iSeries Access for Windows ODBC