A ClearCase® Synchronized Stream is
based on a configuration specified by a UCM stream or a Rational® ClearCase branch
type and label type. If Rational ClearCase users
modify any of this metadata or make any changes to the dynamic view
that the New ClearCase Synchronized Stream wizard
creates, synchronization can be disrupted or produce incorrect results.
Observe the following guidelines when working in
Rational ClearCase with
resources that are part of a synchronized stream:
- The New ClearCase Synchronized Stream wizard
creates a dynamic view that has a distinctive view tag (the prefix DO_NOT_USE and
a UUID suffix). This view should be considered off limits by Rational ClearCase users.
- Do not use the main branch and LATEST label
when creating a synchronized stream (see Step 9 of Creating a ClearCase Synchronized Stream ). The label used by a synchronized stream
must be locked for all users; if the label is not locked, the synchronized
stream will not be created. In addition, the branch type is locked
while synchronization is underway, and it is not advisable to have
the main branch locked in this way. For more
information, see Configuration specification details for base ClearCase.
- Do not unlock the label type used by a synchronized stream.
- Do not use cleartool rmver, cleartool
rmelem, or any UI equivalent of these commands to remove
a version or element that is currently synchronized. If you remove
the version that was most recently synchronized (imported to a synchronized
stream), its predecessor version is selected by the Rational ClearCase dynamic
view, but this change is not imported into the synchronized stream.
If you remove an element that is synchronized, the element is removed
by the Rational ClearCase dynamic
view, but this change is not imported into the synchronized stream;
if you have removed an element from Rational ClearCase,
you must also remove the element from Rational Team Concert source
control to
avoid synchronization errors.
- When synchronization fails, files in the synchronization view
might remain checked out. While this does not disrupt future synchronizations,
it does prevent other Rational ClearCase users
from checking out the files on the synchronization view's stream or
branch. These files are checked in by the next successful synchronization
process.
- The executable property of a file stored in Rational ClearCase is
preserved during synchronization regardless of any change that is
made to that property by Rational Team Concert source
control.
- Rational ClearCase users
can write triggers that perform ClearCase actions during synchronization.
For information about available triggers and behaviors,
see Using ClearCase triggers during synchronization.
- It is a good practice to avoid creating more than one synchronized
stream defined by the same UCM stream or by the same branch type and
label type. Such a configuration increases the chances of synchronization
failures due to the stream (or branch) being locked.