This command transfers the mastership of one or more objects from one replica to another. Only the current replica is affected immediately; other replicas are notified of the mastership transfers through the normal exchange of update packets.
To limit use of this command to a certain set of users, you can create triggers. For more information, see Managing Software Projects.
The chmaster command requires a view context. If you are not in a set view or working directory view on UNIX or in a view drive on Windows, you can specify a view on the command line, as shown in the following table. If you specify a dynamic view, it must be active on your host.
Note: A view you specify in the chmaster command takes precedence over your current set view, working directory view, or view drive.
Identities: For all UCM objects except baselines, no special identity is required. For baselines and all non-UCM objects, you must have one of the following identities:
Mastership: Your current replica must master the object. Using both –all and –obsolete_replica overrides this restriction, but you must not use the –obsolete_replica option except in special circumstances. (See the description of the –all option.)
Other: You cannot transfer mastership of a branch if either of these conditions exist:
Specify object-selector in one of the following forms:
Use the –override option only if the chmaster –stream command fails. With –override, chmaster attempts to transfer mastership of objects whose mastership was not transferred during the original invocation of the command. For more information, see the Administrator's Guide for Rational ClearCase MultiSite.
Caution: Incorrect use of the –obsolete_replica form of the command can lead to divergence among the replicas in a family.
Transfers to master-replica-selector mastership of all objects that are located in and mastered by the current replica. (The chmaster command determines the current replica by using the vob-selector that you specify as part of master-replica-selector. If you do not include a vob-selector, chmaster uses the replica containing the current working directory.)
If errors occur, the command continues, but after finishing, it reports that not all mastership changes succeeded.
With –long, chmaster lists the objects whose mastership is changing.
With –view, chmaster uses the specified view as the view context.
With –obsolete_replica, chmaster transfers mastership of all objects in the replica specified with old-replica-selector. Also, chmaster associates nonmastered checkouts with the new replica. Use this form of chmaster only when replica old-replica-selector is no longer available (for example, was deleted accidentally). Before entering this command, you must make sure that old-replica-selector masters itself or is mastered by the replica that it last updated. Then, enter the chmaster command at the last-updated replica. You must also send update packets from the last-updated replica to all other remaining replicas in the family. For more information, see the rmreplica reference page.
Note: You can use this command only at the replica that masters the branch type.
At the replica that masters the branch:
multitool describe –fmt "%[master]p\n" brtype:v3_bugfix
boston_hub@\dev
multitool chmaster boston_hub@\dev \dev\acc.c@@\main\v3_bugfix
Changed mastership of branch "\dev\acc.c@@\main\v3_bugfix"
to "boston_hub@\dev"
multitool syncreplica –export –fship boston_hub@\dev
Generating synchronization packet
c:\Program Files\Rational\ClearCase\var
\shipping\ms_ship\outgoing\sync_bangalore_19-Aug-02.09.33.02_3447_1
...
At the replica that masters the branch type:
Copyright© 2003 Rational Software. All Rights Reserved.