Well, ok, but its not exactly undocumented... It did take a few minutes
of diligent searching to find it, but there is documentation...
I do tend to agree that declaring the SP is the best practice, but the
other sure is convenient for remote call with full in/out parameter
support....
Thx,
Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
Sent: Thursday, February 19, 2009 2:52 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Stored procedure that calls another program
Yes, I'm pretty sure it's still true. That said, it's an undocumented
IBM interface and I don't want to encourage folks to use it :) As you
mentioned, there are some gotchas with a simple program call, but more
importantly, what if IBM decides to pull the plug on that capability in
some future release?
Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400 www.centerfieldtechnology.com
-----Original Message-----
Subject: RE: Stored procedure that calls another program
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
--
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
