Changes the type of an element or renames a branch
Product | Command Type |
---|---|
ClearCase | cleartool subcommand |
ClearCase LT | cleartool subcommand |
Attache | command |
Platform |
---|
UNIX |
Windows |
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.
For an element, you must have one of the following identities:
Element owner
VOB owner
root (UNIX)
Member of the ClearCase 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 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:
Element: | VOB, element type, element, pool |
Branch: | VOB, element type, element, branch type, branch. |
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.
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.
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.
SPECIFYING THE NEW TYPE. Default: None.
type-kind | One of | |
type-name | Name of the type object | |
vob-selector | Object-selector for a VOB, in the form [vob:]pname-in-vob. The pname-in-vob can be the pathname of the VOB-tag (whether or not the VOB is mounted) or of any file-system object within the VOB (if the VOB is mounted) |
SPECIFYING THE ELEMENTS, BRANCHES, OR ACTIVITIES. Default: None.
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.
Convert an element to type file.
cmd-context chtype file hello.c
Change version manager and reconstruct all versions for "hello.c"? [no]
yes
Changed type of element "hello.c" to "file".
Change branch rel2_bugfix to branch maintenance, providing a comment.
cmd-context chtype -c "rel2_bugfix no longer in use" maintenance util.c@@\main\rel2_bugfix
Changed type of branch "util.c@@\main\rel2_bugfix" to "maintenance".
Convert an archive library to compressed_file format, suppressing confirmation prompts.
cmd-context chtype -force compressed_file libutil.a
Changed type of element "libutil.a" to "compressed_file".
cc.magic, mkbrtype, mkelem, mkeltype, profile_ccase, rename
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |