Re: CALL, CALLP, & CALLB

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

The cross-reference tool Pathfinder from Hawkeye works great.

>It is obvious that you should not bind a program that changes
>frequently, but occasionally changes to occur to bound modules.

I don't see where the volumne of changes to a module has any
bearing on this. A module that is used by a large number of
programs is a candidate for a Service Program. A module that
is used by a few programs is a candidate for a bound program.
Breaking a large program up into manageable components is
also a candidate for a bound program.

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