Re: Change management systems

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

David

Your needs can vary - the CMS products will help manage development for 
you - including tell you when more than one person is trying to work on 
something. They will also help you know what objects are affected by any 
change. E.g., if you change a physical file, which programs, service 
programs, or logical files need to be recompiled. And when working on a 
set of objects, the correct order will be ensured.

You might not need all of that - and these are not without cost. The 
problem you present is - how to keep more than one person from working 
on something? Or, how do you handle things when that happens? If you 
want to prevent simultaneous development on the same object, you can get 
source control - not source change management. TAATOOLS has this in it - 
look at http://taatool.com/Document/L_srcctl.htm for more information. 
One thing to do with this kind of tool is, lock developers out of 
production code, so that they can't just go in and make changes. Then 
use a tool like this as the only way for developers to get at the code - 
this kind of tool will make a copy of the source member that the 
developer works on.

HTH
Vern

David FOXWELL wrote:
> Lately, had a problem with 2 developpers wanting to modify the same source at the same time.
>
> Never heard of CMS before I was on this list and I'd like to know more about these. We've always had our own installation tools, but constantly finding ways in which they need to be perfected.
>
> What might a good CMS do that our own tools can't?
>
> David FOXWELL
> Service Informatique
> Tél : 03 90 23 91 63
> david.foxwell@xxxxxxxxx<mailto:david.foxwe@xxxxxxxxx>
>
> P Pensez à l'environnement avant d'imprimer ce message
>
>