|
In some of our initial 'playing around' with WDSC 6 and RSE, we're noticing that when copying source from/to one of our production source libraries, that the existing validity checking doesn't seem to be triggered. It's almost like it's not really touch the actual 'cpysrcf' command or is just ignoring the validy check portion of the command. We're using some very basic change management that just enforces the checking out/in of production source and helps with the auditing of these functions. (The validity checker calls a program when source is copied from/to certain libraries and the programmer must log info pertaining to project, etc.). Is anyone doing something similar in the WDSC environment or is it necessary to get into more of a full blown product that helps with change management. We're hoping for a simple method like we're using now... Any comments will be appreciated, thanks! _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________
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.
midrange.com
