Thanks, but I'd much rather do a query in one step rather than having to
create the data and then query it.


On Thu, 16 Jan 2020 at 12:20, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Thu, Jan 16, 2020 at 11:34 AM Vernon Hamberg
<vhamberg@xxxxxxxxxxxxxxx> wrote:

The system catalogs would not have that, as they are very SQL-related,
and this attribute is specific to IBM i.

That rationale is very understandable, but it's not that useful as a
heuristic for predicting what information is *actually* provided in
all IBM-i-specific and would not make sense on other SQL-enabled
systems. (Even if you could find a non-IBM platform which has
something analogous to IASPs, chances are they wouldn't *call* it
IASPs. And in any case, this is utterly irrelevant to *SQL*.)

Even something like NUMBER_DELETED_ROWS isn't really relevant to SQL,
and the fact that it's available (via SQL) on the i makes it
oh-so-tantalizingly close to having something which tells you whether
those rows can be reused or not.

Gord, no matter what anyone says, there is nothing wrong with using
DSPFFD to *OUTFILE. I mean, it's definitely worth taking a look into
the catalogs; and worth asking here in case you missed something; and
you did both of those things. But even if you hadn't checked, and gone
straight to DSPFFD instead, I wouldn't fault you for that.

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,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxx for any subscription related

Help support by shopping at with our affiliate

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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