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


  1.  Home
  2. RPG400-L
  3. November 2007

RE: Wrap an RPG Procedure with an SQL External Procedure

We'd have to ask someone more knowledgeable about the compiler to see if the
following idea is safe, but you MIGHT be able to take the address of the
return value and compare it to NULL. If it's null, don't set the return
value.

It's not perfect, but if it's safe, it beats the double maintenance of a
wrapper stub.

Joe


From: RNewton@xxxxxxxxxxxx

Joe: No I do not NEED the value since its merely a success indicator. I
was
willing to do without it when calling from the SQL procedure if it wasn't
to supported, but I didn't imagine it would cause the program to bomb out.
Now having to have a stub proc that removes the return values of
procedures
is going to be a pain just to make them callable from an external proc.


As an Amazon Associate we earn from qualifying purchases.

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