mkcomp

Creates a UCM component object

APPLICABILITY

SYNOPSIS

mkcomp [ -c·omment comment | -cfi·le pname | -cq·uery | -nc·omment ]

-root dir-pname component-selector

DESCRIPTION

The mkcomp command creates a UCM component. A component groups directories and file elements. 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.

This command must be used within a view context.

Component objects live in project VOBs, and point to directory elements. All elements below the directory root are in the component.

An initial baseline is automatically 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.

RESTRICTIONS

Identities: No special identity required.

Locks: An error occurs if there are locks on the following objects: the UCM project VOB.

Mastership: The master replica of the indicated objects must match the replica (originally) performing the operation

OPTIONS AND ARGUMENTS

EVENT RECORDS AND COMMENTS. Default: 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 A COMPONENT SELECTOR AND LOCATION.

-root dir-pname

Specifies the root directory pathname for this component. The directory-pathname must be the root directory of a VOB. A VOB directory can be referenced only by one component in one project VOB.

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.

EXAMPLES

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. In Attache, cmd-context represents the workspace 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".

SEE ALSO

lscomp, mkbl, rmcomp