Tried that, both in STRSQL and iNav. It doesn't recognize the
"function" because I created it as a procedure:
Message ID . . . . . . : SQL0204 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Message . . . . : LIBSTATS in QGPL type *N not found.
Cause . . . . . : LIBSTATS in QGPL type *N was not found. If the
member name
is *ALL, the table is not partitioned. If this is an ALTER TABLE
statement
and the type is *N, a constraint or partition was not found. If this
is not
an ALTER TABLE statement and the type is *N, a function, procedure,
trigger
or sequence object was not found.
If a function was not found, LIBSTATS is the service program that
contains
the function. The function will not be found unless the external
name and
usage name match exactly. Examine the job log for a message that
gives more
details on which function name is being searched for and the name
that did
not match.
Recovery . . . : Change the name and try the request again. If the
object
is a node group, ensure that the DB2 Multisystem product is
installed on
your system and create a nodegroup with the CRTNODGRP CL command. If an
external function was not found, be sure that the case of the
EXTERNAL NAME
on the CREATE FUNCTION statement exactly matches the case of the name
exported by the service program.
I guess I could re-write it as a function returning a table.
Thanks, anyway.
Robert
"Contrariwise, if it was so, it might be; and if it were so, it would
be; but as it isn't, it ain't. That's logic."--Tweedledee
On 09/24/2013 3:15 PM, Dan Kimmel wrote:
SELECT MYLIB.* FROM TABLE(QGPL.LIBSTATS(' MyLib ')) AS MYLIB
As an Amazon Associate we earn from qualifying purchases.