Re: independent modules vs. service program.

I should also add that this is a simple explanation, but hopefully it helps.

I've been slowly putting some ILE 101 stuff together at FieldExit.com which
can be seen here that may offer some light on the subject.

http://www.fieldexit.com/forum/thread?groupid=Prog&forumid=RPG

It's the ILE 101 thread which shows each "topic" that you can jump to. The
entire thread can be seen here:

http://www.fieldexit.com/forum/display?threadid=154

Brad
www.bvstools.com

On Wed, Mar 9, 2016 at 3:20 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Gerald,

Think of it this way.

A module is like copying the code into the program. Only when you
recompile the program will it get the new version of the module (bind by
copy).

A service program is like a program you call. When you update the service
program, any programs calling it will "call" the new version. (bind by
reference).

Both have their advantages and disadvantages depending on your
environment.

A binding directory really doesn't do anything as far as this is
concerned. It's more like a list of modules and service programs that can
bind to your program at compile time (by copy or reference).

Brad
www.bvstools.com

On Wed, Mar 9, 2016 at 3:05 PM, Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx> wrote:

when we got going with ILE we started creating modules (single procedure),
and then put them in a binding directory...

now we have found lots of instances where we modified the modules,
sometimes significantly, but didn't re-compile or updpgm...

does putting your modules into a service program, instead of a binding
directory, help with this?

if a module changes, and it is bound up in a service program, and we
re-compile the service program, does that somehow get the programs
updated?

-or- either way, no matter how you handle modules... you will need to
re-compile or updpgm?

I do think I understand ILE modules and ILE programs, but components of
service programs (signatures, export/import, binding source) I am not so
clear on.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.