The QADB* files are not accessible for everybody, because the "database" is
stored within this files.
Instead QADBIFLD or DSPFFD you can access the catalog view SYSCOLUMNS (with
SQL) located within the QSYS2 schema which provides information about all
columns/fields in all tables/views/physical and logical files.
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"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!"
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von John Yeung
Gesendet: Tuesday, 05.2 2013 19:50
An: Midrange Systems Technical Discussion
Betreff: QADBIFLD versus DSPFFD OUTPUT(*OUTFILE)
In another thread, someone mentioned getting field information from
QADBIFLD. I wish I'd known about this years ago. Now that I do know about
it, it seems like creating an output file from DSPFFD is a slow and clumsy
way to go about getting essentially the same information.
Are there any advantages to using DSPFFD? Right now, I can think of
two: (1) arguably friendlier for interactive use; and (2) provides buffer
lengths instead of internal lengths (which makes a difference for date,
time, and timestamp fields).
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
This mailing list archive is Copyright 1997-2015 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