rename

Assigns a new name to an existing ClearCase object.

APPLICABILITY

ClearCase (cleartool subcommand), Attache (command), MultiSite (multitool subcommand)

SYNOPSIS

rename [ -c·omment comment | -cfi·le comment-file-pname |-cq·uery | -cqe·ach | -nc·omment ]

{ old-object-selector new-object-selector | -gen·erate old-object-selector }

DESCRIPTION

NOTE: To move or change the name of a ClearCase file or directory element, use the mv command.

The rename command renames a ClearCase or MultiSite object-for example, a VOB storage pool, a replica, or a type object such as an activity type.

If you are renaming a pool, no data container in the pool is affected.

If you are renaming a replica, the name change is propagated to other replicas, through the standard synchronization mechanism. This command is valid only at the replica that masters the VOB-replica object being renamed.

If you are renaming a type object, all instances of the type object, throughout the VOB, are also renamed. If the type object is global, all local copies of the type object are renamed. For example, if you rename a branch type from bugfix to rel1.3_fixes, all existing bugfix branches are also renamed to rel1.3_fixes. (For more information about global type renaming, see Administering ClearCase.)

RESTRICTION: A VOB cannot contain a branch type and a label type with the same name.

NOTE: Do not use this command to rename an instance of a type, for example to rename a particular branch of a particular element. For that purpose, use chtype.

PERMISSIONS AND LOCKS

Permissions Checking: For each object processed, you must be one of the following: replica creator (for renaming a replica only), object owner, VOB owner, member of the ClearCase group. See the permissions reference page.

Locks: An error occurs if any of the following objects are locked: VOB, object.

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 CUSTOMIZING COMMENT HANDLING in 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 OLD AND NEW NAMES. Default: None.

old-object-selector
new-object-selector

The name of an existing object and a new name for it. Specify object-selector in one of the following forms:

vob-selector

vob:pname-in-vob

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). It cannot be the pathname of the VOB storage directory.

attribute-type-selector

attype:type-name[@vob-selector]

branch-type-selector

brtype:type-name[@vob-selector]

element-type-selector

eltype:type-name[@vob-selector]

hyperlink-type-selector

hltype:type-name[@vob-selector]

label-type-selector

lbtype:type-name[@vob-selector]

trigger-type-selector

trtype:type-name[@vob-selector]

pool-selector

pool:pool-name[@vob-selector]

hlink-selector

hlink:hlink-id[@vob-selector]

oid-obj-selector

oid:object-oid[@vob-selector]

The following object selector is valid only if you use MultiSite:

replica-selector

replica:replica-name[@vob-selector]

The following object selectors apply to UCM:

activity-selector

activity:actvity-name[@vob-selector]

baseline-selector

baseline:baseline-name[@vob-selector]

component-selector

component:component-name[@vob-selector]

folder-selector

folder:folder-name[@vob-selector]

project-selector

project:project-name[@vob-selector]

stream-selector

stream:stream-name[@vob-selector]

For more information about object selectors, see the cleartool reference page.

EXAMPLES

Examples including 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 command interpreter prompt. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.

cmd-context rename -c "make pool name clearer" pool:c_pool pool:c_source_pool
Renamed pool from "c_pool" to "c_source_pool".
cmd-context lspool -short
c_source_pool
cdft
ddft
do1
my_ctpool
sdft
cmd-context rename pool:do1 pool:do_staged
Renamed pool from "do1" to "do_staged".
cmd-context lsvtree -short util.c
util.c@@\main\1
util.c@@\main\rel2_bugfix
util.c@@\main\rel2_bugfix\1
util.c@@\main\3
cmd-context rename brtype:rel2_bugfix brtype:r2_maint
Renamed type from "rel2_bugfix" to "r2_maint".
cmd-context lsvtree -short util.c
util.c@@\main\1
util.c@@\main\r2_maint
util.c@@\main\r2_maint\1
util.c@@\main\3
cmd-context rename eltype:text_file eltype:source_file
cleartool: Warning: Renaming a predefined object!
Renamed type from "text_file" to "source_file".
cmd-context describe -aattr TESTED msg.c
msg.c@@\main\3
Attributes:
TESTED = "TRUE"
cmd-context rename attype:TESTED attype:QAed
Renamed type from "TESTED" to "QAed".
cmd-context describe -aattr QAed msg.c
msg.c@@\main\3
Attributes:
QAed = "TRUE"
cmd-context rename replica:paris paris_louvre
Renamed replica "paris" to "paris_louvre".

SEE ALSO

chactivity, chchkpt, chevent, chpool, chtype, describe, lspool, lstype, mkpool, mkreplica (in the ClearCase MultiSite Manual), rmpool, rmtype



Feedback on the documentation in this site? We welcome any comments!
Copyright © 1999 by Rational Software Corporation. All rights reserved.