Re: independent modules vs. service program.

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Yes, a module that's going to be used in multiple places should be in a
*SRVPGM.

Then when you change the module, you only need to UPDSRVPGM and every
program using it will now be using the new version.

Charles

On Wed, Mar 9, 2016 at 4: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.