RE: Move stored procedure definitions to another AS400.

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

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.  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.  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