|
<snip> >Our change management software (MKS Implementer v5.4) won't cooperate. >I contacted them, and they sent me a nice knowledgebase article which >seems to confirm that all related objects must be checked out along with >the module being changed and promoted right along with it. (It >explicitly states that they do not nor will they ever support UPDSRVPGM >or UPDPGM). Not only this, but I must also check out and recreate the >service program itself with the module and all the programs. </snip> We use implementer. I check out only what I'm changing plus the service pgm object. Don't need to check out all of the modules that make up the service pgm or any pgms which use the service pgm. If you use signitures, then you don't need to recreate pgms which use the service pgm (unless they need the new functionality of course) even if you add a subprocedure. Phil
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.