×
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.
If the code is not making any procedure calls, it makes little sense.
May just as well use CRTBNDRPG, (instead of CRTRPGMOD + CRTPGM). The
*MODULE serves no purpose other than take up space and complicate object
management in this situation.
However, if procedure calls ARE being used, (e.g. in a *SRVPGM or maybe
bindable API's) then it makes perfect sense. (Even then, CRTBNDRPG
enables procedure calls through *BNDDIR.)
Maybe a shop-standard that's a little too stringent? Maybe the change
control tool dictates this approach? Maybe there's more to this tale
than meets the eye?
HTH,
Brian.
On 01/10/2019 18:20, tim.feldmeier wrote:
I have not seen many companies binding modules, but, one strange thing I've seen....they make a module , and a *PGM the same name for every program. why?What is the sense of binding only one module?Sent from my Verizon, Samsung Galaxy smartphone
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.
midrange.com
