15.1 What Does relocate Do?

The relocate command moves a designated set of elements from one VOB (the source VOB) to another VOB (the target VOB)-typically, a new VOB created for this purpose. The relocate command does all of the following:

• Moves elements from one VOB to another, including these:

• Data containers

• Event histories (some minor events are lost)

• Bidirectional hyperlinks (see also mkhlink)

• Related VOB database records

• The config records associated with checked-in derived objects (DOs)

• Creates VOB symbolic links from the source VOB to the target directory, generally preserving the source VOB's namespace for views bound to specific, preexisting versions of relocated elements.

• Copies metadata types associated with moved elements to the target VOB, as necessary (label, attribute, element, trigger, and hyperlink types).

• Leaves behind an event history for each relocated element-a remove element event in the source VOB, and a relocate event in the target VOB.

• Deletes nonversioned DOs and config records for DOs contained in relocated directories. (See the rmdo reference page.)

• Strands view-private files and DOs contained in relocated directories (recoverview -sync view-tag recovers these files to view-stg-dir\.s\lost+found).

• Creates a log of its activities-by default, in the file relocate.log.date-time in the current directory.

relocate does not do the following:

• Relocate elements when either the source or the destination VOB is a UCM VOB.

• Copy elements; it moves them. (relocate is not a backup tool.)

• Move view-private files and nonversioned DOs stored in relocated directories.

• Move elements to a new location in the same VOB. (Use cleartool mv for this purpose.)

NOTE: Because nonversioned DOs do not move with relocated directories (they are instead removed, as if by rmdo), any views that exist to help re-create past releases must rebuild any nonversioned DOs that were stored in relocated directories.