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



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



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.