Re: Service Program Question

Thanks Mark. That is what I gathered from the IBM documentation on UPDSRVPGM also. Just was not sure if Buck knew something that I might have missed.


----- Original Message ----
From: Mark S. Waterbury <mark.s.waterbury@xxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, March 26, 2009 10:55:26 AM
Subject: Re: Service Program Question

Hi, Jim:

UPDSRVPGM can replace existing *MODULE(s) in a *SRVPGM with a new or
updated version of the module(s).

UPDPGM can replace existing *MODULE(s) in a bound *PGM with a new or
updated version of the module(s).

You must use CRTSRVPGM or CRTPGM to add new *MODULES ...

Mark

Jim Minisce wrote:
Buck,

If I understand your response correctly, I could setup a command within the CMS that utilizes the UPDSRVPGM so when new modules need to be added, the developers will only need to add the new modules to the UPDSRVPGM command, update the binder language and let the CMS do its thing. Hopefully it did not twist things too bad.

Jim Minisce
Godiva Chocolatier, Inc.




----- Original Message ----
From: Buck <kc2hiz@xxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx
Sent: Thursday, March 26, 2009 10:18:22 AM
Subject: Re: Service Program Question

Jim Minisce wrote:

My question is this: Would it be considered best practice to create another binding directory that contains all the modules that make up the service program and reference that on the CRTSRVPGM command or am I adding another level of complexity that really does not add value? The goal would be to minimize and simplify the promotion process through the change management application.

I don't know about 'best' but I have a 'make' program I use when I need
to re-create a service program from scratch. It can be as simple as a
CL program for each service program... Normally, I don't recreate a
service program. Most of my maintenance involves UPDSRVPGM.
--buck