Elvis,
Just to clarify, is it not still the case that ANY program object in
QSYS.LIB can be called as a stored procedure? Technically, you should
be able to simply CALL LIB/PGM (Parm1, Parm2, Parm...) via SQL, and
expect the target to get invoked.
I understand that its easy for SQL to confuse parameter types, like
treating character literals as VARCHAR and so forth, but I use the
implied SP call methods from SQLRPGLE and not had any issues to this
point...
Just curious,
Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
Sent: Thursday, February 19, 2009 11:26 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Stored procedure that calls another program
Stored procedure can call an RPG program through IBM's QCMDEXC stored
procedure, provided it doesn't need any output arguments from the RPG
program.
Something like:
CALL QCMDEXC('CALL myRpgProgram',17);
If it requires output arguments, then you'll need to register your RPG
program as an external stored procedure.
As for performance, all of the normal performance tips you use for SQL
and/or RPG apply. There is nothing special about this scenario.
Hth, Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400 www.centerfieldtechnology.com
-----Original Message-----
Subject: Stored procedure that calls another program
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
--
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.
midrange.com
