× 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: CALL, CALLP, & CALLB
  • From: "Stone, Brad V (PP)" <bvstone@xxxxxxxxxxxxx>
  • Date: Tue, 2 Mar 1999 08:17:55 -0600

Patrick,

I never bind by copy, but the documentation for each method should be
similar.

My documentation is the /COPY line in the final program.  I name all of my
modules F.xxxxx and my /COPY members P.xxxxx.  So, if in a program I see:

/COPY QBNDSRC/P.String

I know that the F.String Module is being used in that program.

One thing you must remember is that changes to modules can be made.  If you
are binding by reference and don't change the export of the subprocedures
(ie add or removed exported subprocedures) and only change the underlying
code, recreating the service program is all that is needed in most cases.

If you DO add or remove subprocedures, this will change the signature of the
service program.  But if you use Binder Language you can specify *PRV for a
list of subprocedures that you are exporting and retain the original
signature as well as creating a new signature.  (See the ILE reference
manual for some pretty good examples)  (EXPORT *ALL is a no-no in my book).

Bradley V. Stone


-----Original Message-----
From: Patrick Shrader [mailto:pshrader@foodcity.com]
Sent: Tuesday, March 02, 1999 7:44 AM
To: RPG400-L@midrange.com
Subject: Re: CALL, CALLP, & CALLB


Hello, everyone.

The only remaining question I have on the CALLB/CALLP is how folks are
documenting the modules that are bound by copy so that when a sub-program
is changed, how do you keep track of which programs to update across your
system? It is obvious that you should not bind a program that changes
frequently, but occasionally changes to occur to bound modules.

Hans, I will look into the CALLP for all my long distance calling needs.
Thanks for the great explanation. I have begun using the CALLB, but will
quickly switch to the CALLP.

Thanks to everyone for the helpful advice. The manuals are helpful for the
"hows", but this discussion group is so much better for the "whys". Manuals
are great for command syntax, but the continued support and ideas generated
from the question/answer posts on this forem is immeasurable. Too bad
manuals don't have a natural language query system built in, eh?



------------------------------------------------------------
Patrick Shrader 
pshrader@foodcity.com
Systems Analyst
K-VA-T Food Stores/Food City

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


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.