On 3/29/11 4:28 PM, James Lampert wrote:
Ok. Now I have working scalar UDFs to implement my "Display Value"
conversion, and I've even got a VIEW that incorporates a call to it.

But here's something interesting <<SNIP UDF CREATE statements>>

If I call the DISPLAYVAL function from either a stored procedure
called from STRSQL, or a SELECT statement executed in STRSQL, or by
opening the aforementioned VIEW from STRSQL, I get the expected (and
desired) results, as long as WTFLDD and WTTBLE exist somewhere in my
*LIBL.

But if I use SQuirreL SQL (which uses JDBC), any attempt to use the
functions will result in this:

> Error: [SQL0204] WTTBLE in *LIBL type *FILE not found.
> SQLState: 42704
> ErrorCode: -204

(I also get the same message if I try to use the UDF from STRSQL
without the *LIBL set properly)

I've tried SET SCHEMA, and that doesn't seem to do a damned thing.

I'd like to have DISPLAYVAL automatically recognize, and use,
whatever library is used for the data it's being fed.


The library [list] and naming specifications for JDBC have already been mentioned by other(s). However the output from PRTSQLINF issued against the *SRVPGM objects created by the CREATE FUNCTION requests, reviewed for the naming OPTION and the SQLPATH, might be additionally instructive; esp. in conjunction with "SQL Path" and "SET PATH" documentation.
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/db2/rbafzpath.htm
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/db2/rbafzsetpath.htm

Regards, Chuck

This thread ...


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

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