chtype
Changes the type of an element
or renames a branch
SYNOPSIS
- chtype [ –c·omment comment | –cfi·le comment-file-pname
- | –cq·uery | –cqe·ach
| –nc·omment ]
[ –f·orce ]
[ –pna·me ] type-selector
{ pname ... | object-selector ...
}
DESCRIPTION
The chtype command changes
the element type of one or more existing elements or renames one or more existing
branches. These operations involve changing the type object associated with
the element or branch.
RESTRICTIONS
Identities
For an element,
you must have one of the following identities:
- Element
owner
- VOB
owner
- root (UNIX)
- Member
of the ClearCase administrators group (ClearCase on Windows)
- Local
administrator of the ClearCase LT server host (ClearCase LT on Windows)
For a branch, you must have one of the following
identities:
- Branch
creator
- Element
owner
- VOB
owner
- root (UNIX)
- Member
of the ClearCase administrators group (ClearCase on Windows)
- Local
administrator of the ClearCase LT server host (ClearCase LT on Windows)
Locks
An error occurs if one
or more of these objects are locked:
Mastership
(Replicated VOBs
only) For an element, your current replica must master the element. For a
branch, your current replica must master the new branch type and the branch
you are changing.
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.
Confirmation Step
- Default
- chtype prompts for confirmation
if changing an element's type will change the way its versions are stored
in the VOB storage pool.
- –f·orce
- Suppresses the confirmation step.
Specifying the New Type
- Default
- None.
- type-selector
- An element type or branch type. The type
must already exist. (Exception: If you specify a global element type or global
branch type, a local copy of the type is created if one does not already exist.)
Specify type-selector in the form [type-kind:]type-name[@vob-selector].
Specifying the Elements, Branches, or Activities
- Default
- None.
- [ –pna·me ] pname ...
- One or more pathnames, each of which specifies
a file or directory element. A standard pathname is valid; you need not append
the extended naming symbol. That is, specifying a version is equivalent to
specifying its element. Specifying a branch (for example, foo.c@@/main/bugfix)
causes an error.
If pname has the
form of an object selector (for example, eltype:fl2),
you must use the –pname option to indicate that it
is a pathname. The –pname option must precede nonoption
arguments. For example:
cmd-context chtype –nc –force –pname
eltype:c_source eltype:fl2
- object-selector ...
- One or more extended pathnames, each of which
specifies a particular branch of an element. For example:
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.
- Convert
an element to type file.
- Change
branch rel2_bugfix to branch maintenance,
providing a comment.
- Convert
an archive library to compressed_file format, suppressing
confirmation prompts.