When comparing AIS DB2i performance vs the new DB2i Native Endpoint. The results of this comparison is showing a better performance when using the older AIS DB2i Endpoint.
Factors which affect the Db2i Performance:
The DB2i Native and the DB2i AIS are served by different jobs on the iSeries:
Job Default Subsystem
| DB2i Native |
QZDASOINIT |
QUSRWRK |
| DB2i AIS |
QSQSRVR |
QSYSWRK |
Allocating more resources to QZDASOINIT jobs may not be possible, the reason is that these jobs serve all of the activities generated by the ODBC client. Among others this includes end-users using Microsoft Access, and any other ODBC client tool to run ad-hoc queries and reports.
On the other hand the QSQSRVR jobs (used by AIS) are used by local programs running on the iSeries backend itself, and System Administrators may feel more comfortable in allocating resources to these jobs. So there is a fundamental difference between serving remote ODBC clients and local server programs.
Improving the Performance of the Db2i Native:
A workaround would be to identify specific remote ODBC clients as being privileged above other ODBC clients and allocate more resources to them. It is possible to route QZDASOINIT jobs to different subsystems based on the User ID of the connection or by the originating IP address.
For more information, follow these IBM webpages:
Routing by User ID
http://www-01.ibm.com/support/docview.wss?uid=nas8N1021000
Routing by IP address
https://www-01.ibm.com/support/docview.wss?uid=nas8N1019587
.png "Former Employee"){kind=icon}
