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


  • Subject: Re: RPG/400 pgm strange behavior
  • From: Douglas Handy <dhandy1@xxxxxxxxxxxxx>
  • Date: Thu, 13 Jul 2000 00:28:29 -0400

Richard,

>Are the RPG prototypes "externally described" 

I typically use /COPY members for prototypes, so in a sense you could
call them "externally described".

>or could I create a program
>with a wrong prototype, compile it successfully, the run the program and
>cause a failure?

Granted, if you created a prototype using ExtPgm and defined the
parameters wrong then used a CALLP consistent with the prototype (but
not consistent with what the program expected), then you're back to
the same potential problem and memory corruption.

However, /COPY prototypes can be created at the same time as the
program or procedure, as part of the original work and testing.  If
they are just included in future programs needing to do the calls, it
provides an effective compile-time safeguard against parameter
mismatchs.

Doug
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

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