mkstream

Creates a stream for a UCM project

APPLICABILITY

SYNOPSIS

mkstream [ -c·omment comment | -cfi·le pname | -cq·uery | -cqe·ach | -nc·omment ]

[ -tit·le title ] [ -int·egration ]
[ -bas·eline baseline-selector[,... ]]
-in project-selector [ stream-selector...]

DESCRIPTION

The mkstream command creates a stream for use with a UCM project. A stream consists of a title, 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 active code development. This is called a development stream. A project can have any number of development streams.

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

Optionally, you can assign the stream a title and 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). Typically, a project's integration stream has a view for each developer, whereas each development stream has a single view.

A stream can have more than one view attached to it. In general, because project members work with a common integration stream, the stream has several views attached to it. A development stream usually has only one view attached to it.

RESTRICTIONS

Identities: No special identity required.

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

Mastership: There are no mastership requirements.

OPTIONS AND ARGUMENTS

EVENT RECORDS AND COMMENTS. Default: 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.

SPECIFYING THE STREAM TITLE. Default: A generated title.

-tit·le title

Assigns the specified title to all streams created.

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

-baseline 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] and vob is the baseline's UCM project VOB.

The following restrictions apply to the specified baselines:

• For a development stream, all foundation baseline must either be baselines created in the project's integration stream, or serve as the integration stream's foundation baselines.

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

SPECIFYING THE STREAM'S ROLE IN THE PROJECT. Default: Development stream.

-int·egration

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

SPECIFYING THE STREAM'S PROJECT. Default: None.

-in project-selector

Specifies the stream's project.

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

SPECIFYING THE STREAM NAME. Default: 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, then this command assumes the stream resides in the project VOB associated with the current view. If the current directory is a project VOB, then that project VOB is the context for identifying the stream.

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

cmd-context mkstream -title chris_webo_dev \
-in webo_proj1@/vobs/webo_pvob chris_webo_dev@/vobs/webo_pvob

Created stream "chris_webo_dev".

• Create an integration stream.

cmd-context mkstream -title integration -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 -title chris_webo_dev \
-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

SEE ALSO

chstream, lsstream, rebase, rmstream