RE: Service Program Signatures and Change Management

|First, to get it out of the way, we are talking about re-binding here,
not
|re-compiling.  I presume Implementer would just be re-binding the *PGM
and
|*SRVPGM objects that are bound to your service programs.  I point this
out
|only because binding is not that expensive in terms of time, at least
|compared to compiling.

I thought service programs were bound to the calling programs at
run-time.  
 
|I can't speak for Implementer, but in TurnOver the X-Ref process is not
|exactly behind the scenes.  In TurnOver you create a promotion request,
|called a form, and TurnOver can optionally run an X-Ref process to add
the
|objects to be re-compiled or re-bound.  You can run this process
|interactively and choose which objects to include, or you can edit the
|form after the fact and remove items you do not want.  If you were only
|promoting this service program and did not want to rebind anything, you
|would just take the option to not run the X-Ref process.

I think Implementer is automatic by default, but you can use a function
key to bring up a list and modify what gets included in the compile.
Sounds like similar functionality, but different presentation.

 
Greg