RE: UDTF with SQL and JDBC call

Good point!  
UDFs follow a convention of "function overloading".  Basically it means that
you can have a function that has the same name but depending on the input
parms (int, short, bigint, ...) has a different signature and hence takes
different code path.  

More descriptive error message would have helped.
Oh well, I guess it just means it can't find the exact signature and
accordingly figures there is no function user requested.  

Sudha, make sure your input parms data type exactly matches your UDF parms.
This may require type casting, as pointed out by Jay.

Elvis

-----Original Message-----
 Subject: RE: UDTF with SQL and JDBC call

A problem I have had with UDFs is that they can be very picky about the
input parameters.

For example GETRELSEQ takes an integer but c1nmid is numeric(9,0) - Here are
the results:

select GETRELSEQ(c1nmid)              
 from nammsp where c1nmid = 1         
GETRELSEQ in *LIBL type *N not found. 

select GETRELSEQ(int(c1nmid))    
 from nammsp where c1nmid = 1    
SELECT statement run complete. 

Char parms in particular often need to be cast to the right length.

Jay Himes
Liberty University