Works fine for me...

I get an error when the external PR doesn't match the PI...
RNF3765 Not enough parameters specified in the procedure interface.

Either the copybook you think is being pulled in isn't or there something
else going on.

Charles

On Wed, Aug 22, 2018 at 11:37 AM Doug Englander <
denglander@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:


Does anyone know if there is a way to have the compiler enforce [DCL-PR]
prototype definitions against its associated DCL-PI definition? Earlier
versions of RPG [i.e. maybe before V7R1] the compiler would give a message
when the DCL-PR specs for a subprocedure in a module did not agree with the
corresponding DCL-PI specs. Now that the compiler rules have been relaxed,
it is now easier to have the DCL-PI and corresponding DCL-PR specs to
become out of sync. For example, I have a DCL-PI in a module that does not
accept parameters and just returns a value. I have changed the DCL-PR specs
that are in a copybook, and they are pulled in, but they have defined
parameter values being passed in. The compiler does not give any message
about this. Does anyone know if there is a way to get the compiler to
enforce the definitions like it used to do?

Thank you,

Doug

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


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-2019 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].