Re: sql using cqe when qaqqini derived is specified

Sorry to not be clear.
(not connected now so some naming may be a little off) - Used the Ops Nav>database>SQL Plan Cache "show statements" option then to Visual Explain for a selected sql stmt:
it references QUSRSYS/QAQQINI file, and the reason for using CQE (and not SQE) as "Derived Index". We verified the Ignore_Derived_Index value set to *YES in this QAQQINI file, which should allow the SQE engine to be used even if derived indexes existed on the files involved. This value we set several years ago to resolve performance issues. In mid 2012 we installed a v6r1 cume & groups (including db2) and immediately some client apps were running all sql under CQE while other client apps still ran in SQE - and afterworking w/IBM Support I believe it was determined we needed the profiles running "these apps" to have a user's special authorities include *jobctl - it had something to do with the Win environment and the way it was accessing the QAQQINI - so we created a group profile and added these users to the group, and it worked. Somewhere in the qaudjrn there should be records of the auth failure, but I'm not authorized to see it.
Today I sent the OP, not recognizing this as the same issue as over a year ago, and only later learned Operations had never added newer users to the group profile.
I'm not on the win development side, but they utilize multiple development studios to support a number of apps (old & new), and I would say they all work different. One is OLE DB, one is ODBC (but not the IBM driver) the others I'm not sure. We see different i programs handling the requests, and yes they are moving to consolidate. The larger application set is still RPGLE where I reside.
Jim Franz


----- Original Message ----- From: "CRPence" <CRPbottle@xxxxxxxxx>
Newsgroups: midrange.midrange-l
To: <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, June 27, 2013 3:12 PM
Subject: Re: sql using cqe when qaqqini derived is specified

Does that mean to imply the users could not effect the override to
the defaults [per an inability to effect CHGQRYA due to authority]? If
so, that seems in conflict with a claim to have "verified the QAQQINI
used has the Ignore Derived Index specified." Did I incorrectly infer
what was the resolution, or what was the original problem, or could
something else be offered to explain my confusion about what I inferred
to be logically disjointed comments?

Regards, Chuck

On 27 Jun 2013 12:37, J Franz wrote:

I get to answer my own posting....
V6R1 updated via ptf new requirements for authorization for
db2 requests and we had new users not in the group set up
for this. We solved this a year ago, but not maintained.
http://www-03.ibm.com/systems/resources/systems_i_db2_navigator_security_controls.pdf

J Franz onThursday, June 27, 2013 12:36 PM wrote:

I can view the Visual Explain, see that CQE was used, reason is
Derived Key or Select/Omit Indexes, yet verified the QAQQINI used
has the Ignore Derived Index specified. <<SNIP>>

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.