AW: SQL SYSIXADV STRANGE RESULT

Hi,

If what you say is correct then on V5R4 the SQL optimiser is not looking

at LGL files and uses only SQL indexes.

Both CQE and SQE optimizer search access paths stored in DDS described
logical files AND SQL indexes.
Even though access paths stored in DDS described logical files with
select/omit clauses cannot be used by the SQE.
If there are DDS desribed logical files with select/omit clauses built over
the specified physical files the query gets automatically executed by the
CQE, except QAQQINI is used and IGNORE_DERIVED_INDEX is set to *YES. In this
case the queries can be executed by the SQE, but all access paths stored in
DDS desribed files with select/omit clauses are ignored.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Frank.Kolmann@xxxxxxxxxx
Gesendet: Thursday, July 31, 2008 03:16
An: midrange-l@xxxxxxxxxxxx
Betreff: Re: SQL SYSIXADV STRANGE RESULT


Thanks Chuck

If what you say is correct then on V5R4 the SQL optimiser is
not looking at LGL files and uses only SQL indexes.
I cannot believe that is true. If it were true we I believe we would have
SERIOUS performanance issues.

I still reckon SYSIXADV is broken, probably because it does not consider LGL
files as SQL indexes.

Frank Kolmann

--- Message from CRPence <CRPbottle@xxxxxxxxx> on Wed, 30 Jul 2008

19:09:44 -0500 -----

To: midrange-l@xxxxxxxxxxxx
Subject: Re: SQL SYSIXADV STRANGE RESULT (WAS Way to get STRSQL

SELECT to run in batch?)

The displayed file information does not show SQL attribute of INDEX,
so the access path characteristics might not be preferable for SELECT
queries. Perhaps created as an SQL INDEX the results would change.

Regards, Chuck

Frank.Kolmann@xxxxxxxxxx wrote:

If it worked, the V5R4 file SYSIXADV would be a very powerful and
time saving function. I use STRDBMON to get the same info, but I can
only do that when the job is running. We have BPCS and IIM is the
Item Master.

I used the SQL below and IIM came up. I could not believe my eyes,
we are quite diligent and anyway there exits a LGL with the exact
key advised with no other Selects etc etc.

So either SYSIDXADV is broken or something else is not set properly.

Any suggestions?

TIMES_ADVISED TABLE_SCHEMA NAME LAST_ADVISED KEY_COLUMNS_ADVISED
56,674,993 LIB IIM 2008-07-31-09.30.19.926679 IPROD

<<SNIP DISPLAY FILE DESCRIPTION output>>