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



On 10-Jan-2014 14:53 -0800, Englander, Douglas wrote:

I have a prototype defined for a function that returns a 30 character
alpha when given two numeric parameters: the first is 3P 0 and the
second is 7P 0. This function is in a service program.

I have a statement in an ILE RPG program that uses that function.
Inadvertently, I passed two numbers but with different sizes (7P 0
and 3P 0). The program compiled, but crashes when it tries to use the
function with the parameters with the incorrect sizes.

I thought using prototypes would prevent the program from compiling
if the passed parameter definitions did not match those of the
prototype.

Has something changed? We are on V7R1.


The term /crashes/ was not very explicitly defined.?

Did the prototypes mismatch, or just the coded invocation mismatched the prototype? If the latter, then...

If the parameters are defined with CONST, then the invocation mismatch is allowed because the RPG can copy the result of the variable [as an effective expression] into a temporary variable that matches the prototyped declaration. There would be no issue in the given scenario, as long as there were no underflow or overflow.

So perhaps the error encountered was 0103 or RNX0103 [preceded by MCH1210], probably effecting the default handler to inquire with RNQ0103, per the value for the 7P00 being too large to be copied to the 3P00 temporary storage location?


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.