Re: Service program signatures, and how to avoid unnecessarilyrecompiling programs that call service programs

This raised another question, to which I think I know the answer, but
confirmation is appreciated.

When deploying program / service program objects to a production system, I
never need to include *MODULE and *BNDDIR objects. Correct? (We do not
compile anything on the production system.)

While I now understand what UPDPGM and UPDSRVPGM do, I anticipate that the
*MODULE objects will remain on the system. I could also anticipate a
scenario where two modules are being modified for two different projects in
development, but only one module/project is ready to be deployed to
production. Ergo, it would make sense to use UPDSRVPGM with only the
module modified for that project for the service program object that will
be deployed.

- Dan

On Thu, Sep 14, 2017 at 3:01 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Consider this scenario...

You have a *PGM or *SRVPGM made up of 300 separate modules.

You need to change 1 of them.

Now in order to use CRTPGM or CRTSRVPGM, you either have to have kept
around the other 299 *MODULE objects, or you have to re-compile the other
299 *MODULE objects.

The UPDPGM / UPDSRVPGM allow you to update the *PGM / *SRVPGM with just the
changed module, you don't need the other 299.