Glossary for ClearCase, MultiSite, and Attache


A B C D E F G H I J K L M N O P Q R S T U V W X Y Z


A

abe

(UNIX platforms only) See audited build executor.

absolute VOB pathname

(Windows platforms only) A pathname to a VOB object that begins with the VOB-tag. (That is, the pathname does not specify a network drive or view.) For example, \myvob\src\test.c, where the VOB-tag is \myvob.

access mode

A three-digit octal number —— 751, 644, or 777, for example. From left to right, the three digits designate file access permissions for three classes of user: owner, group, and others. The three bits of each of the three octal digits further define file access as read, write, or execute with respect to the three classes of users. The command cleartool protect –chmod controls an element's access mode.

activate

Make a dynamic view or VOB accessible on a particular host. See the mount reference page. On UNIX platforms, see also the setview reference page.

active

A VOB becomes active on a host when it is mounted with the cleartool mount command.

A dynamic view becomes active on a host when it is started with either a cleartool setview or startview command on UNIX platform; or a Connect Network Drive, net use, or startview command on Windows platforms. These commands establish a connection between the host's MVFS file system and the dynamic view's view_server process.

activity

A ClearCase UCM object that tracks the work required to complete a development task. An activity includes a text headline, which describes the task, and a change set, which identifies all versions that you create or modify while working on the activity. When you work on a version, you must associate that version with an activity. If your project is configured to use the UCM-ClearQuest integration, a corresponding ClearQuest record stores additional activity information, such as the state and owner of the activity.

administrative VOB

A VOB containing global type objects, which are copied to client VOBs on an as-needed basis when users wish to create instances of the type objects in the client VOBs. See auto-make-type, global type, local copy.

Administrator

(Windows platforms only) The Administrator user, or any member of the Administrators group. Some operations, such as stopping and starting ClearCase, require membership in the Administrators group only on the client workstation. Other operations, such as modifying domain-wide group assignments, require membership in the Administrators group on the domain controller for the Windows NT Server domain.

albd_server

Atria Location Broker Daemon. This ClearCase master server runs on each ClearCase host; it starts up, and dispatches messages to, the various ClearCase server programs (for example, view_server, vob_server, db_server, vobrpc_server, and so on) as necessary. See the albd_server reference page.

all-element trigger type

A trigger type that is automatically associated with all elements in a VOB.

ancestor

In an element's version tree, a version that is on the line of descent of another version. In other words, a version that has contributed to the contents of another version is considered an ancestor to the latter version.

annotation box

(UNIX platforms only) Part of the xcleardiff display, showing how lines of one file differ from lines of other files, with which it is being compared or merged.

argument

A word or quoted set of words processed by a command.

Atria Location Broker

See albd_server.

Attache client

(Attache) The program through which you enter all commands, using the command-line and graphical interfaces. This program, attache.exe, is located in the bin subdirectory within the Attache installation area on your PC (attache-home-dir\bin\attache.exe).

Attache window

(Attache) The standard Microsoft Windows window in which the Attache client program executes.

attached list

See trigger inheritance.

attribute

A meta-data annotation attached to an object, in the form of a name/value pair. Names of attributes are specified by user-defined attribute types; values of these attributes can be set by users. Example: a project administrator creates an attribute type whose name is QAed. A user then attaches the attribute QAed with the value "Yes" to versions of several file elements.

attribute type

An object that defines an attribute name for use within a VOB. It constrains the attribute values that can be paired with the attribute name (for example, an integer in the range 1󈝶).

attribute value

See attribute type.

audit, audited shell

See build audit.

audited build executor

(UNIX platforms only) A process invoked through the UNIX remote-shell facility, in order to execute one or more build scripts on behalf of a remote clearmake.

auto-make-branch

ClearCase's facility, specified in a config spec rule, for automatically creating one or more branches when a checkout is performed.

auto-make-type

ClearCase's facility for automatically copying type objects from an administrative VOB to a client VOB, when a user attempts to make an instance of the type object in the client VOB. See global type, local copy.

automounted

A file system on a remote host that has been automatically mounted on the local host.

B

backup registry server host

See registry server host.

base contributor

In ClearCase comparison and merge tools, the contributor against which all other contributors are compared when reporting differences. For example, if you are comparing four contributors, a through d, and contributor a is the base contributor, ClearCase compares:

A matched set of source versions, representing a certain milestone in a project. Typically, a baselevel is recorded by attaching a version label to each version in the set.

baselevel-plus-changes

A software development methodology, in which the current status is determined in relation to a recent baselevel.

baseline

A ClearCase UCM object that typically represents a stable configuration for one or more components. A baseline identifies activities and one version of every element visible in one or more components. You can create a development stream or rebase an existing development stream from a baseline.

bidirectional

See hyperlink.

bitmap files

Files that store bitmaps for the icons displayed by ClearCase GUI programs.

BOS file

A file containing rules that specify settings of make macros, which affect the way in which a target rebuild proceeds.

branch

An object that specifies a linear sequence of versions of an element. The entire set of versions of an element is called a version tree; it always has a single main branch, and may also have subbranches. Each branch is an instance of a branch type object.

branch name

See branch type.

branch pathname

A sequence of branch names, starting with main (the name of an element's starting branch). Examples: /main/motif on UNIX platforms, or \main\maintenance\bug459 on Windows platforms.

branch type

An object that defines a branch name for use within a VOB.

Broadcast Message Server

(UNIX platforms only) A Hewlett-Packard SoftBench program that passes messages among SoftBench applications.

browser

A class of ClearCase graphical tools. The various kinds of browser —— type object, vtree, properties, history, log, VOB admin, view-tag, VOB-tag, pool, list, and so on —— share a common model: they display some kind of ClearCase data, and they include toolbar and menu commands for operating on that data. In addition, as you perform your ClearCase work, browsers prompt you automatically for any data required to complete particular ClearCase operations.

Browser window

(Attache) When the Attache window is divided into upper and lower partitions, the upper partition is the browser window. The File Browser is displayed in the browser window.

build

The process during which a ClearCase build program (clearmake, clearaudit, or omake) produces one or more derived objects. (NOTE: omake is supported only on Windows platforms.) This may involve actual translation of source files and construction of binary files by compilers, linkers, text formatters, and so on. A system build consists of a combination of actual target rebuilds and build avoidance. See also express build.

build audit

The process of recording which files and directories (and which versions of them) are read or written by the operating system during the execution of one or more programs. A client host's MVFS file system performs an audit during execution of a ClearCase build program: clearmake, omake, clearaudit, or abe. (NOTE: omake is supported only on Windows platforms, and abe is supported only on UNIX platforms.) When the build audit ends, the build program creates one or more configuration records (CRs). An audited shell is a UNIX shell process created by clearaudit in which all file system accesses are audited, and are recorded in a configuration record when the shell exits.

build avoidance

The ability of a ClearCase build program to fulfill a build request by using an existing derived object, instead of creating a new derived object by executing a build script. The build program can reuse a derived object currently in the view or wink in a derived object that exists in another view. The process by which the build program decides how to produce a derived object is called configuration lookup.

build configuration

The set of source versions in a view, the current build script that would be executed, and the current build options. See also configuration lookup.

build dependency

See dependency.

build hosts file

(UNIX platforms only) A file that lists hosts to be used in a parallel build.

build options specification file

See BOS file.

build reference time

The time at which a build session (invocation of a ClearCase build program) begins. Versions created after this time are kept out of the build.

build script

The set of shell commands that a ClearCase build program or a standard make program reads from a makefile when building a particular target.

build server control file

(UNIX platforms only) A file on a build host that controls its availability as a build server.

build server host

(UNIX platforms only) A host used to execute build scripts during a clearmake parallel build.

build session

A top-level invocation of a ClearCase build program; during the session, recursive invocations of clearmake, omake, or clearaudit may start subsessions. (NOTE: omake is supported only on Windows platforms.)

build target

A word, typically the name of an object module or program, that can be used as an argument in a clearmake or omake command. (NOTE: omake is supported only on Windows platforms.) The target must appear in a makefile, where it is associated with one or more build scripts.

built-in rules

Build rules defined in a system-supplied or ClearCase-supplied file, which supplement the explicit build rules in a user's makefiles.

bump

The taking away of a ClearCase license from a lower-priority user by a higher-priority user.

C

candidate

A derived object that is being considered for winkin or reuse during configuration lookup.

cascading menu

A menu that includes one or more sub-menus.

cataloged

Names of elements and VOB symbolic links that appear in a version of a directory element are said to be cataloged in the directory version. A derived object is said to be cataloged (and, hence, available for reuse and winkin) in a particular VOB.

change set

A list of related versions associated with a UCM activity. ClearCase records the versions that you create while you work on an activity. An activity uses a change set to record the versions of files that are delivered, integrated, and released together.

checked-out version

A placeholder object in a VOB database, created by the checkout command. This object corresponds to the view-private object (file or directory) that you work with after checking out the element.

checking (a VOB)

Finding and fixing inconsistencies between a VOB database and the VOBs storage pools. See VOB database snapshot and the checkvob reference page.

checkout/checkin

The two-part process that extends a branch of an element's version tree with a new version. The first part of the process, checkout, expresses your intent to create a new version at the current end of a particular branch. (This is sometimes called checking out a branch.) The second part, checkin, completes the process by creating the new version.

For file elements, the checkout process creates an editable version of the file in the view (and, with Attache, in your workspace), with the same contents as the version at the end of the branch. Typically, a user edits this file, then checks it back in.

For directory elements, the checkout process allows file elements, (sub)directory elements, and VOB symbolic links to be created, renamed, moved, and deleted.

Performing a checkout of a branch does not necessarily guarantee you the right to perform a subsequent checkin. Many users can checkout the same branch, as long as they are working in different views. At most one of these can be a reserved checkout, which guarantees the user's right to checkin a new version. An unreserved checkout affords no such guarantee. If several users have unreserved checkouts on the same branch in different views, the first user to perform a checkin wins —— another user must perform a merge if he wishes to save his or her checked-out version.

checkout record

The event record created by the checkout command.

clearcase group

(Windows platforms only) A special group, usually created in the Windows NT domain when ClearCase is installed. Only ClearCase administrative accounts and the login account for the ClearCase ALBD Service should be members of this group.

ClearCase registry

A set of files on the registry server host that map logical VOB and view names (VOB-tags and view-tags) to physical storage locations (VOB storage directories and view storage directories). See registry_ccase, backup registry servers.

cleartext file

An ASCII text file that contains a whole copy of some version of an element, having been extracted from a data container that is in compressed format or delta format. A ClearCase type manager creates a cleartext container the first time it accesses the version. Subsequent reads of that version access the cleartext file, for better performance.

cleartext pool

A VOB storage pool, used for data containers that contain cleartext.

CLI

Command-line interface.

client

The programs invoked by users: cleartool, clearmake, cleardiff, and other programs located in the ClearCase bin directory. See Attache client.

clock skew

The discrepancies among the system clocks of several hosts.

command option

In the command-line interface (CLI), a word beginning with a hyphen (–) that affects the meaning of a command.

command prompt

(Attache) The character string (the name of the current working directory, followed by ">") that Attache displays when it is ready to execute a command.

Command window

(Attache) The part of the Attache window where you type commands, and where command output is displayed. When the Attache window is divided into upper and lower partitions, the lower partition is the command window.

command-line interface

The input method in which you type a command at a command prompt.

comment default

The action taken by certain CLI commands when you do not specify a comment-related option.

common ancestor

In an element's version tree, a version that is on the line of descent of two (or more) versions on different branches.

compatibility mode

A clearmake or omake execution mode, in which it emulates another make variant. (NOTE: omake is supported only on Windows platforms.)

component

A ClearCase object that you use to group a set of related directory and file elements within a UCM project. Typically, you develop, integrate, and release the elements that make up a component together. A project must contain at least one component, and it can contain multiple components. Projects can share components.

compressed_file

The ClearCase element type that uses data compression on individual versions.

compressed_text_file

The ClearCase element type that uses both delta management and data compression on individual versions.

config spec

A set of configuration rules specifying which versions of VOB elements a view selects. The config spec for a snapshot view also specifies which elements to load into the view. See pattern, scope, version-selector, version-selection rule, load rule, and the config_spec reference page.

configuration (of a derived object)

The bill-of-materials information recorded in a derived object's configuration record, including versions of source files used to build the object, build script, and build options.

configuration (of a view)

The set of versions (one version of each element) selected by a view's config spec.

configuration lookup

The process by which a ClearCase build program determines whether to perform a target rebuild of a derived object (execute a build script) or reuse an existing instance of the derived object. This involves comparing the configuration records of existing derived objects with the build configuration of the current view.

configuration management

The discipline of tracking the individual objects and collections of objects (and the versions thereof) that are used to build systems.

configuration record (CR)

A listing produced by a target rebuild, logically associated with each derived object created during the rebuild. A configuration record is a bill of materials for a derived object, indicating exactly which file system objects (and which specific versions of those objects) were used by the rebuild as input data or as executable programs, and which files were created as output. It also contains other aspects of the build configuration.

Each target rebuild typically involves the execution of a single build script, and creates a single configuration record. If a target has subtargets that must be rebuilt, also, a separate configuration record is created for each subtarget rebuild.

configuration record hierarchy

A tree structure of configuration records, which mirrors the hierarchical structure of targets in the makefile.

configuration rule

See config spec.

configuration specification.

See config spec.

container

See data container.

context

See view context.

contributor

A file, directory, or version considered for a comparison or merge. Typically, contributors are multiple versions of the same ClearCase file or directory element.

conversion specification

A code (for example, %En) that is part of the format string specification following a –fmt option. See the fmt_ccase reference page.

CR

See configuration record.

cross-VOB hyperlink

A hyperlink that connects two objects in different VOBs. The hyperlink always appears in a describe listing of the from object. It also appears in a listing of the to object, unless it was created as a unidirectional hyperlink (mkhlink –unidir). See same-VOB hyperlink.

current working directory

(ClearCase) The context in which relative pathnames are resolved by the operating system. This can be a location in ClearCase's extended namespace.

(Attache) The directory within your workspace (and the corresponding directory within some VOB) with respect to which the command-line interface interprets simple file names and relative pathnames of ClearCase data.

current workspace

(Attache) The workspace that is active in the Attache window. The workspace name appears in the title bar.

D

data container

A file (or directory) that contains the data produced by a build script. A data container and a configuration record are the essential constituents of a derived object. Also, a file in a source pool or cleartext pool, containing the data for one or more versions of a file element.

default config spec

See config spec.

degenerate derived object

A derived object that cannot be successfully processed, because its data container and/or associated configuration record are not available.

deliver

A ClearCase operation that allows developers to share their work with the rest of the project team by merging work from their own development streams to the project's integration stream. If required, the deliver operation invokes the Merge Manager to merge versions.

delta

The incremental difference (or set of differences) between two versions of a file element. Certain type managers (for example, text_file_delta), store all versions of an element in a single data container, as a series of deltas.

dependency

In a makefile, a word listed after the colon (:) on the same line as a target. A source dependency of a target is a file whose version-ID is taken into account in a configuration lookup of the target. A build dependency is a derived object that must be built before the target is built.

derived object (DO)

An MVFS file (pathname within a VOB) produced by a clearmake or omake build or a clearaudit session. (NOTE: omake is supported only on Windows platforms.) Each derived object is associated with the configuration record that is created by the ClearCase build program to document the build. A shareable DO can be winked in by other views. A nonshareable DO cannot be winked in by other views unless you explicitly make it available.

derived object scrubbing

The removal of data containers from view storage, of data containers from derived object pools in a VOB, and of derived objects themselves from a VOB database.

derived object sharing

Multiple views simultaneously using the same derived object. See winkin.

derived object storage pool

A storage pool for the data containers of a VOB's derived objects. Only those derived objects that have been winked in are stored in these pools. Data containers of unshared and nonshareable derived objects are stored in view-private storage.

The first time a derived object is winked in, the promote_server program copies the data from the original view, creating a data container in a derived object storage pool.

derived object version

See DO version.

detected dependency

A source dependency that is automatically detected by clearmake or omake, rather than being explicitly coded in a makefile. (NOTE: omake is supported only on Windows platforms.)

development stream

A ClearCase UCM object that determines which versions of elements appear in your development view, and maintains a list of your activities. The purpose of the development stream is to let you work on a set of activities and corresponding versions in isolation from the rest of the project team. The development stream configures your development view to select the versions associated with the foundation baselines plus any activities and versions that you create after joining the project or rebasing your development stream.

development view

A view associated with a UCM development stream.

Use a development view to work on a set of activities and corresponding versions isolated from the rest of the project team. You then can share changes made in a development view with the rest of the project team by delivering activities to the project's integration stream.

A development view can be either a dynamic view or a snapshot view.

direct mode

(UNIX platforms only) A state of the hyperlink tree browser in which the browser displays only the hyperlinks that are directly connected to the displayed objects. Compare this to the hyperlink tree browser's inheritance m

difference

(When comparing files, directories, or versions, a section where the content of the base contributor is unlike that of one or more contributors.

directory element

An element whose versions are like directories —— they catalog the names of file elements, other directory elements, and VOB symbolic links.

directory version

A version of a directory element.

distributed build

(UNIX platforms only) A parallel build in which execution takes place on multiple hosts in a local area network.

DO

See derived object.

DO-ID

A unique identifier for a derived object, including a time stamp and a numeric suffix to guarantee uniqueness. Example: the substring beginning with @@ in hello.o@@12-May.19:15.232.

domain

(Windows platforms only) See Windows NT Server domain.

DO version

A derived object that has been checked in as a version of an element.

downloading files

(Attache) Copying files to your current workspace from its associated view.

drive-relative pathname

(Windows platforms only) A full pathname that does not include a drive specification (for example, \project\src).

dynamic view

A view that is always current with the VOB (as specified by the config spec). Dynamic views use the MVFS to create and maintain a directory tree that contains versions of VOB elements and view-private files. Dynamic views are not supported on all ClearCase platforms.

dynamic-views drive

(Windows platforms only) A drive, M: by default, that provides access to the VOBs and dynamic views active on the current ClearCase host.

dynamic-views root directory

The directory maintained by the MVFS file system in which view-tag entries appear, allowing views to be accessed. On Windows, this directory is \\view or M:\; on UNIX, it is /view. See also viewroot directory.

E

eclipsed

Invisible, because another object with the same name is currently selected by the current view.

element

An object that encompasses a set of versions, organized into a version tree.

element trigger type

See trigger type.

element type

A class of versioned file or directory objects. ClearCase supports predefined element types (for example, file, text_file). Users can define additional types (for example, c_source_file) that are refinements of the predefined types. When an element is created, it is assigned one of the currently-defined element types in its VOB. Each user-defined element type is implemented as a separate VOB object.

ellipsis

The wildcard symbol "...". In a version-selector, it indicates zero or more directory levels.

emulation mode (omake)

(Windows platforms only) omake's execution mode in which its behavior resembles that of other build utilities, such as PolyMake. See also compatibility mode.

enabled

An enabled button or menu command is active and can be activated with a mouse click. Opposite: insensitive.

encapsulator

A program that packages the functionality of an external software system.

epoch number

(MultiSite) An integer associated with a ClearCase operation performed at a replica. Each replica records the epoch numbers of operations it has performed and of operations it has received from other replicas.

epoch number matrix

(MultiSite) A complete set of epoch numbers, indicating the local VOB replica's estimate of the current state of all replicas in a VOB family. A replica's own epoch row within the matrix reflects its actual state.

event

A ClearCase operation that is recorded by an event record in a VOB's event history.

event-ID

A numeric identifier, which can be used to specify a particular event record in the chevent subcommand.

event record

An item in a VOB database that contains information about an operation that modified that VOB.

exception list

The set of users to whom a lock or trigger will not apply.

expiration period

(MultiSite) The interval after which the store-and-forward facility stops trying to process a shipping order.

export view

(UNIX platforms only) A view used to export a VOB to a non-ClearCase host.

express build

A build during which the ClearCase build program creates derived objects, but does not write information about them into the VOB. This speeds up the build and means that the DOs cannot be winked in by other views.

extended namespace

ClearCase's extension of the standard Windows or UNIX pathname hierarchy. Each host has a view-extended namespace, allowing a pathname to access VOB data using any view that is active on that host. Each VOB has a VOB-extended namespace, allowing a pathname to access any version of any element, independently of (and overriding) version-selection by views.Derived objects also have extended pathnames, which include DO-IDs. See namespace.

extended naming symbol

A symbol (by default, @@) appended to an element name or derived object name, signaling the MVFS file system to bypass automatic version-selection by a view.

extended pathname

A VOB-extended pathname specifies a particular location in an element's version tree, or a particular derived object cataloged in that VOB.

If the pathname specifies a particular version, is termed a version-extended pathname. Examples:

Windows:

foo.c@@\main\17
\myproduct\bin\xtract@@\REL_1
\myproduct@@\main\bug403\5

UNIX:

foo.c@@/main/17
/usr/myproduct/bin/xtract@@/RELEASE_1
/usr/myproduct@@/main/bug403/5

A view-extended pathname accesses a file system object in the context of a specified view. For an element, such a pathname specifies the version of the element selected by that view's config spec; for a view-private file or derived object, such a pathname accesses an object in the view's private storage area. Examples:

Windows (assuming that M: is the dynamic views root directory):

m:\akp\proj_1\foo.c
m:\archive\proj_1\foo
m:\bugfix\proj_1\to_do.list

UNIX:

/view/akp/usr/project/foo.c
/view/archive/usr/project/foo
/view/bugfix/usr/project/to_do.list

F

FAT file

(Windows platforms only) A file located in a file system of type FAT (file allocation table).

feature level

An integer that Rational increments at each ClearCase release that introduces features that affect compatibility across VOB replicas running earlier ClearCase releases.

field-width specifier

An optional part of a conversion specification, which helps in creating reports with fixed-width columns. See the fmt_ccase reference page.

file browser

(Attache) A directory tree browser that you can display in the upper partition of the Attache window. The left side displays an icon for each of your workspaces, and initially, the View and Workspace Contents for the current workspace.

file contents

See file system data.

file element

See element.

file system configuration

The set of versions accessible through a view.

file system data

The bytes stored in a version of a file element. A file's contents are distinguished from its meta-data (attributes, hyperlinks, and so on).

file type

The identifier returned by ClearCase file typing subsystem, through a lookup in ClearCase-supplied and/or user-supplied magic files. File types are used to select an element type for a new element.

file typing rule

See magic file, file type.

filename pattern

See pattern.

fire a trigger

The process by which ClearCase verifies that the conditions defined in a trigger are satisfied, and causes the associated trigger action(s) to be performed.

flag file

A file whose existence/non-existence controls conditional processing in a build script.

flat

A non-hierarchical listing, combining information from a collection of configuration records.

flat file

A file that contains text characters only.

format string

In several cleartool subcommands, a character string argument to the –fmt option. This string can combine literal text with conversion specifications, to specify how event record data is to be formatted in the command's output. See the fmt_ccase reference page.

foundation baseline

A property of a stream. Foundation baselines specify the versions and activities that appear in your view. As part of a rebase operation, foundation baselines of the target stream are replaced with the set of recommended baselines from the source stream.

from-object

See hyperlink.

from text

A string-valued attribute attached to a hyperlink object, conceptually at its from end.

full baseline

A baseline created by recording all versions below the component's root directory. Generally, full baselines take longer to create than incremental baselines; however, ClearCase can look up the contents of a full baseline faster than it can look up the contents of an incremental baseline.

full local pathname

(Windows platforms only) A full pathname that includes a drive specification (for example, D:\project\src).

full pathname

A standard operating system pathname beginning with a "/" on UNIX or a drive letter followed by "\" on Windows (for example, C:\ or Z:\).

full remote pathname

A full pathname indicating a location in some ClearCase VOB.

G

g-file

(UNIX platforms only) A file produced by the SCCS get command.

generated comment

A comment string for an event record that is created automatically by cleartool —— for example, the checkin comment for a new directory version.

get

(Attache) The command that downloads one or more files to your workspace.

global pathname

A network-wide pathname for a ClearCase view storage directory or VOB storage directory. Some global pathnames are valid only within a particular network region.

global type object

A type object, created with mkxxtype –global and located in an administrative VOB. Such objects are used by the auto-make-type facility to create local copies in other VOBs (termed client VOBs). See also: administrative VOB.

Gnu make

A make variant distributed by the Free Software Foundation.

goal target

The target(s) explicitly named on a clearmake or omake command line. (NOTE: omake is supported only on Windows platforms.)

group list

The list of groups to which your user account belongs (in addition to the Windows primary group name or UNIX principal group ID defined for your user account). VOBs, views, and file system objects also have group assignments, and the interaction of these assignments with your group memberships helps determine the outcome of VOB and view data storage access attempts.

H

hard link

(UNIX platforms only) An additional name for a file system object, cataloged in the same directory or in a different directory. UNIX hard links are cataloged in standard UNIX directories; VOB hard links are cataloged in versions of directory elements.

helper host

(Attache) See workspace helper host.

hijacked file

A version in a snapshot view that is modified but not checked out. By default, a non-checked out version in a snapshot view is given the file attribute of read-only. If you change this attribute and modify the file, you have hijacked the file by taking it out of direct ClearCase control.

history

Meta-data in a VOB, consisting of event records involving that VOB's objects. The history of a file element includes the creation event of the element itself, the creation event of each version of the file, the creation event of each branch, the assignment of attributes to the element and/or its versions, the attaching of hyperlinks to the element and/or its versions, and so on.

history browser

A graphical tool that enables you to examine ClearCase event records for one or more objects.

history mode

The state of a process whose current working directory is in the ClearCase VOB-extended namespace (for example, hello.c@@/main on UNIX or hello.c@@\main on Windows).

host-local pathname

For a view storage directory or VOB storage directory, a pathname that specifies the directory's location in its own host's file system. This pathname need not be valid on any other host. Contrast this with the directory's global pathname.

hybrid command

(Attache) A command that affects both your workspace (on your PC) and ClearCase storage (view and/or VOB located on one or more remote hosts).

hyperlink

A logical pointer between two objects. A hyperlink is implemented as a VOB object; it derives its name by referencing another VOB object, a hyperlink type. A hyperlink can have a from-string and/or to-string, which are implemented as string-valued attributes on the hyperlink object.

A bidirectional hyperlink connects two objects in the same VOB or in different VOBs, and can be navigated in either direction: from-object to to-object or to-object to from-object. A unidirectional hyperlink connects two objects in different VOBs, and can be navigated only in the from-object to to-object direction.

hyperlink tree browser

(UNIX platforms only) A graphical tool that enables you to traverse hyperlinks connecting objects.

hyperlink-ID

A system-generated identifier that, in conjunction with the name of the hyperlink type, uniquely identifies a hyperlink object. Examples: @391@/usr/hw on UNIX or @391@\hw_vob on Windows.

hyperlink inheritance

The ClearCase feature by which hyperlinks attached to a version can be detected in a search for hyperlinks on a successor version.

hyperlink selector

A string that specifies a particular hyperlink. It consists of the name of a hyperlink type object, followed by a (possibly abbreviated) hyperlink-ID. Examples: DesignFor@391@/usr/hw on UNIX and DesignFor@391@\hw_vob on Windows.

hyperlink type

An object that defines a hyperlink name for use within a VOB.

I

icon

A small picture used by graphical tools.

icon file

A file containing rules that map ClearCase file types to names of bitmap files.

incremental baseline

A baseline created by recording the last full baseline and those versions that have changed since the last full baseline was created. Generally, incremental baselines are faster to create than full baselines; however, ClearCase can look up the contents of a full baseline faster than it can look up the contents of an incremental baseline.

inclusion list

A list of type objects, defining the scope of a trigger type.

indirect file

(Attache) A local file containing a list of files to be used by the get, put, find, or findmerge commands.

inherit, inheritance list

See trigger inheritance.

inheritance mode

(UNIX platforms only) A state of the hyperlink tree browser in which the browser displays both the hyperlinks that are directly connected to the displayed objects and the hyperlinks that are connected to ancestors of the displayed objects.Compare this to the hyperlink tree browser's direct mode.You can switch back and forth between these modes using the browser's menu.

insensitive

An insensitive button or menu command is greyed out and does not respond to pointer actions. Opposite: enabled.

installation host

A host on which ClearCase has been (or is about to be) installed.

installation method

An installation-time choice, specifying which installation host(s) are to be addressed, and whether software is to be installed or deinstalled.

installation model

An installation-time choice, specifying how the software for a ClearCase family product is to be transferred from the network-wide release area to one or more installation hosts.

instance

See type object.

integration branch.

A branch containing versions available to all members of a team. A team member often works in isolation on a private branch. To make private work available to others, the team member merges versions on the private branch with versions on the integration branch.

integration stream

A ClearCase UCM object that enables access to versions of the project's shared elements. A project contains only one integration stream. The integration stream maintains the project's baselines. The integration stream configures integration views to select the versions associated with the foundation baselines plus any activities and versions that have been delivered to the integration stream.

integration view

A view associated with a UCM project's integration stream.

Use an integration view to build and test the latest versions of a project's shared elements.

An integration view can be either a dynamic view or a snapshot view.

interactive mode

The mode of cleartool usage in which the program prompts you (with cleartool>) to enter a command, executes the command, then prompts you to enter another one. See single-command mode.

J

K

L

label

See version label.

label type

A type object that defines a version label for use within a VOB.

leaf name

The simple file or directory name at the end of a multiple-component pathname.

license

Permission for one user to run ClearCase programs and/or use ClearCase data, using any number of hosts in the local area network.

license database file

(UNIX platforms only) A file that defines a set of ClearCase licenses.

license database

(Windows platforms only) A data structure in the Windows NT Registry that defines a set of ClearCase licenses.

license priority

A slot in the scheme by which some ClearCase users can bump others, taking their licenses.

license server host

A host whose albd_server process controls access to the licenses defined in its license database file.

line of descent

The sequence of element versions leading to a particular version. This sequence may traverse branches.

link text

The text string that is the contents of a VOB symbolic link. (NOTE: On UNIX platforms, the link text can be the contents of a UNIX-level symbolic link.)

load

Copy a version of an element to a snapshot view and keep track of the checkins, updates, and other ClearCase operations affecting the element.

load rule

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. See also version-selection rule.

local command

(Attache) A command that affects only your workspace —— not any ClearCase storage (view or VOB).

local copy

During an auto-make-type operation, the copy of a global type object (located in an administrative VOB) that is created in a client VOB.

local file

(Attache) A file whose physical location is on your PC.

local shell

(Attache) A command shell executing on your PC.

lock

A mechanism that prevents a VOB object from being modified (for file system objects) or from being instanced (for type objects). See obsolete.

lock manager

A ClearCase server that arbitrates transaction requests to all VOB databases on the local host. A lockmgr runs on each ClearCase host. (NOTE: On Windows NT hosts, the lockmgr runs as a Windows NT service.)

log browser

A graphical tool that enables you to examine ClearCase log entries on one or more hosts in the network.

logical operator

A symbol that specifies a Boolean arithmetic operation.

logical packet

(MultiSite) The complete set of data required to create a new VOB replica, or to synchronize two or more existing replicas in a VOB family. A logical packet can encompass several physical files. See also physical packet.

lost+found

A subdirectory of a VOB's top-level directory, to which elements are moved if they are no longer cataloged in any version of any directory element. See orphaned element.

M

magic file

A file used by the ClearCase file typing subsystem to determine the type of an existing file, or for the name of a new file. A magic file consists of an ordered set of file-typing rules.

main branch

The starting branch of an element's version tree. The default name for this branch is main.

make macro

A parameter in a makefile, which can be assigned a string value within the makefile itself, in a build options spec, on the clearmake or omake command line, or by assuming the value of an environment variable. (NOTE: omake is supported only on Windows platforms.)

makefile

A text file, read by clearmake or omake, that associates build scripts, consisting of shell commands (executable commands), with targets. Typically, executing a build script produces one or more derived objects. (NOTE: omake is supported only on Windows platforms.)

Makefiles constructed for clearmake or omake need not include source-level dependencies (for example, header file dependencies), but they must include build-order dependencies (for example, that executable program hello is built using object module hello.o.

makefile dependency

See dependency.

master

(MultiSite) See mastering replica.

mastering replica

(MultiSite) The mastering replica of a ClearCase object is the only replica at which the object can be modified or instances of the object can be created.

mastership

(MultiSite) The ability to modify an object, or to create instances of a type object.

merge

The combining of the contents of two or more files or directories into a single new file or directory. Typically, when merging files, all the files involved are versions of a single file element. When merging directories, all contributors to the merge must be versions of the same directory element.

merge output file or directory

The output of a merge operation. Once you have resolved any conflicting differences between contributors, you can save the merged contents into the merge output file or directory. Typically, the merge output file or directory is written to the CHECKEDOUT version of the contributor to which you are merging.

meta-data

Data associated with an object, supplementing the object's file system data.

Example: The contents of a file version is a series of text characters. User-specified meta-data annotations attached to the file version includes version labels, attributes, and hyperlinks. ClearCase automatically maintains other meta-data for some objects, in the form of event records and configuration records.

method

A program, subroutine, or utility that implements one of the functions of a type manager.

minor event

An event whose event record is, by default, not displayed by the history browser or listed by the lshistory command.

mnode

An MVFS-specific data structure, used to maintain information about an MVFS object. An mnode is attached to an operating-system vnode, as private data.

mode

See access mode.

mounted VOB

An active VOB.

MSDOS-enabled mode

An operating mode for a VOB, wherein the VOB database tracks the number of lines in a text file, enabling correct file-size reporting on both UNIX and Windows NT systems.

MSDOS text mode

See text mode.

multiversion file system (MVFS).

A directory tree which, when activated (mounted as a file system of type MVFS) implements a ClearCase VOB. To standard operating system commands, a VOB appears to contain a directory hierarchy; ClearCase commands can also access the VOB's meta-data. Also, MVFS file system refers to a file system extension to the operating system, which provides access to VOB data. The MVFS file system is not supported on all ClearCase platforms.

MVFS cache

An in-memory data structure that speeds MVFS performance. Data on several kinds of file system resources are maintained, in separate caches.

MVFS object

A file or directory whose pathname is within a VOB (that is, whose pathname is within the directory tree beneath the top-level VOB-tag. A non-MVFS object has a pathname that is not within a VOB.

N

namespace

A file/directory name hierarchy. Different views can see different namespaces, because they can select different versions of directory elements. See extended namespace.

network provider

(Windows platforms only) A supplier —— an extended file system or Windows NT Server, for example —— of a complete networking system for Windows NT hosts. Because it functions as a network provider, the ClearCase MVFS deactivates VOBs and views at user login time. (NOTE: For UNIX platforms, see virtual file system.)

network region

A logical subset of a local area network, within which all hosts refer to VOB storage directories and view storage directories with the same network pathnames.

nobody

(UNIX platforms only) The username sometimes assigned to a remote process owned by the root user on the local host.

non-ClearCase access

(UNIX platforms only) Access to ClearCase data from a host on which ClearCase has not been installed.

nonmastered checkout.

An unreserved checkout performed on a branch that is not mastered by the local VOB replica.

non-MVFS object

See MVFS object.

nonshareable derived object

A derived object that cannot be winked in by other views. If your dynamic view is configured with the nonshareable DO property, the ClearCase build programs create DOs in the view, but do not write shopping information into the VOB.

notice forwarder

(UNIX platforms only) One of the message-passing programs in an H-P SoftBench environment.

null-ended

A hyperlink that is connected to only one object, not two.

O

object

An item stored in a versioned object base —— elements, versions of elements, branches, derived objects, hyperlinks, locks, pools, and types, and so on. An object can identified by an object-selector string, which includes a prefix indicating the kind of object, the object's name, and a suffix indicating the VOB in which the object resides. Examples: lbtype:REL1@/vobs/vega on UNIX and lbtype:REL1@\vega on Windows

object-ID (OID)

A ClearCase-internal identifier for an object. See UUID.

object registry

A network-wide database, which records the actual storage locations of all VOB storage directories and all view storage directories. The mktag, rmtag, mkview, rmview, mkvob, rmvob, register, and unregister commands add, delete, or modify registry file entries.

obsolete object

An object that has been locked with the command lock –obsolete. By default, such objects are not listed by commands such as lstype and lslock.

OID

See object-ID.

oplog

(MultiSite) A list of all changes that have been made to a VOB's database.

oplog entry

(MultiSite) The record of a single change to a VOB. Each oplog entry includes the identity of the originating replica and the epoch number of the operation.

ordinary type object

A type object that is neither a global type object, nor a local copy of one. Prior to ClearCase V3, all type objects were ordinary.

originating replica

(MultiSite) The replica at which an operation was first performed.

orphaned element

An element that is no longer cataloged in any version of any directory. Such elements are moved to the VOB's lost+found directory.

owner

The user who owns a VOB, a view, or an individual object. The user who creates an object becomes its initial owner.

ownership-preserving

(MultiSite) The subset of replicas within a VOB family whose elements share the same user and group identities. Only one such subset is allowed per VOB family.

P

packet

See logical packet, physical packet.

pairwise difference

How the command-line output of cleartool commands (such as diff, cleardiff, merge, and findmerge) represent differences between contributors to the comparison or merge. For example, if three contributors (contrib2, contrib3, and contrib4) all differ from the base contributor (contrib1) in a particular section, the command-line output lists the contrib1-contrib2 difference, followed by the contrib1-contrib3 difference, followed by the contrib1-contrib4 difference.

parallel build

(UNIX platforms only) A build process in which multiple build scripts are executed concurrently. See also distributed build.

parallel development

The concurrent creation of versions on two or more branches of an element.

pathname

A sequence of directory names, perhaps ending with a simple filename. A pathname that begins with a backslash (\), or with a drive letter (A:, B:, C: ...) and backslash (on Windows) or a "/", indicating the root directory (on UNIX), is termed a full pathname. Any other pathname is termed a relative pathname. See extended pathname, namespace, absolute VOB pathname.

pattern

A character string that specifies one or more file and/or directory names. Examples:

UNIX:

/usr/project/.../include
*.c
lib/*.[ch]

Windows:

\proj_1\...\include
*.c

See scope, version selector, config spec.

Perl

A general-purpose scripting language (Practical Extraction and Report Language).

permission

Ability to perform an operation that modifies a file, directory, or other object.

persistent VOB / persistent view

(Windows platforms only) A VOB or view that is automatically activated each time you login.

physical packet

(MultiSite) A file containing one part of a logical packet.

pool

See storage pool.

pool inheritance

The feature by which a newly-created element is assigned to the same VOB storage pools as its parent directory element.

post-operation trigger

A trigger that fires after the associated operation.

pre-operation trigger

A trigger that fires before the associated operation, possibly canceling the operation itself.

predecessor version / successor version

A version of an element that immediately precedes another version in the element's version tree. If version X is the predecessor of version Y, then Y is the successor of X. If there is a chain of predecessors linking two versions, one is called an ancestor of the other.

primary group

(Windows platforms only) The first group to which a user belongs. Typically, this domain-wide group assignment is made by the administrator using the User Manager for Domains utility. A user can belong to additional groups, as well.

primary registry server host

See registry server host.

principal group

(UNIX platforms only) The group to which a user belongs, by virtue of being listed in the password database. A user can belong to additional groups, as well.

private storage area

The directory tree (.s) in which view-private files, directories, and links are stored. By default, this is a subtree of the view storage directory, but ClearCase supports creation of remote private storage areas.

private branch.

A branch on which a team member works in isolation from other members of the team. The branch is usually created at a stable version identified by a label. The team member makes private work available to others by merging versions on the private branch with versions on an integration branch.

private VOB-tag

See public VOB-tag.

process of restoration

(MultiSite) The special state into which the MultiSite restorereplica command places a VOB replica after it has been restored from backup. The replica remains in this state until its database has been made consistent (through synchronization updates) with the other replicas in its VOB family.

project

A ClearCase UCM object that contains the configuration information needed to manage a significant development effort, such as a product release. Use the project to set policies that govern how developers access and update the set of files and directories used in the development effort. A project includes one integration stream, which configures views that select the latest versions of the project's shared elements, and typically multiple development streams, which configure views that allow developers to work in isolation from the rest of the project team.

project configuration file

(Attache) A local file containing a list of files to be used by the File`Update Workspace command.

Project VOB (PVOB)

A VOB that stores UCM objects, such as projects, streams, activities, and change sets. Every UCM project must have a PVOB. Multiple projects can share the same PVOB.

promotion

Migration of a derived object from view storage (unshared or nonshareable) to VOB storage (shared).

QUERY: The preceding definition conflicts with the UCM definition of promotion/demotion below. Should we say something about that in one place or the other? —— Arte

promotion level.

A property of a UCM baseline that can be used to indicate the quality or degree of completeness of the activities and versions represented by that baseline. You can use promotion levels to define policy for a UCM project.

UCM provides an ordered set of default promotion levels, and also supports user-defined promotion levels.

The action of changing the promotion level of a baseline is called promoting or demoting the baseline.

properties browser

A graphical tool that enables you to examine the properties of a VOB database object, including its meta-data annotations.

protection mode

See access mode.

prune

(hyperlink browser) Removing all objects to the right of the selected object.

pseudotarget

A makefile target that is not a file system object.

public VOB-tag

All VOB's with public VOB-tags get mounted automatically by the cleartool mount -all command. (On UNIX, the standard ClearCase scripts run this command as part of the boot process that starts ClearCase and so all public VOBs are typically always mounted.) Creating a VOB with a public VOB-tag requires that you know the VOB-tag password. (See also VOB-tag password file.)

On UNIX platforms, any user can mount or unmount a public VOB by naming it explicitly using the cleartool mount or unmount command. If a VOB's VOB-tag is private, only the VOB's owner or the root user can mount or unmount the VOB.

On Windows platforms, any user can mount or unmount any VOB, public or private, by naming it explicitly using the cleartool mount or unmount command. The private designation means only that the VOB must be mounted explicitly by name.

put

(Attache) The command that uploads one or more files from your workspace to its associated view.

PVCS

The Polytron Version Control System.

pVOB

See Project VOB (PVOB).

Q

query language

A collection of predicates and logical operators that allows selection of elements, branches, and versions based on their associated meta-data. This language can be used in config specs, in the ClearCase find command, and in the –version option to many commands.

R

RCS

The Revision Control System.

rebase

A ClearCase UCM operation that makes your development work area current with the set of versions represented by a more recent baseline in the integration stream.

recommended baseline

The set of baselines that the project team should use to rebase their development streams. In addition, when developers join a project, their development work areas are initialized with the recommended baselines.

The recommended baselines represent a system configuration, or set of components, that has achieved a specified promotion level. A baseline becomes part of the set of recommended baselines when the project manager promotes it to a certain promotion level, for example, TESTED.

record

See event record, configuration record.

recovery incarnation

(MultiSite) A numerical value associated with a replica; it is incremented if the replica undergoes restoration from backup. This value is attached to outgoing packets and is used by other replicas to determine whether the packet was sent before or after the restoration (and, therefore, if they should import it).

reference count

The number of references to a derived object from multiple views. When scrubbing, the reference count is evaluated to determine whether to delete the derived object to free storage space.

reference time

See build reference time.

refinement

See supertype.

region

See network region.

register

Create an entry in the tags registry and/or the object registry, for a view or a VOB.

registry Region

See network region.

registry server host

The host on which all ClearCase data storage areas (all VOBs and views) in a local area network are centrally registered. ClearCase supports a primary and backup registry server host. The backup host is used if the primary host becomes unavailable. See the rgy_backup reference page.

relative pathname

A pathname that does not begin with a "/" on UNIX or with a "\", or with a drive letter and backslash (Z:\).

release area

A directory structure, accessible by all client hosts, containing the software distribution for one or more products in the ClearCase product family. In particular, a merged release area holds the distributions for two or more products.

release host

The host on which the ClearCase software is unloaded from the distribution medium.

relocate set

The set of file and directory elements that are actually moved by the relocate command; a subset of the selection set.

remote command

(Attache) A command that affects only ClearCase storage (view or VOB), not your workspace.

remote Deliver

(A variation of the UCM deliver operation. UCM uses remote deliver in a ClearCase MultiSite configuration when the project's integration stream and individual development stream are mastered in different replicas. When these conditions exist, a developer starts the deliver operation at the remote site but leaves it in a posted state. The project manager must complete the deliver operation at the integration stream's replica site.

remote storage pool

See storage pool.

replica

(MultiSite) An instance of a VOB, located at a particular site. A replica consists of the VOB's database, along with all of the VOB's data containers.

replica-creation packet

(MultiSite) A logical packet that contains the data for creating one or more new replicas within a VOB family.

replica object

(MultiSite) The VOB database object that records the existence, name, site location, and other details of a particular VOB replica.

replica UUID

(MultiSite) See VOB family.

replicated VOB

(MultiSite) A VOB for which two or more replicas currently exist.

rerooting

(hyperlink browser) Removing all objects to the left of the selected object.

reserved checkout

See checkout.

restoration update packet

(MultiSite) A packet that contains specially requested data from a VOB replica, for use in restoring the database of another replica.

restriction list

A specification of which type objects are to be associated with a trigger type.

resynchronizing the workspace

(Attache) Using a get or find –get command to ensure that your workspace contains the same data as its associated view.

return bay

(MultiSite) A directory that holds incoming or outgoing MultiSite packets that are in the process of being returned to their origin because they could not be delivered to all specified destinations.

reuse

During a build in a view, using an existing derived object in that view instead of winking in a DO from another view or rebuilding the DO.

root

(UNIX platforms only) The privileged superuser on a UNIX host.

S

s-file

(UNIX platforms only) A file in which SCCS stores all versions of a versioned file.

same-VOB hyperlink

A hyperlink that connects two objects in the same VOB.

schema

The format of a database.

scheme file

(UNIX platforms only) A file that contains a collection of X Window System resources, which control various aspects of GUI applications.

scope

The part of a config spec rule that restricts it to a particular kind of file system objects. See config spec, pattern, version selector.

scrubbing

Freeing storage space by removing objects that are no longer used:

An expression used by ClearCase's file typing mechanism to match a file system object (or just the name of one). The expression consists of selection operators and logical operators.

selection operator

See selection expression.

selection set

The set of file and directory elements that are candidates for processing by the relocate subcommand, as specified by command arguments.

selective merge

A merge that includes the changes contained in only a specified subset of ancestors. For example, if you are merging a contributor version /main/bugfix/4, but do not want the changes in the /main/bugfix/3 version of that contributor, a selective merge allows you to include the changes in versions 1, 2, and 4 on the /main/bugfix branch, but to omit the changes in the /main/bugfix/3 version.

self-mastering replica

(MultiSite) A replica that masters its own replica object.

semi-live backup

See VOB database snapshot.

server

See albd_server, view_server, vob_server, workspace helper.

setGID, setUID

The UNIX facility by which the operating system process in which a program runs gets its group-ID (setGID) or its user-ID (setUID) from the file in which the program is stored, rather than from user who invoked the program.

set view

(noun) (UNIX platforms only) The view context of a process, established by using the setview command. Setting a view creates a process in which all standard pathnames are resolved in the context of a particular view. See working directory view.

shareable derived object

A derived object that can be winked in by other views.

shared derived object

A derived object whose data container is located in a VOB's derived object storage pool. The DO may be referenced by multiple views.

shared type object

(MultiSite) A type object whose instances can be managed at any replica. Creation of a new instance is controlled by the mastership of the object to which the new instance will be attached.

sharename

(Windows platforms only) The name assigned to a drive or directory that is shared using the Sharing tab of the Properties dialog box in the Windows Explorer (or net share on the command line). A sharename is the second component in a UNC name.

shipping order

(MultiSite) A file that contains information for use by the MultiSite store-and-forward facility to deliver an update packet.

sibling

During a build, a derived object created by the same build script as another derived object. In MultiSite, a replica's siblings are the other replicas in its VOB family.

SID

(Windows platforms only) Security Identifier. A variable-length structure that uniquely identifies a user or group across all Window NT systems. The primary datum in a SID is a 48-bit value: the first 16 bits identify the SID-issuing agency —— typically a Windows NT Server domain —— and the remaining 32 bits identify a user or group within that issuing agency.

single-command mode

The usage mode for a CLI tool in which you specify the tool's name (for example, cleartool), a subcommand, options, and arguments at an operating system command prompt. After executing that one (sub)command, the CLI tool exits.

site

(MultiSite) A location where one replica in a VOB family resides.

snapshot view

A view that contains copies of ClearCase elements and other file system objects in a directory tree. You use an update tool to keep the view current with the VOB (as specified by the config spec).

snapshot view update

A ClearCase operation you invoke to ensure that the versions in the view are the same versions in the VOB selected by the config spec. When necessary, an update operation copies files and directories from the VOB or removes or renames files and directories in the view.

SoftBench

(UNIX platforms only) An interprocess messaging system.

source control

See version control.

source dependency

See dependency.

source pool

A storage pool for the data containers that store versions of file elements.

start-up directory

(Attache) The working directory of the Attache program when you start an Attache session. The default is attache-home-dir\bin. To change the startup directory in Windows 95: on the shortcut menu for the Attache icon, click Properties, then click the Shortcut tab and enter a directory in the Start in box. To change the startup directory in Windows 3.1: on the File menu for the Program Manager or File Manager, click Properties.

storage bay

(MultiSite) A directory that holds MultiSite packets and shipping orders for use by the store-and-forward facility.

storage class

(MultiSite) A user-specified name that is associated with certain information-delivery parameters by the MultiSite store-and-forward facility. For example, each storage class is associated with a particular storage bay (or set of bays) and a particular expiration period.

storage pool

A source pool, derived object pool, or cleartext pool. If it resides on a different host than the VOB database, it is termed a remote storage pool.

storage registry

See object registry.

store-and-forward

(MultiSite) The MultiSite facility for transferring packets (or other files) among sites, either directly or through intermediate hops.

stranded configuration record

A configuration record (CR) that does not correspond to any existing derived object.

stranded derived object

A derived object that cannot be accessed, because the VOB directory in which it was created is not currently accessible or has been deleted.

stranded view-private file

A view-private file that cannot be accessed, because it has no name in the VOB namespace, as currently constructed by your view. The lsprivate command lists such files; the recoverview command salvages them.

stream

A ClearCase UCM object that determines which versions of elements appear in any view configured by that stream. Streams maintain a list of baselines and activities. A project contains one integration stream and typically multiple development streams.

subbranch

A branch of an element's version tree other than the main branch.

subsession

A build session that is started while a higher-level build session is active.

subtarget

In a hierarchical build, a makefile target upon which a higher level target depends. Subtargets must be built, reused, or winked in before higher-level targets.

subtractive merge

A merge operation that removes the contributions of one or more ancestors of a version.

successor version

See predecessor version.

supertype

An element type that is used as the basis for defining another element type (said to be a refinement of the supertype).

synchronization update packet

(MultiSite) See update packet.

T

tags registry

A network-wide database, which records the globally-valid access paths to all VOB storage directories (or all view storage directories), along with the VOB-tags (or view-tags) with which users access these data structures.

target, target rebuild

A target rebuild is the execution of a build script associated with a particular target in a makefile. Each target rebuild produces derived objects along with a configuration record, which includes an audit of the files involved in the actual target rebuild.

text_file

A ClearCase element type that uses delta management to combine all versions of an element into a single data container. The associated type manager is named text_file_delta.

text_file_delta

The type manager for the predefined text_file element type.

text mode

A view is assigned a text mode when it is created. The text mode determines how the view handles line termination sequences —— unix: <NL>, msdos: <CR><NL>. See mkview.

text-only

A hyperlink for which there is no to object, only a text annotation on the from object.

time rule

A separate config spec rule that specifies a time to which the special version label LATEST should evaluate in all subsequent rules; or, a clause that sets the LATEST time within an individual rule.

title bar

The standard Microsoft Windows colored bar at the top of a window. For example, the Attache window's title bar shows the product name, along with the name of the current workspace and the host where the workspace helper program is running.

to-object

See hyperlink.

to-text

A string-valued attribute attached to a hyperlink object, conceptually at its to end.

transcript pad

(Attache) The Command window also acts as a historical record of command execution. In this window, the commands you enter are interspersed with the commands' output.

translation file

A file that controls the mapping of symbols, branch names, and label names to ClearCase branch and label names during export of ClearCase, PVCS, RCS, SCCS, or SourceSafe data. Use this file to enforce naming consistency over multiple invocations of the exporter program. See the clearexport_ccase, clearexport_pvcs, clearexport_rcs, clearexport_sccs, and clearexport_ssafe reference pages. (NOTE: clearexport_ssafe is supported only on Windows platforms.)

transparency, transparent access

The ClearCase feature that enables standard programs to access versioned files and directories using standard pathnames.

trigger

A monitor that specifies one or more standard programs or built-in actions to be executed automatically whenever a certain ClearCase operation is performed. See pre-operation trigger, post-operation trigger, trigger type.

trigger inheritance

The process by which triggers in the inheritance list of a directory element are automatically attached to new elements created within the directory.

trigger type

An object through which triggers are defined. Instances of an "element" trigger type can be attached to one or more individual elements ("attached trigger"). An "all-element" trigger type is implicitly attached to all elements in a VOB. A "type" trigger type is attached to a specified collection of type objects.

trivial merge

A merge in which the base contributor and the contributor to which you are merging are the same. In this case, all differences are between the base contributor and the contributor from which you are merging. ClearCase just copies the contributor from which you are merging to the contributor to which you are merging.

type

A type object defines a ClearCase data structure. Users can create instances of these structures: meta-data annotations are placed on objects by creating instances of label types, attribute types, and hyperlink types. Each version-controlled file and directory is an instance of an element type; each branch is an instance of a branch type; and so on.

type object

An object that defines the characteristics of (acts as the prototype for) an entire category, or class, of data items. ClearCase defines label types, branch types, hyperlink types, and so on.

type manager

A set of routines (methods) that stores and retrieves versions of file elements from disk storage. Some type managers include methods for other operations, such as comparison, merging, and annotation. See the type_manager reference page.

type trigger type

A trigger type that is associated with (and thus, monitors changes to and usage of) one or more type objects.

U

umask

The UNIX file creation mode mask, a three-digit octal number. The three digits (each zero by default) refer to read/write/execute permissions for owner, group, and others, respectively. Each digit is subtracted from the corresponding digit specified by the system for the creation of a file. (See creat(2) on UNIX platforms.) For example, umask 002 removes write permission for others —— files normally created with mode 777 become mode 775; files created with mode 666 become mode 664. Note that the default umask is 022, but ClearCase strongly recommends a umask of 002 (or, simply, 2); otherwise, VOB, view, and derived object sharing can be problematical.

If you are operating in a mixed UNIX/Windows NT environment, accessing UNIX VOBs and views via a PC-based NFS client product, configure the PC-side NFS umask to 002.

UNC name

(Windows platforms only) A convention for naming shared resources. The UNC name for a shared resource (file, directory, printer, etc.) has the following form:

\\hostname\sharename\rest-of-path 

Use UNC names to specify VOB and view storage directories in mkvob, mkview, and mktag commands. See also sharename.

uncheckout

The act of cancelling a checkout operation.

unidirectional

See hyperlink.

unified change management (UCM)

An out-of-the-box process, layered on base ClearCase and ClearQuest functionality, for organizing software development teams and their work products. Members of a project team use activities and components to organize their work.

universal unique identifier

See UUID.

unix text mode

See text mode.

unload

Remove information about an element from a snapshot view, and delete the version from the view. To unload a directory element, ClearCase

See storage registry.

unreserved checkout

See checkout.

unshared derived object

A derived object that has never been winked in to another view.

unshared type object

(MultiSite) A type object whose instances can be created and managed only at its mastering replica.

update packet

(MultiSite) A logical packet that contains data for synchronizing some or all of the existing replicas in a VOB family.

update a snapshot view

See snapshot view update.

upload

(Attache) Transfer data from Attache to the workspace helper host.

uploading files

(Attache) Copying files from your workspace to its associated view.

user profile

A file that stores specifications for comment handling by individual cleartool subcommands.

UUID

Universal unique identifier. ClearCase uses UUIDs to track VOBs, views, and the objects they contain.

V

version

An object that implements a particular revision of an element. The versions of an element are organized into a version tree structure. Also: checked-out version can refer to the view-private file that corresponds to the object created in a VOB database by the checkout command.

version 0

The original version on a branch. It is automatically created when the branch is created, and has the same contents as the version at the branch point. Version 0 on the main branch is defined to be empty.

version control

The discipline of tracking the version evolution of a file or directory.

version-extended namespace

See extended namespace, VOB-extended namespace.

version-extended pathname

A pathname that explicitly specifies a version of an element (or versions of several elements), rather than allowing version-selection to be performed automatically by a view.

version-ID

A branch pathname and version number, indicating a version's exact location in its version tree. Examples:

UNIX:

/main/4
/main/rel2_bugfix/2
/main/bugs/bug405/9

Windows:

\main\4
\main\rel2_bugfix\2
\main\bugs\bug405\9
version label

An instance of a label type object, supplying a user-defined name for a version. See object, meta-data.

version-number

The ClearCase-assigned integer that identifies the position of a version on its branch.

version selection

The process of choosing a specific version from an element's version tree. A view has several mechanisms that perform version selection. Users can select versions with version-extended pathnames and with the ClearCase query language.

version-selection rule

A statement in the config spec that specifies a version of an element to be selected by the view. See also load rule.

version selector

A specification (for example, /main/17 (on UNIX platforms), \main\17 on Windows platforms), or RLS4.3-BETA (on all platforms)) that identifies particular versions of one or more elements. See version selection, scope, pattern and configuration specification, and the version_selector reference page.

version tree

The hierarchical structure in which all the versions of an element are (logically) organized. When displaying a version tree, ClearCase also shows merge operations (indicated by arrows in the illustration).

versioned object base (VOB)

A repository that stores versions of file elements, directory elements, derived objects, and meta-data associated with these objects. With MultiSite, a VOB can have multiple replicas, at different sites.

view

A ClearCase object that provides a work area for one or more users —— to edit source versions, compile them into object modules, format them into documents, and so on. Users in different views can work with the same files without interfering with each other. For each element in a VOB, a view's config spec selects one version from the element's version tree. Each view can also store view-private files and view-private directories, which do not appear in other views. There are two kinds of views: snapshot views and dynamic views.

View contents

(Attache) One of the two top-level entries listed in the File Browser for the current workspace. When expanded it shows all the VOBs currently active on the workspace helper host, as seen through the view associated with the current workspace.

view context

The view (if any) that will be used to resolve a pathname to a particular version of an element.

view database

The database that tracks objects in a view.

view-extended namespace

See extended namespace.

view-extended pathname

A pathname that begins with a view prefix (for example, /view/alpha on UNIX, or M:\alpha on Windows), specifying a particular view to be used for resolving element names to particular versions.

view host

A host on which one or more view storage directories reside.

view log

A log file, located on a particular machine, that records errors in accessing the view storage areas on that machine.

view object

An object stored in a view: a checked-out version of a file, an unshared derived object, a nonshareable derived object, or a view-private file, directory, or link. No historical information is retained for view objects. See VOB object.

view prefix

One or more components at the beginning of a pathname that specify a particular dynamic view. For example, on Windows, M:\gamma (or when M: is the current drive, simply \gamma), and on UNIX, /view/gamma. See also viewroot directory.

view-private directory

A directory that exists only in a particular view, having been created with the standard mkdir command. A view-private directory is not version-controlled, except insofar as it is separate from private directories in other views.

view-private file

A file that exists only in a particular view. A private file is not version-controlled, except insofar as it is separate from private files in other views.

view-private object

A file or directory that exists only in a particular view. View-private objects are not version-controlled. See view-private directory and view-private file.

view profile.

(Windows platforms only) A description of a ClearCase configuration that is shared by members of a team working on a project. A view profile includes the following information: the VOBs used by the project; the name of the administrative VOB, if any; a config spec; a list of labels identifying stable versions from which to create private branches; and the branch type of the integration branch. To use this shared configuration, a team member works in a view associated with the view profile.

view registry

See view storage registry, object registry, tags registry.

viewroot directory

(The portion of an absolute path to an element that precedes the view-tag of a snapshot view. See also dynamic-views root directory and view prefix.

view_server

The daemon process that interprets a view's config spec, mapping element names into versions, and performs workspace management for the view.

view storage directory

The directory tree ClearCase uses to maintain internal information about a view. Along with other files and directories, the view storage directory contains the config spec and the view database.

view storage registry

A file on the network's registry server host that records the view storage directory of every view in the network.

view-tag

The name with which users reference a view.

virtual file system

(UNIX platforms only) An extension to the UNIX kernel, allowing alternative file systems to be implemented without revision to the kernel itself. (NOTE: For Windows platforms, see network provider.)

vnode

An operating system kernel data structure, representing a file or directory. See also: mnode.

VOB

See versioned object base.

VOB browser

A graphical application that administrators use to create, maintain, and control access to the VOBs in a local area network.

VOB database

The part of a VOB storage directory in which ClearCase meta-data and VOB objects (elements, branches, versions, and so on) are stored. This area is managed automatically by ClearCase's embedded database management software. The actual file system data, by contrast, is stored in the VOB's storage pools.

VOB database snapshot

A copy of a VOB database, made by the vob_snapshot utility, which enables a VOB storage directory to be backed up without locking the VOB.

VOB-extended namespace

An extension to the operating system's file naming scheme, which allows any historical version of an element to be accessed directly by any program. The extension also provides access to the meta-data (but not the file system data) of all of a VOB's existing derived objects.

VOB family

(MultiSite) The set of all replicas of a particular VOB. All the replicas share the same VOB family UUID; each replica has its own VOB replica UUID.

VOB hard link

A name, cataloged in a (version of a) directory element, for an element. Typically, the first such link is called the element's name; the term VOB hard link is used to refer to any additional names for the element.

VOB host

A host on which one or more VOB storage directories reside.

VOB link

A VOB symbolic link or VOB hard link.

VOB mount point

The directory on which a VOB storage directory is mounted. All UNIX commands, and most ClearCase commands, access a VOB through its mount point. (NOTE: For Windows platforms, see VOB-tag.)

VOB object

An object stored in a VOB: element, version of element, type, hyperlink, derived object, and so on. See view object. Also, the object in a VOB database that records the existence and identity of the VOB itself.

VOB owner

Initially, the user who created a VOB with the mkvob command. The ownership of a VOB can be changed subsequently, with the protectvob command. Replicas at different sites may or may not have the same owner.

VOB registry

See VOB storage registry, object registry, tags registry.

VOB replica

(MultiSite) See replica.

VOB replica object

(MultiSite) See replica object.

VOB root directory

The top-level directory of a VOB, accessed through the pathname of its mount point (for example, /vobs/project_x) on UNIX platforms or through the pathname of its VOB-tag (for example, \proj_vob) on Windows platforms.

vob_server

The process that provides access to the data containers that store versions' file system data.

VOB storage directory

The directory tree in which a VOB's data is stored: elements, versions, derived objects, CRs, event history, hyperlinks, attributes, and other meta-data.

VOB storage registry

A file on the network's registry server host that records the actual storage locations of all the VOBs in the network.

VOB symbolic link

An object, cataloged in a (version of a) directory element, whose contents is a pathname. ClearCase does not maintain a version history for a VOB symbolic link.

VOB-tag

For UNIX platforms, this is the full pathname at which users access a VOB. The VOB storage directory is activated by mounting it as a file system of type MVFS at the location specified by its VOB-tag.

For Windows platforms, this is the VOB's registered name and also its root directory —— the pathname at which users access VOB data. A VOB-tag has a single component and begins with the backslash character (\). For example, \myvob and \vob_project2 are valid VOB-tags.

VOB-tag password

The password required to create a public VOB-tag. The password is maintained on the ClearCase registry server host. (On Windows, the password is maintained in the Windows NT Registry on the registry server host.)

VOB-tag password file

A file used to validate the password entered by a user when creating a public VOB-tag.

VPATH

A make macro that specifies directories that will be searched for data during a build.

vtree browser

A graphical application with which you can examine the structure of an element's version tree.

W

wildcard

See pattern.

Windows NT Server domain

(Windows platforms only) A group of Windows NT Server hosts that share a common security policy and user account database. A single Windows NT Server host acts as the primary domain controller. Each non-Server host can belong to at most one domain.

winkin

Causing a shareable derived object to appear in a view, even though its file system data is actually located in a VOB's derived object storage pool. Also, converting a nonshareable derived object to a shared derived object.

working directory

See current working directory.

working directory view

The view context of a process, established by using the cd command to change the current working directory to a view-extended pathname or a snapshot view. On UNIX platforms, see set view.

working disconnected

(Attache) Using data that has been downloaded to your PC using Attache, but without having an active Attache session.

workspace

(Attache) A private directory tree on your PC, which contains local copies of data files under ClearCase version control. The current workspace is the one active in the Attache window. The workspace name appears in the title bar and in the command prompt.

Workspace Contents

(Attache) One of the two top-level entries listed in the File Browser for the current Attache workspace. When expanded it shows the contents of the current workspace.

workspace helper

(Attache) A server program, running on some ClearCase host, that maintains a TCP/IP connection to the Attache client program running on your PC.

workspace helper host

(Attache) The ClearCase host on which the workspace helper program is running.

workspace name

(Attache) The name of a workspace, as specified in the mkws command (command-line interface) or the File`New Workspace command (graphical interface). Same as the view-tag of its associated view.

workspace registry

(Attache) A list, maintained by Attache, of all the workspaces that currently exist on your PC.

workspace root

The top-level directory of a workspace. All VOB-tags appear as subdirectories of this top-level directory.

workspace storage directory

(Attache) The location on your PC where a workspace resides.

X

Y

Z

z_text_file_delta

The type manager for the predefined compressed_text_file element type. See delta.



techpubs@rational.com

Copyright © 1993-1999, Rational Software Corporation. All rights reserved.