AW: Controlling Library List in User Defined Functions

["Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx>]

Hi Steve,

if you execute an UDF or stored procedure, the naming under which the UDF or
Stored Procedure was created will be used.
Even if you use a different naming in your job.
For example, you created an UDF with SYS-Naming and call it from a job with
SQL-Naming.
The SQL-Path is used to find the UDF, but to find unqualified tables and
views or UDFs or Stored Procedures called within the UDF the library list
will be searched.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Coyle, Stephen F.
Gesendet: Tuesday, 07. October 2008 20:00
An: midrange-l@xxxxxxxxxxxx
Betreff: RE: Controlling Library List in User Defined Functions

Thanks to both Elvis and Birgitta.

I created the function in Iseries Navigator, where the naming convention
was set to SQL. I attempted to test the function with STRSQL where the
convention was set to *SYS. 

I changed the Iseries Navigator to *SYS, removed the SET PATH from
within the function and recreated it. Works like a charm now. 

I was under the misconception that the naming convention only affected
the environment. It appears that the function will behave differently
depending on the naming convention it was created under. 

Thanks again...
- Steve