mkstream

Creates a stream for a UCM product

APPLICABILITY

ClearCase UCM (cleartool subcommand)

SYNOPSIS

mkstream [ -c comment | -cfile pname | -cq | -cqe | -nc ]

[ -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 element 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. 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 on Foundation Baselines for a Stream

The following restrictions apply to the list of baselines selected by a stream:

• Development streams can only specify baselines produced in its project's integration stream or baselines currently selected by the project's integration stream.
• Integration streams can only specify baselines in other projects' integration streams.

PERMISSIONS AND LOCKS

Permissions Checking: None.

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 CUSTOMIZING COMMENT HANDLING in 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. Default:The stream has no baselines. (You can use rebase later to populate a stream.)

-baseline baseline-selector[,... ]

Specifies one or more baselines to use as the stream's initial configuration.

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

STREAM TITLE.

-tit·le title

Assigns a title to a stream.

SPECIFYING THE STREAM'S PURPOSE. Default: The stream is created for use as a 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.

By default, mkstream creates development streams, which provide isolated work areas within a project.

-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.

stream-selector ...

Specifies a stream. If no stream-selector is specified, a name is generated automatically.

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

EXAMPLES

Examples including 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 command interpreter prompt. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.

• Create a development stream for the y2k project.

cmd-context mkstream -in project:y2k@/vobs/plibvob

• Create an integration stream.

cmd-context mkstream -title "Deliver your changes here" -integration -in Java_Parser_Project_28174 java_int@\vobs\core_projects

Created stream "java_int".

• 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 -long -invob\vobs\components

1. Create your development stream and view. For example:

cmd-context mkstream -title pat_v1.4_cropcircle -in cropcircle -baseline BL3 pat_v1.4_cropcircle@\vobs\mypvob

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

cmd-context mkview -tag pat_v1.4_cropcircle -stream pat_v1.4_cropcircle
-snapshot vws ~\work\pat_v1.4

SEE ALSO

chstream, lsstream, rebase, rmstream