Published using Google Docs
Optimizing SQL perf/ISeries
Updated automatically every 5 minutes

[PlanetJ Corporation]





Optimizing iSeries SQL Performance


JDBC connection properties:

Controlling SQL Using the QAQQINI file:

Changing job priorities for QZDASOINIT Jobs:

Improving Query Performance:



This document describes some of the optimization tools and techniques related to WOW development on the IBM System I.  WOW uses standard IBM interfaces and APIs.  These interfaces include IBM’s ODBC/JDBC interface which allows remote SQL to be performed.  Since these interfaces are IBM supplied, all traditional work management and SQL optimization techniques are applicable and outside the scope of WOW’s direct control.  The following items are supplied as a convenience for IBM System I customers.   

JDBC connection properties:

WOW uses IBM’s JDBC driver for SQL access.  Many properties can be set the WOW connection as shown below.  When changing properties, you must restart the connection for them to be applied.  

• List of properties: 

• All properties are in the form of key=value and separated by a “;”  (semi colon).  

• Properties include date/time formats, performance, logging, etc

Controlling SQL Using the QAQQINI file:

A WOW SQL operation when executed is simply sent to IBM’s SQL processing APIs.  When execution starts the processing occurs totally within OS/400.  Some SQL queries may result in long execution times that affect other users.   IBM has supplied a database file to allow users to “control” different aspects of the SQL execution such as query timeout.  Follow these instructions to setup your own query control file.  IBM’s supplied file is called QAQQINI.  

1. Create a duplicate object using this CL command:


2. Add a connection property to specify which library to locate the ini file to your WOW connection.  Refer to the JDBC Properties section for an example.   To use QAQQINI file in library  QGPL, you would specify   “  ;qaqqinilib=QGPL;   “

3. To control SQL execution, modify the records in the file QGPL/QAQQINI.  You can easily do this by created a WOW admin SQL operation such as:  SELECT * FROM QGPL/QAQQINI .  The field with the attribute setting is QQVAL.  Each row contains a description of the attribute.  In the following example, we have set the maximum query execution time to be 14 seconds for the attribute QUERY_TIME_LIMIT.   Details of each controllable setting can be found here:

4.  Restart the WOW connection and test.  

Any SQL that may take more than 14 seconds to execute would receive an exception and not execute as shown below.  

Other Useful QAQQINI Settings:

• Parameter name='IGNORE_DERIVED_INDEX', parameter value='*YES'.  This setting forces your IBM iSeries (in V5R2 or higher) to run the new SQE engine no matter what job it is processing.  There are times when DB2 for i5 chooses to run with the old CQE query engine.  If a query is run using the old CQE query engine, the query can sometimes run significantly slower.

Changing job priorities for QZDASOINIT Jobs:

WOW uses IBM prestarted jobs for SQL access.  These jobs have the name: QZDASOINIT and can be found using the CL WRKACTJOB command.   By default these jobs run at priority 20 which is the same as interactive jobs.  You can control the priority and resource usage of these jobs.  In this example, the priority is changed to 21, which is slightly lower than its default value of 20.   This will reduce the impact to interactive users.  Note that most interactive jobs run at priority 20.  


2. Verify that the status is Active. If not, use WRKSBSD *ALL/ QSERVER

to find the active subsystem. Note the library (normally it's QSYS).

3. Substituting the library from step 2 in the FROMLIB parameter:



4. Change the run priority on the new class: CHGCLS CLS(QSYS/QPWFJDBC ) RUNPTY(21)     NOTE:  Evaluate the other parameters on the CHGCLS command and set as appropriate for your organizations environment.  



7. Depending on your system configuration, the subsystem may need to be restarted.



Once changes are in place, any new QZDASOINIT jobs will run at the new priority (21).   The following screen shot shows JDBC jobs lowered to priority 23.  

Improving Query Performance:

There are a variety of methods for analyzing a query for performance.  The below suggestions are for creating indexes that the queries would use:

1. Run STRDBG, run the query via STRQSL, then check the job log for suggestions.

2. For V5R4 and later, the iSeries Navigator has a Database option called the Index Advisor


Monitoring SQL Performance Using IBM Index Monitor