× 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.



rob@xxxxxxxxx wrote:
<snip> BTW the default value for IGNORE_DERIVED_INDEXES in the
QAQQINI-File get changed in release 6.1. from *NO to *YES. </snip>

I believe that SSA is going to issue a statement to change it back.
I was talking to a whole team of them and I think they just were
afraid it was "change" and some of their customers might hit a
situation where that would have a negative impact - not that they
know what that situation might be...

If the SSA app has lots of queries that run CQE [Classic Query Engine] that depend on their various Slt/Omt logicals, and where sufficient SQL INDEX beyond those select\omit lndexes do not exist for use in SQE, then the change to the default may indeed be an issue for their application. That is because the application would then be running its queries using SQE, but without the benefit of any existing indexes [that are enabled to be used].

FWiW if such a statement were made [i.e. to revert the changed default], then it should probably recommend also [esp. for those who do not have an established QAQQINI file], that a QAQQINI file specific to their SSA activity is created and activated via CHGQRYA QRYOPTLIB(). In that manner the *non-SSA* query activity gets the benefit of the ability to use the improved SQE [SQL Query Engine] irrespective of the existence of any s/o logicals; i.e. as is the intent of the new\changed default.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.