|
Alfred, Good point about not needing a wrapper for stored procedures. I've called SQL stored procedures from .ASP with great success. I'd rather do it with stored procedures anyway. When looking at documentation about the SQL stored procedures I briefly looked at the program stored procedure route. I'll check it out in more detail. Thanks, Dave
Alfredo Delgado <adelgado@xxxxxxxxxxxxxxxxx> 11/15/2006 07:29 >>>
I went through a similar process when working to call RPG programs from PHP on an i5 running V5R3. I shared my learning process at http://i5php.net/index.php?name=Forums&file=viewtopic&t=44 You may not need a wrapper for the external stored procedure like I did. Thanks, Alfred Dave Odom wrote:
Walden, Thanks for the idea about a stored proc wrapper. Humm, it will take some thinking about how to do that and not only invoke the command
which
would be a parm to the stored procedure but also send any parms for
the
command as additional parms for the call to the stored procedure... if
I
understand correctly. Dave"Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx> 11/14/2006 16:41Dave, Define a stored proc wrapper around QCMDEXEC and have fun. I also
have
a vague recollection that you could call the "stored proc" using two "{{" and not need the stored proc wrapper, it would directly call the program object, but it's been a while since I used OLEDB. As for long-term web, in my view of the world there are only two possible answers, ASP.NET and JSP/Java. -Walden
As an Amazon Associate we earn from qualifying purchases.
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.