>>3. Having ClearCase do atomic operations (eg either all entities specified get
>>checked in or none of them do).
>
>ClearCase behaves the same way that CVS does in this regard: It will check
>in everything it can (as specified on its command line), stopping at the
>first error or interrupt or the successful completion of all checkins. Some
>people describe this as atomic behavior, others don't. Neither tool leaves
>the repository untouched if any file is checked in successfully.
The people who describe this behaviour as atomic
probably do not understand the definition of atomicity
used in databases - an action is either entirely performed
or not performed at all - and as used in most other
subfields of computer programming.