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



Dieter has reminded me of one possible reason to avoid the system tables - which is the authority level required. Unless I misunderstood an earlier comment - you need well beyond regular user authority to use SYSCOLUMNS whereas most anyone can use DSPFFD.

Is that correct?


On Nov 27, 2019, at 4:34 PM, Bruce Vining <bruce.vining@xxxxxxxxx> wrote:

Dieter -- Unfortunately QADBIFLD and QADBXSFLD do not contain all of the
information found with DSPFFD/QUSLFLD. For instance the buffer length of
10 for a date field in *ISO format.

Jon -- If you do a DSPFD of SYSCOLUMNS and SYSCOLUMNS2 you'll find these
QADB* tables are used in the view definition.

PS -- In my earlier post I'm not sure where the "...I'm kind of up in the
area on...". That was supposed to be ..up in the air...

On Wed, Nov 27, 2019 at 11:27 AM D*B <dieter.bender@xxxxxxxxxxxx> wrote:

<Jon>
Not familiar with qdbifld, and/or qadbxsfld - where do they fit?
</Jon>

... q[a]dbifld and qadbxsfld are part of the repository views in sysibm
and
qsys2. Out of my head they should contain all info of DSPFFD and co. (they
are base of the commands and APIs, I suppose). The problems with these
are:
it's not guaranteed that the layout won't change with new releases and
access is restricted to privileged users. The apis and the "nice" and
"modern" UDTFs don't have the built in wizards and help information the
command interfaces of AS/400 have. From APIs to commands with outfiles was
a
step forward and introducing UDTFs is a step back!!!

D*B

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com



--
Thanks and Regards,
Bruce
931-505-1915
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


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.