Clearcase: Prevent developers from modifying configspec

I work as开发者_如何学Python a repo manager for an organization with large teams of developers. Despite our communication efforts, standards definition and awarness raising, we still get developers modifying their configspecs while developing, instead of simply doing a findmerge to retrieve latest developments.

How do you usually deal with such issues? Is there a way to prevent users (coders) from modifying the configspec, once the view is created?

Avoiding config spec modification is part of the main goals behind the UCM (Unified Change Management) methodology.

But if you are stuck with "base" ClearCase (no UCM), one potential workaround is to promote common config spec included within the user config spec.
But that doesn't prevent changes.

I have also seen some admins playing around with ACL rights on the config_spec file within a view storage (in order to make it non-modifiable by any cleartool setcs). But I haven't tested that method personally.