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



David,

I think that comes from the V6R1 "Memo to users". Check this:

http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic//rzaq9/rzaq9.pdf

HTH,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries



On Thu, Dec 17, 2009 at 3:14 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> wrote:
Hello all,

Just received from management this extract of an IBM memo :

If a single version of the CL program must be able to run on multiple releases that include V6R1 and a
previous release, then the source of the RPG procedure being called also requires a change. Change the
RPG source by adding the EXTPROC(*CL) keyword to the prototype (PR) and procedure interface (PI).
Any RPG programs or modules that call the changed RPG procedure must be recompiled.

Manager asks why it would be necessary to recompile all callers, as in our shop they are all bound by copy. Does the memo assume that the prototype modified is the prototype of a service program subprocedure?
Anyone know where I can find the original memo on the web?

Thanks.

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



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.