rmtype
Removes a type object from a
VOB
SYNOPSIS
- rmtype [ –ign·ore ]
[ –rma·ll [ –f·orce ]
]
- [ –c·omment comment | –cfi·le comment-file-pname |–cq·uery | –cqe·ach
| –nc·omment ] type-selector ...
DESCRIPTION
The rmtype command removes
one or more type objects from a VOB.
The file vista.tjf records
updates to the VOB that result from rmtype operations. vista.tjf can
grow very large. For information about limiting its size, read about the file db.conf in
the config_ccase reference page.
RESTRICTIONS
Identities
You must have one
of the following identities:
- Type
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: VOB, type.
Mastership
(Replicated VOBs
only) Your current replica must master the type.
Other
You cannot remove a type
object if there are any instances of that type. For example, if any version
of any element is labeled REL1, you cannot remove
the REL1 label type. You can bypass this restriction
by specifying the –rmall option.
You cannot remove an element type from a
replicated VOB.
OPTIONS AND ARGUMENTS
Removing Instances of the Type
- Default
- If there are any instances of a specified
type object, rmtype does not remove the type object.
- –rma·ll
- Removes all instances of a type, and then
proceeds to remove the type object itself. If the type object is a global
type or is a local copy of a global type, rmtype removes
the global type and all local copies of the type.
Caution: If the rmtype –rmall command
fails for any reason, you must address the causes of the failure and enter
the command again. You must persist until the command completes successfully
and the type is removed. Failure to do so results in inconsistent metadata.
Caution: This option potentially destroys
a great deal of data.
- –f·orce (for use with –rmall only)
- By default, rmtype prompts
for confirmation when you use the –rmall option to
request removal of all instances of a type. The –force option
suppresses the confirmation step.
- –ign·ore (for use with
trigger types only)
- Removes a trigger type even if a previously
defined preoperation trigger would otherwise prevent it from being removed.
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.
Specifying the Type Objects to Be Removed
- Default
- Removes types from the VOB that contains
the current working directory unless you specify another VOB with the @vob-selector suffix.
- type-selector ...
- One or more names of existing type objects,
of the specified kind. Specify type-selector in
the form type-kind:type-name[@vob-selector]
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.
- Delete
the branch type patch3.
- Delete
the attribute type QA_date in the VOB \tests.
- Delete
all branches of type expmnt3 (along with all the
versions on those branches and any subbranches); then delete the expmnt3 branch
type itself.
- Delete
the hyperlink type design_doc.
- Remove
all instances of the label type REL2; then delete
the label type.
- Delete
the trigger type trig1. Use the –ignore option
to ensure that the command executes without interference from a previously
defined trigger.
SEE ALSO
chevent, cleartool, comments, config_ccase, describe, lshistory, lstype, mkattype, mkbrtype, mkeltype, mkhltype, mklbtype, mktrtype, rename