Re: SYSCOLUMNS & SYSCOLUMN2

I am only using DSPFFD in the written example of the process for the article Bruce.

Question of how many things you want to teach in one piece and whereas most RPGers are familiar with DSPFFD the number who are comfortable with APIs is I suspect significantly lower.

SQL was and OK alternative as the intent is pretty obvious - but I got bogged down in the differences and took the easy way out!

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

On Nov 26, 2019, at 8:14 PM, Bruce Vining <bruce.vining@xxxxxxxxx> wrote:

Oh my, DSPFFD to an outfile? I believe you'll find the List Fields API
QUSLFLD (
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/apis/quslfld.htm)
to be sufficiently robust for the information you're seeking (that is, what
you find with DSPFFD), And I'm kind of up in the area on syscolumns,
syscolumns2, qdbifld, and/or qadbxsfld not at least making the same guesses
as DSPFFD/QUSLFLD..


On Tue, Nov 26, 2019 at 10:51 AM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Tue, Nov 26, 2019 at 10:18 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

I'm trying to build utility routines that can work through a trigger

buffer - or journal image and identify the individual fields that have been
modified.

You should have led with that. How you are looking at the data matters.

I used the term table because even if created with DDS it is still a

table that can be accessed with SQL. It's origin is irrelevant to my
purpose.

You may not think the origin is relevant to your purpose (which you
didn't reveal until now), but it still may be relevant nonetheless. If
the only tables you were working with were created via SQL, then you
wouldn't be talking to us about the possibility of *MDY dates.

As it stands, what you really care about is how the data is *rendered*
in a trigger buffer or journal image. I personally don't know what
those look like, but if they were built to match what comes out of
DSPFFD, then that seems like the obvious thing to use.

There is a lot of overlap between what you can do with SQL, and what
you can do with DDS and the "traditional" midrange facilities. But
there are areas where they're different, and you're bound to bump up
against them, all the more so when you are working at a fairly low
level (as with the utilities you're writing). And that is what I meant
when I said IBM *could* expose more DDS-specific features through SQL,
but they've chosen not to.

John Y.
--
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