Rational ClearCase Commands Reference

Initial Baseline

When you create an ordinary component (that is, one that contains directories and elements), it includes an initial baseline whose name is of the form component-name_INITIAL. This baseline selects the /main/0 version of the component's root directory and serves as a starting point for successive baselines of the component.

Creating a Baseline for an Unmodified Component

Use the –identical option to create a new baseline for a component that has not been modified. This can be useful in working with several components. You can create new baselines for a set of components regardless of whether they have been modified.

Creating Baselines That Include a Set of Activities

By default, all activities modified since the last baseline was made are captured in new baselines. You can select a subset of activities for inclusion in the baseline. If there are dependencies between the change sets of activities, you may not be able to include only the activity you want; you'll need to include the activities it depends on as well.

A single baseline is created if the selected activities are part of the same component. If an activity modifies more than one component, a new baseline is created for each component it modifies.

Creating a New Composite Baseline with Existing Dependency Relationships

The operation of creating a new composite baseline is recursive. That is, the operation first creates baselines of its member components and then creates dependency references to those baselines in the composite. The result is a composite baseline that retains the dependency structure of its predecessor.

Creating or Changing Dependency Relationships for a Composite Baseline

You can create or change the dependency relationships for a composite baseline by using the –adepends_on or –ddepends_on options. When a dependency reference to a component is added, a baseline of that component is made, if necessary. These operations apply only to direct members of a composite baseline and do not affect indirect members in a baseline hierarchy. A dropped component can still have a baseline that is lower in the dependency hierarchy.

Note: To change the existing dependency relationships, you must create a new composite baseline. You cannot change the relationships of an existing baseline with chbl.

Creating a Baseline by Importing a Label

You can recognize a VOB as a component with the mkcomp command. When you do this, the VOB is given an initial baseline that selects the /main/0 version of the component root directory. However, this baseline does not automatically enable access to files and directories that are already in the VOB.

You can create a new baseline that corresponds to a set of labeled versions in the VOB or one of the VOB's components. To do this, use the –import option. The mkbl command creates a baseline that selects the labeled versions, making them accessible to the UCM project.

Before creating the baseline, be sure that the label is unlocked and ordinary (not global) and that labeled elements are checked in. Once the baseline is created, the label cannot be moved or removed except by privileged users. Be certain the label selects some version of all visible elements.

Baseline Names

By default, baseline identifiers are made up of two parts: a user-specifiable basename and a generated, unique numeric extension. However, if you have defined a baseline name template for your project, baseline names will be created using that template. For information about defining a baseline name template, see mkproject and chproject.

The exceptions to the above rule are initial baselines and baselines created from a label. The name of an initial baseline is of the form component-name_INITIAL. When you create a baseline by importing a label, the basename is derived from the label's type selector. For example, the label-type selector REL1@/vobs/baz generates a baseline basename of REL1 whose scope is the baz component.

Baseline Labels

You can choose whether versions of the baseline are to be labeled when the baseline is created. Baselines can be unlabeled, incrementally labeled, or fully labeled. After they are applied, baseline labels cannot be moved.

All baselines record a component's current configuration in a stream, but only labeled baselines can be used to configure other streams (by means of rebase or mkstream).

Choose a labeling scheme that suits your project's structure. Incremental baselines typically can be created more quickly than full baselines.

These options control labeling during baseline creation:

Each time when new baselines are made, mkbl checks to see whether any latest baselines are unlabeled. If any are found, mkbl issues a warning and displays the unlabeled baselines. You can change the labeling status for a baseline with the chbl command.

Promotion Levels

Baselines are marked with a promotion level that signifies the quality of the baseline. When created, a project VOB is assigned an ordered set of promotion levels, one of which is designated the default promotion level, which is the level assigned to new baselines when they are created.

For more information, see setplevel.

Identities

No special identity required.

Locks

An error is generated if there are locks on any of the following objects: the UCM project VOB, the component, the containing stream; and if you are importing a label type, the label type being imported.

Mastership

(Replicated VOBs only) Your current replica must master the stream where you make the baseline. When you create an imported baseline from a pre-UCM label, your current replica must master the component and label type.

Event Records and Comments

Specifying the Components

Specifying the Activities

Selecting Labeling Behavior

Specifying the View and Stream

Specifying the Baseline Root

Creating or Changing Dependency Relationships for a Composite Baseline

Specifying a Label to Import