How does having to remember to name all modules, every time you recompile simplify things? If it is in the binding directory, and you have that listed in your H spec. It seems simpler to me. The compiler will just find it.
"Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
08/07/2008 09:47 AM
Re: Question about service programs
I suggest that a *MODULE should only ever be bound in one place, either in a single ILE bound *PGM, or in a single *SRVPGM, where it can then be "shared" and accessed by as many other ILE *PGMs as needed/desired.
So, then, you would never add any *MODULEs to any binding directories. You would only name that *MODULE on the one CRTPGM or CRTSRVPGM command, initially.
This approach greatly simplifies maintenance (when that *MODULE eventually gets changed).
Mark S. Waterbury
> Kevin Bucknum wrote:
That makes sense. Everything in our BNDDIR's are service programs which
is why I was thinking it would be unusual for them to copy.
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bruce Vining
Sent: Thursday, August 07, 2008 7:49 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Question about service programs
*MODULEs are bound by copy, *SRVPGMs are bound by reference.