RE: Query engine question

Add a dummy parm on the WHERE clause, i.e.:

SELECT ....... WHERE ..... AND UPPER('A') = 'A'

UPPER is considered 'translation' by the query dispatcher and will force the
query to go CQE path even on V5R4.

On V5R3 only, you might use a similar trick with LIKE keyword.

Elvis 

-----Original Message-----
 Subject: Query engine question

Does anyone know how to force a system running at V5R3 to use the CQE
engine and not the SQE engine?  We have been working with IBM on this,
but our management is very concerned about how long this is taking to be
resolved.  
We have an issue of when we process a SQL statement on our development
partition the SQL runs using the CQE engine and processes in 4 seconds.
When we process the exact same SQL statement on our production partition
the SQL uses the SQE engine and processes in 204 seconds.
We have also found in iSeries Navigator looking at the statistic
collections are different.  On development the collection is stale, on
production it is not stale.   
We have verified each partition is at the same PTF level and group
level.  IBM said we seem to have found a bug for the engine selection.
Any help with this is greatly appreciated. 

Bruce Barrett
PMI Mortgage Insurance Co.
3003 Oak Road
Walnut Creek, CA 94597
925-658-6152
510-520-4263 Cell
bruce.barrett@xxxxxxxxxxxx

This e-mail is confidential and may be privileged. If you are not the
intended recipient, please destroy this message and notify the sender.