Re: [Bulk] Re: Service Program or Stand Alone

Hi, Jeff:

I would like to add the following thoughts ...

1. before creating any new "stub" *PGM that calls the corresponding new
*SRVPGM procedure, run a FNDSTRPDM to determine how many places
actually CALL the original *PGM
2. if that number is not "too large," I would just go ahead and change
the CALLs to just invoke the new procedure directly, and thus
dispense with having to create one more "stub" *PGM that needs to be
maintained (and eventually eliminated)
3. how many is "too many" may vary, depending on project workload and
how much time you have available for such "maintenance" work
4. I would only want to create a "stub" *PGM to call the procedure in
the *SRVPGM for cases where that original program is called in a
large number of programs -- too many to conveniently change them all
"in one go" ...
5. and then, in these cases, I would subsequently start working towards
reducing the number of programs that call this "stub" program,
replacing with the new procedure call, gradually, as time permits.
The long-term goal should be to eventually eliminate all such "stub"
programs

I hope this "makes sense" ...

Mark S. Waterbury

> On 7/21/2014 12:17 PM, Jeff Young wrote:

To everyone that responded, thanks.
As I indicated, this is something I am researching for my own benefit.
I had originally thought along the lines of changing the "OLDPGM" to
"NEWSRVPGM" and creating a new "OLDPGM" with the original parms and logic
to call procedures in the service program.

It is nice to know that most of the community appears to confirm that *if*
something like this is done (change OLDPGM to NEWSRVPGM) that the above
would be the best method to use.

I will not be changing anything for the sake of change, but if I do need to
add significant new code and/or function, I will keep this in mind.


Jeff Young
Sr. Programmer Analyst