RE: Getting SQL0204 in CLI on V5R1 machine

Hi Elvis

Yeah, maybe - did not try that. I had added the library to the user portion of 
the library list in the stored procedure. My bewilderment comes partly because 
the function is found when run from OpsNav but not from CLI. I had thought that 
setting the default library in CLI would do the same as setting it in the JDBC 
connection options in OpsNav, but it seems not to do so. Besides, it is ignored 
when using system naming.

I did get it working today by compiling the stored procedure external program 
with SQL naming and DFTDBRCOL of RJSIMAGE and qualifying the function with the 
library name. And this will work back to V4R4, which we still support with this 
product. I think CLI might be broken, but there's no way a PTF would find its 
way back that far.   ;-)

Thanks
Vern

-------------- Original message -------------- 
From: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> 

I think setting SQLPATH might help. That's what tells the system where to 
look for UDFS, stored procs and like (but not tables). 

Or CHGSYSLIBL :) 

Elvis 

-----Original Message----- 
Subject: Getting SQL0204 in CLI on V5R1 machine 

Hi all 

I am befuddled. 

I have an external user-defined function and an external stored 
procedure that uses the UDF in a WHERE clause. 

If I call the stored procedure in the iSeries Access statement 
processor, it works fine - the UDF is found and does what I want. 

If I use the UDF in interactive SQL, it is cool, too, so long as I 
have the library list set to include the library (RJSIMAGE) I 
specified on the CREATE FUNCTION statement. 

But I need to use the stored procedure in RPG, so I am using CLI, 
because the stored procedure returns a result set. And I get the 
SQL0204 message