A glossary of terms for IBM Rational ClearCase use and administration.
This glossary includes terms and definitions for IBM Rational ClearCase.
The following cross-references are used in this glossary:
-
See refers the reader from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form.
-
See also refers the reader to a related or contrasting term.
To view glossaries for other IBM products, go to the IBM Terminology Web site
An instance of a label type object, which provides a user-defined name for a version. See also object.
A type object that defines a version label for use within a versioned object base (VOB).
To copy a version of an element to a snapshot view or Web view.
A statement in the config spec that specifies an element or subtree to load into a snapshot view. Config specs can have more than one load rule.
The starting branch of a version tree of an element. The default name for this branch is main.
In ClearCase MultiSite, the replica at which a mastered object can be modified or instances of the object can be created.
The ability to modify an object or to create instances of an object in a replica.
Data that describes the characteristics of data; descriptive data.
A file system that supports dynamic views.
See Multiversion file system (MVFS)
A type of license locked to a specific node, so that the product can be used only at that node. The node-locked license is installed on the workstation for which it was created.
An item stored in a versioned object base (VOB). An object can be identified by an object-selector string, which includes a prefix that indicates the kind of object, the object's name, and a suffix that indicates the VOB in which the object resides. Examples: lbtype:REL1@/vobs/vega on UNIX and lbtype:REL1@\vega on Windows. See also label.
A networkwide database that records the storage locations of all versioned object base (VOB) storage directories and all view storage directories.
An element that is no longer cataloged in any version of any directory. Such elements are moved to the lost+found directory of the versioned object base (VOB).
| 
