SYNOPSIS
- chbl [ –c·omment comment |
–cfi·le comment-file-pname | –cq·uery
- | –cqe·ach | –nc·omment ]
{ [ [ –inc·remental | –fu·ll ]
[ –nre·curse ] ]
[ –level promotion-level ]
} baseline-selector ...
DESCRIPTION
The chbl command modifies
one or more baselines. You can modify a baseline's labeling status
or assign a new promotion level to a baseline.
For information about changing the baseline's
name, see rename.
Baseline Labels
Baselines can be unlabeled, incrementally labeled,
or fully labeled. Only labeled baselines can be used to configure streams
(see rebase and mkstream).
After they are applied, baseline labels cannot be moved.
Promotion Levels
Promotion levels must be defined in the baseline's
project VOB before they can be applied to baselines. For information about
promotion levels, see the setplevel reference
page.
The promotion levels available in a VOB can
be listed by running the describe command
on the UCM project VOB object.
RESTRICTIONS
Identities
You must have one
of the following identities:
- Project
VOB owner
- Baseline
owner
- Stream
owner
- root (UNIX)
- Member
of the ClearCase administrators group (ClearCase on Windows only)
- Local
administrator of the ClearCase LT server host (ClearCase LT on Windows
only)
Setting the stream policy POLICY_CHSTREAM_UNRESTRICTED skips the permission
checking. For more information on setting stream policies, see the mkstream and chstream reference
pages.
Locks
An error occurs if there
are locks on any of the following objects: the UCM project VOB, the baseline.
Mastership
(Replicated VOBs only)
Your current replica must master the baseline.
OPTIONS AND ARGUMENTS
Event Records and Comments
- Default
- Creates one or more event records,
with commenting controlled by your .clearcase_profile file
(default: –nc). 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.
Changing a Baseline's Labeling Status
- Default
- None.
- –inc·remental
- Changes the labeling status for an unlabeled
baseline to incremental. This option has no effect if the baseline is already
incrementally or fully labeled.
- –fu·ll
- Changes the labeling status for a baseline
from unlabeled or incremental to full. This option has no effect if the baseline
is already fully labeled. A chbl –full operation
may take a long time for components with many elements.
- –nre·curse
- By default, when –incremental and –full are
used on a composite baseline, the specified change is applied recursively
to its member baselines. The –nrecurse option
is used to prevent the default behavior. It causes the changes to apply only
to the composite baseline and not its members.
Assigning Promotion Levels
- Default
- No change in promotion level.
- –level promotion-level
- Sets the promotion level for the specified
baselines. The specified promotion level must be defined in the baseline's
project VOB. When used on a composite baseline, the change is not applied
recursively to its members.
Specifying the Baseline
- Default
- None.
- baseline-selector ...
- Specifies one or more baselines to modify.
baseline-selector is
of the form [baseline:]baseline-name[@vob-selector],
where vob-selector specifies the baseline's project
VOB.
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.
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.
- Change
an unlabeled baseline to be incrementally labeled. The baseline specifier
includes a VOB component, which must be the baseline's project VOB.
- Change
a baseline's promotion level and check the labeling status. The baseline specifier
includes a VOB component, which must be the baseline's project VOB.