× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Oh, yeah - I think it's safe to say, SQE needs good indexes. Your best payoff may come from running Visual Explain, to get index advice.

On 3/30/2012 8:06 AM, Vern Hamberg wrote:
Hi Franz

I'm with Tommy - not sure how it could be broken. Does it give incorrect
results? Does it have a different sort order? Does it take too long?

In other words, just HOW is it broken?

If you are not getting the same results, that is a definite bug, and you
need to call IBM RIGHT NOW! =-O

Vern

On 3/30/2012 7:30 AM, Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
I'm not sure why you would have to rely on CQE? They are 2 different
query engines but the results are the same...just faster with SQE. I'm
just not sure how this would break your apps. Anyway you can update
QAQQINI where QQPARM='IGNORE_DERIVED_INDEX' and set it to *NO



From:<franz400@xxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 03/30/2012 06:59 AM
Subject: How to force sql CQE instead of SQE V6r1
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Loaded recent ptfs& DB2 group. v6r1
Now many that used to go thru CQE using SQE.
This broke some apps& need a quick way to
get a production app to use CQE.
These are Windows client .net and some of the sql joins
are huge and ugly.
Have no maintenance window to back down.
Specify logical file in sql no longer forces CQE.
Jim

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.