Re: ILE Binding Question

I always build any production program with a module and a program
definition. Based on my standard, I would have a SB0001_M01 for example
which would bind to SB0001 program.

I always do this because many times I do some maintenance and all I need to
do is add the new module.

I use my iBuild(www.sourceforge.org/projects/iBuild) when I can to put the
instructions for how to create the object in the header. On my new job,
Aldon always has at least one module and one program object.

Simply put, it just gives me more flexibility. CRTBNDRPG is really created
for people still doing monolith programming wanting to create an RPG
program and a CL program. I would never do that. I might have a CL Module
calling functions in a RPG module and all bound together to form one
program or a service program.


On Wed, Oct 2, 2019 at 6:10 AM Brian Parkins <goodprophet.bp@xxxxxxxxx>
wrote:

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 is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com