Re: Move stored procedure definitions to another AS400.

On Monday 05 May 2003 17:53, you wrote:
> Dieter wrote:
> >The real problem arises, if you want to move a SQL
> >procedure to another as400. This stuff must be created
> >(and compiled) on the target system and often customers
> >don't like compilers on production systems, or are not
> >allowed to have.
> >In my opinion deployment of stored procedures is
> >rather bad supported on as400.
>
> When I originally create a stored procedure, I put the CREATE PROCEDURE in
> a source member that I can run with RUNSQLSTM.  Then, if I ever need to
> re-create it, I can simply re-run the RUNSQLSTM command.  

no problem until here 

As far as moving
> the SP to another box goes, SAVOBJ/FTP/RSTOBJ followed by RUNSQLSTM to
> process the CREATE PROCEDURE command works quite well.  

I was talking about sql procedures (language SQL!!!) and those need a c 
compiler and QSYSINC installed - on any system you run the create procedure. 
Or how did you manage it???

Dieter

No compiler needed
> on the customer machine.  If the customer does not have the SQL kit,
> CRTQMQRY/STRQMQRY can be used on either the production system or on the
> customer system to create a script.
>   --buck
> _______________________________________________
> This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
> mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.

-- 
mfG

Dieter Bender


DV-Beratung Dieter Bender
Wetzlarerstr. 25
35435 Wettenberg
Tel. +49 641 9805855
Fax +49 641 9805856
www.bender-dv.de