Re: Level Check - service program

[Joel Cochran <jrc@xxxxxxxxxx>]

> message: 6
> date: Mon, 14 Feb 2005 08:41:29 -0700
> from: "Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxx>
> subject: Level Check - service program
> 
> I added a field to a file that uses an I/O module (service program) for
> all access to this particular file. I have re-compiled the file.
> I went to the following link to see exactly what I need to do next.
> http://archive.midrange.com/midrange-l/200210/msg00025.html
> 
> Then re-read Joel Cochran's article: "Service Programs with a Smile"
> particularly this paragraph: "With service programs, you only have to
> issue one command, UPDSRVPGM, like so: 
> UPDSRVPGM SRVPGM(MYLIB/MYSRVPGM)   MODULE(MYLIB/PROC2)
> Doing so updates not only the service program itself but also all of
> the programs that have bound PROC2."

This is assuming you recompiled the *MODULE that accesses the file...

> Like many shops, we have  dev and prod boxes. If I use the UPDSRVPGM
> command to get everything back in sync on development, does that mean I
> only have to send the re-created file to production then run the
> UPDSRVPGM there, as well? 

You'll need to move the new file and the *SRVPGM object.

> Or, could I, to be on the safe side (read: sissy) just recreate
> everything - add *prv to binder source, etc - and promote to production?

You only need to worry about *current, *prv if you are changing the
export list for the service program.  If all you are doing is updating
the existing configuration, then you shouldn't have to do anything with
the existing binder source.

Joel