Rad:
I put all my UDFs in a folder, then use a tool to recursivly resolve which UDFs from that folder are needed to complete the script. The result is a larger script, but it's complete and not dependent on external libraries, thus more portable in my environment. Also, updating the library UDFs won't impact the production scripts until they are re-genned, tested, and distributed.
You can get the KGen tool from my web site - go to the Products section / Admin ToolChest / Kix Development for more info and a download.
You might at least be able to use the resolution routines to include the UDFs. There's an option in the code to either embed the external UDF (which is how I use it) or to insert a reference to the external UDF file via a CALL statement. Using Executes, you might even be able to develope a self-referencing script that automatically loads all needed UDFs at runtime. 
Glenn
_________________________
Actually I
am a Rocket Scientist!
