Re: Maintaining Service Program signatures

[Rory Hewitt <rory.hewitt@xxxxxxxxx>]

Kurt,

Aha!

I'm coming from the position of a software developer that makes my software
available to others - I provide a *SRVPGM object and copybooks and say
"Here is a service program with a bunch of useful procedures, defined in
this copybook. Go crazy!". But you're right that in a normal production
environment, even the copybook isn't needed.

Rory


On Wed, Feb 20, 2013 at 8:55 AM, Anderson, Kurt <KAnderson@xxxxxxxxxxxx>wrote:

> You don't need to copy source files to production in order for the service
> program to work.  I guess ask yourself - what role do those items play, and
> how are they different than modules that would make you want to also
> promote them to production?
>
> Oversimplification:
> Binder Source + possible Copybook(s) + Module(s) + (possible other things)
> = Service Program
>
> In the above, only Service Program would need to be moved to a production
> box if all of your compiling is occurring off the production box.  (The
> copybooks will be needed where other programs get compiled that are using
> the service program.)
>
> -Kurt