Re: Stored procedure that calls another program

Assuming that the stored procedure is written in RPG it can call anything it
wants just like any other program. The only kink is if you are using SQL. If
you say on the stored procedure definition that SQL does read only and you
call a program that does update your procedure will abend.

Performance is dependent on how often you are calling the program. If you
are calling again and again, better to be a service program.

If you are talking about the stored procedure and the procedure is being
called again and again leave LR off as SQL stored procedures maintain state
(Remember where they were from the last time) so they don't have to be
reloaded every time.

Other than that, just like any ILE program. Build the program as procedures
and declare your variables local to the procedures and have the absolute
minimum amount of static storage (global). The more variables you have in
the global part of your program the slower it is going to run.

If you happen to be at V6R1 use the new MAIN capability to get rid of the
cycle.

On Thu, Feb 19, 2009 at 10:15 AM, Carl Galgano
<cgalgano2@xxxxxxxxxxxxxxxxx>wrote:

I have 2 systems, system A and system B.

System A will use SQL to call a stored procedure on system B.
I have registered the stored procedure on system B. The stored procedure
calls another RPGLE program, does that program also need to be a stored
procedure as well, or is there anything I need to do to have good
performance?

Thanks,

Carl J. Galgano
EDI Consulting Services, Inc.
770-422-2995
F: 678-881-9224
http://www.ediconsulting.com

530 Roselane Street
Marietta, GA 30060


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