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



one further note - Advisor has no advise for these statements.
Jim


________________________________
From: J Franz <franz400@xxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Friday, March 14, 2014 12:13 PM
Subject: when v7r1 SQE is slower than v6r1 cqe


We have a large volume of .net based client code doing sql requests to our i.
At V6R1 is was performing reasonably well. Couple years ago we did have issues
when IBM made adjustments to cqe/sqe via ptf, and after db2 support involved
we did find the qaqqini derived index setting to *no would keep performance ok.
We do set a copy of it to *yes and have many apps use that qaqqini. There are many
posts related to this on this list.
Now updated a test partition to V7r1 and finding some of the problem sql is
going to SQE (and performing badly(68 seconds SQE versus 2 seconds CQE)).
This is old code, not well optimized, & when we previous sent to IBM they said
(at v6r1) sqe would not handle it well. Now at 7.1 and more executing code going
to SQE, it is again an issue.
Is there any ability to turn off the change (IBM sometimes creates a data area
to control version changes)?
Has anyone else felt this?
It's not a quick rewrite, and those developers long gone.
Jim Franz   

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.