× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

in either way I'd suggest to recreate the SQL stored procedures on the new
system, even though saving and restoring would be enough.
Simply use iSeries Navigator, Generate SQL Scripts for all SQL procedures
and run this script on the new system.
There were several enhancements in the way how SQL procedures are translated
to C (Expression Evaluator), that will speed up the execution of the stored
procedures.
But to take advantage of these enhancements the stored procedures and user
defined functions must be recreated.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von CRPence
Gesendet: Thursday, 14. May 2009 02:41
An: midrange-l@xxxxxxxxxxxx
Betreff: Re: Move Stored procures to new iseries

Carl Galgano wrote:
I am moving a customer from a 5.1 to a 5.4 box. They have about
40 stored proc and I'd like a way to move them easily. I see
they are stored in SYSROUTINES but I can figure out how to move
them either using AS400 commands or SQL. Any suggestions. Seems
like this should be very simple.

External or SQL? If External then were the procedures created
after the programs named in the CREATE, or after; verify by
PRTSQLINF to see if the routine information exists. If there is no
SQL information then either recreate the procedures to make it so
[only possible on programs of specific languages; those which have
SQL pre-compiler support I believe]. If any routines still remain
as both external and without SQL information [e.g. if language does
not support SQL], then either rerun the creation script [SQL
statement CREATE PROCEDURE] on\at the target system, or: upgrade to
v5r2, perform a manual scratch install of the v5r4 system with
[v5r4m5] only the LIC, then restore QSYS2 [and probably wanting to
do so for QUSRSYS & QGPL as well], then finally install the OS and
LPPs. For any SQL or external routines which have their SQL
information, simply restoring [CL command: RSTLIB or RSTOBJ] the
objects will have them registered automatically to the catalogs.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.