Brian Tkatch wrote:

> You need to DROP and CREATE the function, or at least, GET/PUT. Just
> changing the file on disk will not tell the database that new code is
> there.

This is not true!! You don't need to drop/create the function as this is a
particular troublesome issues if other objects (views, triggers, functions,
procedures, packages) depend on the function. The only thing you have to
ensure is that the cached version of the library is not used any longer,
and ways to accomplish that were already discussed.

I'm not quite sure if changing the external name via ALTER FUNCTION ...
EXTERNAL NAME '...' and using the same library as before would help as
well. I rather doubt it, however, and using a different library name as
the OP did would be the safest way.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany