mkstream

You can create an integration stream template for each project VOB. You must have administrator privileges and create the template from the project VOB directory. With an integration stream template you can select policies that are applied to all subsequent integration streams created in the project VOB. Use of this feature ensures consistent policy enablement across projects.

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. UCM Stream Policies describes these policies and lists the keywords used to set them. For more information about setting policies, see the Help.

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.

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 exactly one integration stream.

Default

None.

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

Default

Creates one or more event records, with commenting controlled by your .versionvault_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.

Default

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, a foundation baseline must be labeled or the initial baseline of a component.
• For an integration stream, all foundation baselines must be either baselines created in other projects' integration streams, or be imported or initial baselines.

Default

None.

–pol/icy policy-keyword[,... ]

Enables the specified policy. See Stream policies.

–npo/licy policy-keyword[,... ]

Disables the specified policy. See Stream policies.

Default

None.

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

Creates a view and attaches it to the new stream.

Specifies a name for the view, in the form of a simple filename. For dynamic views, this name appears in the local host's file system as a subdirectory of /view, the viewroot directorydynamic-views root directory (by default, M:\). For example, the dynamic view experiment would appear as /view/experiment M:\experiment.

Adds a comment to the view-tag's entry in the view_tag registry file. Use lsview -long, or the graphical view-tag browser, to display the tag comment.

Default

None.

-deliver_to integration-view-tag

Specifies a view attached to the deliver target stream in the same project or in a different project.

Default

A modifiable development stream.

–reado/nly

Creates a Read-Only stream.

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, 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 will get an error if the name you provide collides with the name of an existing UCM object, for example, a project.

For testing purposes, you can create a modifiable component that the parent project would otherwise define as nonmodifiable. Refer to the chstream reference page for information on the use of such components and the restrictions on their use.

–amodcomp

Makes the specified component modifiable by creating a Base VersionVault (that is, non-UCM) branch named stream_name_nonmod and associating it with the stream-modifiable component. Checkout operations are performed on the Base VersionVault branch and changes made on that branch are not included in any UCM activity change set. You cannot change the modifiability of a component in these circumstances:

• The project already defines the component as modifiable.
• The component is an integration stream component.

component-selector

Identifies the component that is to be made modifiable or nonmodifiable.

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.

The component name must be unique within the PVOB; otherwise, an error results.