|
midrange-l-bounces@xxxxxxxxxxxx wrote on 02/16/2006 11:41:20 AM: > Premise1: The value of using binder source is that it allows me to NOT > compile calling programs which don't use the latest procedure. It gives you that ability, true, but you still have to do it right. The mere presence of binder source alone does not provide this. > Premise2: Implementer (and presumably other change management products) > recompile all related objects behind the scenes anyway. 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 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. > Conclusion: Therefore, if using change management, there is no value in > using binder source. I do not agree. There is a lot of value in binder source. For one thing, you may want certain procedures to be private and others to be public. The fact that your change management solution is being safe and rebuilding everything for you should not stop you from using binder source. Mark _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.