RE: Best way of using Service programs.

|Adding a new prototype to a copy book may lead to duplicate
definitions.
|So, in order to accomplish something in program A you extend a copy
|book. A few months later you modify program B and it won't compile
|(Experience? How did you guess.). Thus, it makes sense for a change
|management system to force a compile for all sources referencing the
|copy book.
|
|Joep Beckeringh
|

But program B wouldn't have had any trouble running during that time,
since the compiled object still included the original copy book
definitions.

If there are duplicate references created by the new copy book
definitions, there's no need to deal with them until you modify program
B.  If the CMS recompiled everything, you would have to make changes to
program B and god knows how many other programs just to get your program
A changes into production, when there really wasn't any need to do so.

There's no reason a CMS should recompile everything unless there is a
danger of the application failing to run as a result of the copy book
changes, IMHO.