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

Odd CALLPRC behavior when using RPG indicator with RTNVAL

*** POSTED TO MIDRANGE-L ALSO ***

Ok, this is odd.

I'm trying to call a RPG procedure in a CL program ... the RPG procedure returns an indicator (N) data type.

The normal way of handling this would be to specify a 2 character field as the RTNVAL parameter on the CALLPRC statement, and then test the first character of the field for '1'.

On this particular situation, however, I'm getting x'00F1' as the value in the 2 character CL variable that is returned.

If it makes any difference, the RPG procedure I'm calling has 2 parameters ... one 7 character field another 5 character field ... but the 2nd parameter is optional. I'm not passing the 2nd parameter in the CALLPRC.

Any suggestions?

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.