Re: Service Program Question

Jim Minisce wrote:

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.

If you have a CMS, I'd call the vendor and ask for their recommendation.
There are a couple of scenarios I can think of off the cuff:

1) Create the service program for the very first time
2) Add a module to an existing service program
3) Add a subprocedure to an existing service program
4) Update/change an existing subprocedure


The vast majority of my maintenance falls into 3 and 4. I don't have a
CMS here, so when I need to do 1 or 2, I use a CL program to handle the
(re)creation.

Actually, Alan's pre-processor is a very nice addition to the tool box.
I've eliminated many of my CL 'make' programs but as I sometimes want
CRTsrvpgm and sometimes want UPDsrvpgm, I still use a CL program for the
rare CRT task.

Finally, a custom binding directory isn't a bad idea either. Depends a
lot on how circular your references are.
--buck