IPnom Home • Manuals • ClearCase

 Rational ClearCase Commands Reference

ClearCase Stuff:ClearCase LinksClearCase BooksClearCase Commands ReferenceClearCase ForumsClearCase News
Keyword Live Search (10 results max):
 Type in part of a ClearCase command in the search box.
Commands Index:


Moves elements and directory trees from one VOB to another


ProductCommand type
ClearCasecleartool subcommand
ClearCase LTcleartool subcommand



relocate [ –f·orce ] [ –qal·l ] [ –log log-pname ] [ –upd·ate ]
pname [ pname ... ] target-dir-pname


The relocate command moves elements, including directory trees, from one VOB to another. All related VOB database entries and data containers are moved to the target VOB. relocate preserves the “move from” VOB's namespace by substituting VOB symbolic links for moved elements.

The more common use of relocate involves splitting a piece from one VOB and moving it to a newly created VOB. However, you can move an arbitrary collection of elements from one VOB to a location in any other VOB. You cannot use relocate to move an element to a new location in the same VOB. Use cleartool mv for this purpose.

For a dynamic view, view-private files and nonversioned DOs are not relocated. If a relocated directory contains view-private files, they are stranded; DOs are removed.

Warning: The relocate command makes irreversible changes to at least two VOBs and their event histories. We recommend that you not use it frivolously or routinely for minor adjustments. Furthermore, you are advised to stop VOB update activity before and during a relocate operation.



You must have one of the following identities:

  • VOB owner (for both VOBs)
  • root (UNIX)
  • Member of the ClearCase administrators group (ClearCase on Windows)
  • Local administrator of the ClearCase LT server host (ClearCase LT on Windows)


An error occurs if one or more of these objects are locked in the source VOB: VOB, element. An error occurs if one or more of these objects are locked in the destination VOB: VOB, element, branch type, element type, label type, hyperlink type, attribute type.


(Replicated VOBs only) Your current replica must master any element to be relocated.


The following restrictions apply:

  • relocate cannot be used in a UCM VOB.
  • relocate cannot move checked-out elements. It fails during the selection phase if it finds any checked-out files among the ones it is going to move.
  • relocate may fail if there are restrictive triggers on checkout, checkin, and rmelem commands. Because relocate runs these commands, triggers on these operations are also executed. If these triggers cause relocate to fail, you must disable the triggers or remove them from those operations and run relocate again.


Suppressing the Confirmation Query

After displaying the relocate set, relocate asks you to confirm that these are the elements you want to relocate.

Suppresses the confirmation step.

Controlling Special Case Handling

For information about how the selection set is filtered, see the Administrator's Guide .

Prompts user to affirm or reject relocate's handling of each borderline element—one that is cataloged both in a directory being relocated and in a directory not being relocated. The default answer in an individual case depends on the element's visibility in the current view: yes if the view selects some version of the element; no otherwise.

If you reject these defaults, the result is nonfunctional links that you must repair. If a version of an element is visible in the current view and you indicate it is not to be relocated, the result is a bad link in the target VOB. If a version of an element is not visible in the view and you indicate that it is to be relocated, the result is a bad link in the source VOB.

Writing a Log File

relocate creates a log file in the current directory with the name relocate.log.date-time.

–log log-pname
Creates a relocate log file at location log-pname.

Relocating in Update Mode

relocate proceeds as described in the Administrator's Guide.

relocate runs in update mode.

Specifying Which Files to Relocate


pname ...
Specifies the elements to be relocated. A pname can be a file element, directory element, or VOB symbolic link.

Specifying a Target VOB and Directory

None. You must supply a target directory in a second VOB.

Specifies the directory in the target, or destination, VOB that will store the relocated elements. relocate checks out and modifies the version of this directory that is selected by your current view. The target directory must be in the same view as the source pathname (that is, you cannot specify a view-extended pathname for target-dir-pname).

On Windows, this pathname must be drive-relative:

\foo\bar m:\foo\bar
foo f:foo
..\foo g:..\foo


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.

  • Move subdirectory glib (and its one file, file.c) from /vobs/lib to the newly created VOB /vobs/gui. Query on borderline elements. To illustrate how relocate replaces element names with symbolic links in the source VOB, the example uses a relative pathname to specify the target VOB.

    After relocating glib, examine the RelocationVOB hyperlink added to /vobs/gui.

    % cd /vobs/lib
    cmd-context setcs –default 
     relocate -qall ./glib ../gui 
    Logfile is "relocate.log.09-Apr-99.14:11:37".
    Selected "glib".
    Selected "glib/file.c".
    Do you want to relocate these objects?  [no] 
    Checked out "." from version "/main/3".
    Checked out "/vobs/gui" from version "/main/0".
    Locking selected objects
    Locked "glib"
    Locked "glib/file.c"
    Recreating selected objects
    Created "glib"
    updated branch "/main"
        updated version "/main/0"
            created version "/main/1"
            Created "glib/file.c"
        updated branch "/main"
            updated version "/main/0"
            created version "/main/1"
    Cataloging new objects
        cataloged symbolic link "/vobs/lib/glib/.@@/main/2/glib" -> 
        cataloged symbolic link "/vobs/lib/glib/.@@/main/3/glib" -> 
        cataloged "/vobs/lib/.@@/main/CHECKEDOUT.32/glib"
        cataloged symbolic link "/vobs/lib/glib/.@@/main/1/file.c" -> 
        cataloged symbolic link "/vobs/lib/glib/.@@/main/2/file.c" -> 
        cataloged "/vobs/gui/glib@@/main/1/file.c"
    Removing original objects
        removed "glib/file.c"
        removed "glib"
    Checked in "/vobs/lib/." version "/main/4".
    Checked in "/vobs/gui/." version "/main/1".

    cmd-context  describe vob:/vobs/gui 
    versioned object base "/vobs/gui"
      created 09-Apr-99.13:50:16 by CCase Admin (clearadm.sys@propane)
      "relocate target for former directory /vobs/lib/gui"
      VOB storage host:pathname "propane:/usr1/vobstore/gui.vbs"
      VOB storage global pathname "/net/propane/usr1/vobstore/gui.vbs"
      VOB ownership:
        owner clearadm
        group sys
         RelocationVOB@33@/vobs/gui vob:/vobs/gui -> vob:/vobs/lib/




ln, mkvob, mv



ClearCase Links • ClearCase Books • ClearCase Commands Reference • ClearCase Forums • ClearCase News