Re: Best practice for distributing SQL UDF

Are you sure about the record not being in SYSFUNCS?

I believe the system adds the record when the object is restored.

Plus you said it works in STRSQL but not in Run SQL Scripts...

In that case, my guess it's a SYS/SQL naming issue with an unqualified function.

Check the naming format, default library and library list configured
in Start SQL Scripts


HTH,
Charles


On Thu, Nov 11, 2010 at 7:21 PM, <phil.seay@xxxxxxx> wrote:

I have an SQL UDF that I created using the SQL CREATE FUNCTION statement.  This resulted in a *SRVPGM (CLE) object and a record in SYSFUNCS.  I would like to distribute this UDF to the other AS/400's in my organization.  What is the best way to do this?

I tried simply distributing the *SRVPGM (via save files and FTP).  This has the advantage of guaranteeing that the same *SRVPGM object is used on all systems. And DSPSRVPGM SRVPGM(CVTDEPT) displays the same information on all systems.  If I use STRSQL, I'm able to invoke the function.  If I use iSeries Navigator 'Run SQL Scripts', I get an SQL0204 error message: CVTDEPT in *LIBL type *N was not found.  I'm guessing it is because the record in SYSFUNCS is absent.

Do I have to run the CREATE FUNCTION command on each system as I did the first (thereby creating a new object) or is there another way of running the CREATE FUNCTION command that adds the SYSFUNCS record without creating a new object?  Thanks!

--
Regards,
Philip Seay

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.