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


  1.  Home
  2. MIDRANGE-L
  3. July 2020

Re: Switchback to classic SQL engine for runsqlstm

The SQE_NATIVE_ACCESS setting might be 7.3 only, according to that page. And it might have been removed after 7.3.

On 7/29/2020 2:22 PM, Rob Berendt wrote:
Some of those are dependent on the version of IBM i and are not under your control at all. If you want the statement on that look at:
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzajq/queryoptimize.htm
Now click on "Change version or product" and change that from 7.3 to 7.2 and notice the difference in that section.

See also SQE_NATIVE_ACCESS at https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzajq/qryopt.htm
But this does not "lock" you into SQE or CQE. It will try what you select but will run the other if it cannot. For example if RUNSQLSTM forbids itself from running in CQE after a certain release then you'll run in SQE. Heck, it may even be certain statements within RUNSQLSTM.

Rob Berendt


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.