Re: Help with my first SRVPGM

When you change a service program you don't need to recompile, you cen even get a new siganture and keep the old one(s) by using an "export source". I usualy put several related modules in each service program.
__________________________________________________________________________
David FOXWELL wrote:

Thanks for the help so far.

At the moment, all our programs are bound to modules. No SRVPGMs. When a module is modified, all the programs bound to that module are recompiled automatically.

This is creating a difficult situation. Some modules are declared in many different BNDDIR, being bound to many different programs.

The big problem is when this happens : a new module is written and is used by one of those modules that is in many BNDDIRs. We have to put the new module into all those BNDDIRs. Then recompile all those programs. As the same modules become used by more and more programs, there is a kind of snowball effect. The addition of a new module means more and more recompiles.

Now in my case, I've just written a new module and created a service program for that module. I've now placed it in a BNDDIR.

Please correct me if I'm mistaken :
I now have PGM1 made up of MODULE1 and SRVPGM1. I still have to add SRVPGM1 to all the BNDDIR where MODULE1 figures.

In the future, as long as I don't change the signature of SRVPGM1, I don't need to recompile the programs.

Also, in the future, when adding a new module, if I can bind the new module to SRVPGM1 instead of PGM1, I won't need to touch the BNDDIR of all those programs where SRVPGM1 is declared.