|
Have you ever thought about using ACS (Access Client Solutions)--
Schemas to get your file information?
Why is SYSCOLUMNS no option for you?
It contains all information for all columns in all files.
To get all information about a specific file you only need a select
statement:
SELECT *
FROM QSYS2.SYSCOLUMNS
WHERE TABLE_NAME = 'YOURFILE'
AND TABLE_SCHEMA = 'YOURLIB';
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars."
(Les
Brown)
"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!"
„Train people well enough so they can leave, treat them well enough so
they don't want to.“ (Richard Branson)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Craig Richards
Sent: Dienstag, 6. August 2019 10:04
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: DSPFFD utility
DSPFFD with its "Display Spooled File" UI is not very convenient for
quickly scanning the fields and types on a file. And obviously it
doesn't show the database keys.
Most places I've worked use 3rd Party utilities like Synon YWRKF or
some in-house solution.
The place I'm working now uses WRKDBF but that doesn't seem to have
been maintained in a bunch of years and it falls over with an overflow
error on some files which contain CLOBs.
I just had a quick look at Peter Colpaert's WRKFLD which is
downloadable from http://www.think400.dk/downloads.htm but I'm not
sure that's quite what I'm after.
I don't want an editor or anything fancy, but something to show
fields, types, keys and text would be nice.
I know I could write something using the DB APIs or some of the QSYS2
tables like SYSCOLUMNS but at the moment I don't really have the time
or inclination.
I wondered what most other people are using for this kind of thing?
regards,
Craig
--
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
--
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 mailing list archive is Copyright 1997-2025 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.