Before updating a snapshot view

To ensure that your view contains the set of versions in the stream (in UCM) or selected by the config spec (in base ClearCase®), you must update it.

For example, in a UCM integration view, when other developers deliver new versions to the target stream, your snapshot integration view may become out-of-date or inconsistent with the versions in the stream.

Update the entire view periodically to make sure you have the correct version of all loaded files and directories. To save time, you can update individual files or directories. (Directories are updated recursively.) Updating only specific parts of your view may eventually cause your view to contain an inconsistent set of versions.

Time stamps

While updating the view, you can determine which type of time stamp is given to the files that are copied into your views. If your build software checks for build dependencies based on time stamps, choosing the right type of time stamp is essential.

Your versions can be given one of the following time stamps:

The time at which the file is copied into the view
The time at which the version was checked in to the view
Tip: The time stamp for a directory element in a snapshot view always reflects one of the following conditions:
- The time at which the directory is first loaded into the view
- The time at which the directory is modified by either the Update Tool or by any other file system operation
Windows tip: When you first create the view, you can set the default time stamp for files. You can change this setting when you update a view.

Resolving hijacked files

The update operation finds all files that you have hijacked. You can choose a resolution for hijacked files. By default, hijacked files are left in place.