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



Rob, that does look like a function call, as you surmised - and at the later releases, there's much more of that, it seems.

Yeah, it'd be tough to get much out of QADBXREF. But the QADB*FLD tables are probably the source for this view, as well as the other 2 I mentioned - the latter, along with QADBXREF, might be enough to build what the OP wants.

Of course, I keep mentioning something that's already there - if you have Perf Tools licensed product. ANZDBF and ANZDBFKEY.

On 2/9/2012 12:07 PM, rob@xxxxxxxxx wrote:
Vern,
The sql to build SYSPARTITIONINDEXES is several pages long. The only
table I could see in it was QADBXREF. That's been there since V3R1. It
also shows this:
Files accessed by logical file PFILE
File Library LF Format
QADBXREF QSYS SYSPA00001

Now, if you can figure out how to get the key names out of just QADBXREF
I'd be impressed. I started to wonder if IBM is using UDT's, UDF's or
whatever to get the key names. Wait, here's more. But I've got to get
some "real work" done. After all, I am running 7.1 and I don't need to
know this info.
... FROM QSYS.QADBXREF A, LATERAL (SELECT * FROM TABLE
(QSYS2.INDEX_PARTITION_STATISTICS
(A.DBXLIB, A.DBXFIL)) AS X ) AS B ...

So there's the second index or view. And I suppose it cascades from
there...


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.