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



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.



From:
"Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
To:
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Date:
08/07/2008 09:47 AM
Subject:
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).

Regards,

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.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[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.




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.