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 stream for a project


ProductCommand type
ClearCasecleartool subcommand
ClearCase LTcleartool subcommand



  • Create an integration stream in a project:
    mkstream –int·egration –in project-selector
    [ –c·omment comment | –cfi· le pname | –cq·uery
    | –cqe·ach | –nc·omment ]
    [ –bas·eline baseline-selector[,... ]]
    [ –pol·icy policy-keyword[,... ]]
    [ –npo·licy policy-keyword[,...]]
    [ –tar·get stream-selector ]
    [ stream-selector...]

  • Create a development stream in a project or a stream:
    mkstream {–in project-selector | stream-selector }
    [ –c·omment comment |–cfi·le pname | –cq·uery
    | –cqe·ach | –nc·omment ]
    [ –bas·eline baseline-selector[,... ]]
    [ –pol·icy policy-keyword[,... ]]
    [ –npo·licy policy-keyword[,...]]
    [ –reado·nly ]
    [ stream-selector...]


The mkstream command creates a stream for use with a UCM project. A stream consists of a name, a set of baselines that configure the stream, and a record of the set of activities associated with the stream.

There are two kinds of streams with UCM projects:

  • As a shared work area for integrating work from different sources. This is called the project's integration stream. Each project has exactly one integration stream.
  • As an isolated work area for use in code development. This is called a development stream. A project can have any number of development streams. A development stream can have child streams. There is no limitation on the number of nested levels of streams.

To create an integration stream, you must specify its project. Note that a project's integration stream must be present before a development stream can be created.

To create a development stream, you must specify a stream as its parent. Specifying a project is equivalent to specifying the project's integration stream. By default, the development stream delivers to the integration stream and rebases from recommended baselines of the integration stream. If you specify a development stream as its parent, the stream becomes the child of that development stream and delivers to and rebases from its parent.

Optionally, you can assign the stream a set of foundation baselines. Foundation baselines specify a stream's configuration by selecting the file and directory versions that are accessible in the stream.

Streams are accessed through views (see mkview –stream). A stream can have more than one view attached to it.

Stream Policies

You can set or unset policies for integration streams or development streams. Note that the project's policy settings take precedence over the stream's settings, unless –spolicy is used in the project to allow individual streams to control the policy. Table 9 describes these policies and lists the keywords used to set them. For more information about setting policies, see Managing Software Projects.

Table 9. UCM Stream Policies

Skip permission checking to allow any user to modify a stream with chstream or a baseline with chbl.POLICY_CHSTREAM_UNRESTRICTED
Require a development stream to be based on the current recommended baselines of its parent stream before it can deliver changes to the parent stream.POLICY_DELIVER_REQUIRE_REBASE
Do not allow delivery from a development stream that has checkouts.POLICY_DELIVER_NCO_DEVSTR
Allow a deliver operation from a stream in the same project to include changes from the stream's foundation baselines.POLICY_INTRAPROJECT_DELIVER _FOUNDATION_CHANGES
Allow a deliver operation from a stream in the same project to contain changes in components that are not included in the target stream's configuration. The changes in the missing components are not delivered.1POLICY_INTRAPROJECT_DELIVER _ALLOW_MISSING_TGTCOMPS
Allow a stream from a different project to deliver changes from its stream to this stream.POLICY_INTERPROJECT_DELIVER
Allow a deliver operation from a stream in a different project to include changes from the stream's foundation baselines. This policy is ignored if interproject delivery is disabled.POLICY_INTERPROJECT_DELIVER _FOUNDATION_CHANGES
Require a deliver operation from a stream in a different project to deliver changes in all components. This policy is ignored if interproject delivery is disabled.[a]POLICY_INTERPROJECT_DELIVER _REQUIRE_TGTCOMP_VISIBILITY
Allow a deliver operation from a stream in a different project to contain changes in components that are not modifiable in the target stream's configuration. The changes in the nonmodifiable components are not delivered. This policy is ignored if interproject delivery is disabled.POLICY_INTERPROJECT_DELIVER _ALLOW_NONMOD_TGTCOMPS

Defaults are different for intraproject and interproject deliver operations.

Read-Only Streams

To provide some users with read-only access to a set of baselines, you can create a special type of development stream with the option –readonly. You cannot deliver to or from this stream, but you can rebase it. Read-Only streams are not restricted by the normal rebase rules. In the view attached to a Read-Only stream, you can create DOs and other view-private files, but you cannot make any changes to components.

To create a read-only stream, your UCM VOBs and PVOBs must be at feature level 3 or greater.



No special identity required.


An error occurs if there are locks on any of the following objects: the UCM project VOB, the project, the parent stream (for development streams).


(Replicated VOBs only) No mastership restrictions.


Specifying the Stream's Role in the Project

Development stream.

Creates an integration stream, which is used for shared elements on a project and as a source for recording baselines. Each project can have exactly one integration stream.

Specifying the Stream's Parent


–in project-selector | stream-selector
Specifies the stream's parent. For an integration stream, it must be a project. For a development stream, it can be an integration stream or another development stream.

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

stream-selector is of the form [stream:]stream-name[@vob-selector], where vob-selector specifies the stream's project VOB.

Event Records and Comments

Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: –c). 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.

Stream Configuration

The stream's configuration is empty (that is, it has no foundation baselines).

–bas·eline baseline-selector[,... ]
Specifies one or more baselines to use as the stream's initial configuration—you can subsequently use rebase to change the stream's configuration.

baseline-selector is of the form [baseline:]baseline-name[@vob-selector], where vob-selector specifies the baseline's project VOB.

The following restrictions apply to the specified baselines:

  • For a development stream, all foundation baselines must be recommended baselines in its parent stream or baselines created in the project's integration stream.

  • For an integration stream, all foundation baselines must be either baselines created in other projects' integration streams, or be imported or initial baselines. You cannot use baselines created in development streams.

Setting Stream Policy


–pol·icy policy-keyword[,... ]
Enables the specified policy. See “Stream Policies”.

–npo·licy policy-keyword[,... ]
Disables the specified policy. See “Stream Policies”.

Setting the Default Deliver Target for Integration Streams Only


–tar·get stream-selector
Specify the default deliver stream of an integration stream. The target must be a stream in a different project and mastered in the local replica.

stream-selector is of the form [stream:]stream-name[@vob-selector] and wherevob-selector specifies the project VOB of a different project.

Creating a Read-Only Stream

A modifiable development stream.

Creates a Read-Only stream.

Specifying the Stream Name

A generated name.

stream-selector ...
Specifies a stream name.

You can specify the stream as a simple name or as an object selector of the form [stream:]name@vob-selector, where vob-selector specifies a project VOB (see the cleartool reference page). If you specify a simple name and the current directory is not a project VOB, this command assumes the stream resides in the project VOB that is associated with the current view. If the current directory is a project VOB, that project VOB is the context for identifying the stream.

The stream 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 development stream for the webo project.

    cmd-context mkstream –in webo_proj1@/vobs/webo_pvob \ chris_webo_dev@/vobs/webo_pvob
    Created stream "chris_webo_dev".

  • Create an integration stream.

    cmd-context mkstream -integration -in webo_proj1 integration@\webo_pvob \
    Created stream "integration".

  • Join a project. This example shows the sequence of commands to follow to join a UCM project.
    1. Find the project-selector for the project you want to join. For example:

      cmd-context lsproject –invob /vobs/webo_pvob 
      01-Mar-00.16:31:33  webo_proj1  ktessier   "webo_proj1"
      05-Jun-00.12:31:33  webo_proj2 ktessier   "webo_proj2"

    2. Create your development stream. For example:

      cmd-context mkstream -in webo_proj1@/vobs/webo_pvob –baseline BL3@/vobs/webo_pvob chris_webo_dev@/vobs/webo_pvob
      Created stream "chris_webo_dev".

    3. Create a view attached to your development stream:

      cmd-context mkview -stream chris_webo_dev@/vobs/webo_pvob \
      -tag chris_webo_dev /export/views/chris_webo_dev.vws

      Created view.
      Host-local path: venus:/export/views/chris_webo_dev.vws
      Global path: /net/venus/export/views/chris_webo_dev.vws
      It has the following rights:
      User : chris : rwx
      Group: user     : rwx
      Other:          : r-x
      Attached view to stream "chris_webo_dev".

    4. Create a view attached to the project's integration stream:

      cmd-context mkview -stream integration@/vobs/webo_pvob \
      -tag webo_integ /export/views/webo_integ.vws



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