Sudha, one more thought comes to mind. Are you passing literals in your tests? For example, function excepts a short and you are passing '33' in. System will use a default of 'INTEGER' data type and hence you will have your function mismatch and message that "fn" could not be found. For character it will assume VARCHAR for literals. Bottom line is, either define your function as VARCHAR or typecast the literal with CHAR('mycharinput'). Ideal fix is to create several stored procedures with all these varying data inputs and have them all point to the same UDF. Then you don't have to worry about passing in literals or not. Best way to check what you have defined as data type for input parms is to query the SYSFUNCS system table. Elvis -----Original Message----- Subject: RE: UDTF with SQL and JDBC call One more observation. When I defined the input parms as varying, I successfully created errors in the calling SQLRPGLE also. I got the same fn not found in *LIBL. So I reverted them back to static length. I then created the function in another library that is not in my libl, and got the same error in sqlrpgle. So in essence, this must be a library list problem. I have qualified my java call with library but still have the same problem. I just do not know how to resolve this. Thanks, Sudha
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.