MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2008

Re: SQL SYSIXADV STRANGE RESULT



fixed

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






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact