IPnom Home • Manuals • ClearCase

 Rational ClearCase Commands Reference

ClearCase Stuff:ClearCase LinksClearCase BooksClearCase Commands ReferenceClearCase ForumsClearCase News
Keyword Live Search (10 results max):
 Type in part of a ClearCase command in the search box.
Commands Index:


Creates a component object


ProductCommand type
ClearCasecleartool subcommand
ClearCase LTcleartool subcommand



mkcomp [ –c·omment comment | –cfi·le pname | –cq·uery | –nc·omment ]
{ –roo·t root-dir-pname | –nro·ot }


The mkcomp command creates a component. The scope of a UCM project is declared in terms of components. A project must contain at least one component, and it can contain multiple components. Projects can share components.

An ordinary component groups directory and file elements. The directory and file elements of a component are stored in a VOB. The component object is stored in a project VOB (PVOB). You organize a component's directory and file elements into a directory tree in a VOB. A component's root directory must be the VOB's root directory or one level beneath it. A component includes all directory and file elements under its root directory. To store multiple components in a VOB, make each component's root directory one level beneath the VOB's root directory. If you make a component at the VOB's root directory, that VOB can never contain more than that one component.

An initial baseline is created when you create a component. This baseline selects the /main/0 version of the component's root directory. Use this as a starting point for making changes to the component.

You can use the –nroot option to create a special type of component that holds only composite baselines and no file elements.

Elements cannot be moved from one component to another. Therefore, you cannot reorganize a component into multiple components.

A component cannot be renamed if its root directory is one level beneath the VOB's root directory .

When converting a subdirectory of an existing non-UCM VOB into a component, mkcomp checks each element recursively to see whether any are already associated with a different component. (This may occur when an element has hard links outside the component.) If any are found, the command fails. Remove such hard links with rmname and replace them with a symbolic link before proceeding.



You must have one of the following identities:

  • VOB owner
  • root (UNIX)
  • Member of the ClearCase administrators group (ClearCase on Windows)
  • Local administrator of the ClearCase LT server host (ClearCase LT on Windows)


An error occurs if one or more of these objects are locked: the project VOB, the root directory VOB.


(Replicated VOBs only) For a component whose root directory is the VOB's root directory, you must master the root directory element. For a component whose root directory is one level beneath the VOB's root directory, you must master all elements that are to be grouped in the component.


Event Records and Comments

 Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: –nc). See the comments reference page. Comments can be edited with chevent.

–c·omment comment | –cfi·le comment-file-pname |–cq·uery | –cqe·ach | –nc·omment
Overrides the default with the option you specify. See the comments reference page.

The comment is stored in the creation event of the component object.

Specifying What Type of Component to Create

–roo·t root-dir-pname
Specifies a component to be created to group directories and elements and the root directory pathname for this component. To create one component per VOB, the root-dir-pname must be the root directory of a VOB. To create multiple components per VOB, the root-dir-pname must be one level beneath the VOB's root directory. If the specified subdirectory does not already exist, it is created by the mkcomp operation.

Specifies a component to be created to hold only composite baselines. This type of component does not contain directories or file elements.

Specifying a Component Selector

Identifies the component.

component-selector is of the form [component:]component-name[@vob-selector] where vob is the component's UCM project VOB.

If no vob-selector is given, the component is created in the project VOB if it contains the current working directory; otherwise, the component is not created.

The component name must be unique within the PVOB. All UCM objects share the same namespace. You'll get an error if the name you provide collides with the name of an existing UCM object, for example, a project.


The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.

The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.

In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.

Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.

  • Create a component.

    cmd-context  mkcomp -c "modeling component" \
    -root /vobs/webo_modeler webo_modeler@/vobs/webo_pvob
    Set Admin VOB for component "webo_modeler"
    Created component "webo_modeler".


lscomp, mkbl, rmcomp



ClearCase Links • ClearCase Books • ClearCase Commands Reference • ClearCase Forums • ClearCase News