Re: Performance question and SQL SERVER

Ah, interesting question - I wonder if the ODBC exit could handle this? I was also wondering if an ODBC connection string can specify a QAQQINI - seems the JDBC set up in Navigator has this kind of thing, although I've never quite got it to work.

Vern

On 6/5/2013 7:25 AM, Mike Cunningham wrote:

How would one set a QAQQINI table to be used by ONLY incoming ODBC requests for one specific user coming from one external web server using one database schema (aka library)?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Clay
Sent: Wednesday, June 05, 2013 8:10 AM
To: midrange-l@xxxxxxxxxxxx; midrange-l@xxxxxxxxxxxx
Subject: Re: Performance question and SQL SERVER - RESOLVED

We has QAQQINI questions when we upgraded to V6R1 so I asked IBM.

Here's the information confirmed by IBM:

.
CASE WHEN Command CHGQRYA QRYOPTLIB(MyLib) has been issued for a job AND Table MyLib.QAQQINI exists THEN Query parms that exist in the table are used instead of the defaults; For options that do not exist in MyLib.QAQQINI, the system defaults are used .
WHEN Command CHGQRYA QRYOPTLIB(MyLib) has been issued for a job AND Table MyLib.QAQQINI does NOT exist THEN The system defaults are used (as documented in QSYS.QAQQINI) .
WHEN Command CHGQRYA QRYOPTLIB(MyLib) has NOT been issued for a job AND Table QUSRSYS.QAQQINI exists Query parms that exist in the table are used instead of the defaults; For options that do not exist in QUSRSYS.QAQQINI, the system defaults are used .
ELSE The system defaults are used
(as documented in QSYS.QAQQINI)
.
END
.

Remember that QSYS/QAQQINI is the documentation of the defaults as used by the system. Don't change data there as it will not affect system but WILL mess up the documentation.

HTH,
Robert

"Contrariwise, if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic."--Tweedledee

On 06/04/2013 8:42 PM, Peter Connell wrote:

Turns out that all I had to do is set one ini file entry to a non-default value.
UPDATE QUSRSYS/QAQQINI SET QQVAL='*ONLY_REQUIRED' WHERE QQPARM ='REOPTIMIZE_ACCESS_PLAN'
Now all 300 SQL requests complete in just under 5 seconds.
That's so blindingly fast that even after writing a C program that runs them all simultaneously via IBM's multi-thread API it still can't do it any faster than 5 seconds.
I'm looking for a reason why I should use a library other than QUSRSYS since it may be that all SQL requests from any other jobs may benefit as well.

Peter

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