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



The SYS* files in QSYS2 are the "SQL Catalog VIEWs". As such that they may limit data to only SQL defined objects when appropriate.
To see the full details about what is excluded/included, refer to the CREATE VIEW statement <SYSVIEWS data or DSPFD>. Reviewing those definitions will show that as SQL catalogs they are including only SQL INDEX details. Also that the data is coming from the underlying System Database Cross Reference tables; the QADB* files in QSYS. Refer to the data available from those underlying files if non-SQL database file information is of interest.
Note: The QADB* files are read-only. The physical files are also inaccessible to ordinary users by authority, but each [or most if not all] have a logical file with the identical format that does give *READ access. So to either create your own LF or access the PF directly [e.g. to create a VIEW], the special authority *ALLOBJ must be adopted. For any user created VIEW or LF, note caveats in CPF32D1. It is best to always access the files with clauses WITH NC FOR READ ONLY

Regards, Chuck
-- All comments provided "as is" with no warranties of any kind whatsoever and may not represent positions, strategies, nor views of my employer

eftimios pantzopoulos wrote:
I have become used to using SYSCOLUMNS & SYSTABLES in QSYS2 to analyse aspects of an applications data base because files created via DDS & tables created through DDL both have their meta-data recorded there.

I recently thought I'd use SYSINDEXES & SYSKEYS (for the first time ever for me) to do some other analysis and realized that DDS defined keys are not present in these files. I realize that a LF is a hybrid beast and shows traits of both a view and an index, but it seems a bit extreme to completely exclude DDS generated entities from some of the system catalog files, but not others.

Does anyone have a link to a definitive document which details this grey area of DDS & DDL overlap in the system catalog, or can provide a comment on the above?

Thanks,
Mike Pantzopoulos


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.