RE: Library default with external name clause in SQL UDF.

Eftimios,

What release are you at?
If V6R1, then make sure you have the SI34268 PTF loaded.

If V5R4 or V5R3, I suggest you contact IBM support so they give you a PTF
number for that release, per APAR SE37104:

http://www-01.ibm.com/support/docview.wss?rs=0&dc=DB550&dc=D100&q1=SE37104&u
id=nas2a4786341a354a0e08625756e0041f3c9&loc=en_US&cs=UTF-8&lang=all

or a more clickable URL:

http://tinyurl.com/cdzdk9

Let us know what the IBM says.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Library default with external name clause in SQL UDF.

In my haste to prove the AES encryption process (which now works), I
hard-coded the development library in the external name clause which
references the service program(procedure).

We have a mulit-tier release mechanism which relies on the library list for
all other objects used in the application.

The documentation seems to demand that a hard-coded library be defined. I
tried *libl and it failed.

Is there some other SQL construct that enables the a library name to be
referenced for the resolution of the service program object?