Re: audit journaling source file member adds, updates, deletes -- MIDRANGE-L

Followup - SQL Reference Appendix F (V5R2) has an explicit statement that says not to use the QADB* files in QSYS directly. Rather to use the views.

Granting Privileges to Catalog Views: Tables and views in the catalog are like any other database tables and views. If you have authorization, you can use SQL statements to look at data in the catalog views in the same way that you retrieve data from any other table. The tables and views in the catalogs are shipped with the SELECT privilege to PUBLIC. This privilege may be revoked and the SELECT privilege granted to individual users. QSYS Catalog Tables: Most of the catalog views are based on the following tables in the QSYS library (sometimes called the database cross reference files). These tables are not shipped with the SELECT privilege to PUBLIC and should not be used directly: QADBCCST QADBKFLD QADBXSFLD QADBFDEP QADBPKG QADBXTRIGB QADBFCST QADBXRDBD QADBXTRIGC QADBIFLD QADBXREF QADBXTRIGD

HTH

Vern

At 03:11 PM 9/12/2003 -0700, you wrote:
-snip-

QADBXREF: Yours is the first I've ever heard about not reading the
QADBXREF file - not touching it period.  I've known that it was not
recommended to build logicals on that file, but I've never run into
problems querying the file.  Does IBM warn against this?

-snip-

This mailing list archive is Copyright 1997-2026 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.