chmaster

chmaster

[ –c/omment comment | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment ] { master-replica-selector object-selector ... | [ –pname ] master-replica-selector branch-or-element-pname ... | –str/eam [ –ove/rride ] master-replica-selector stream-selector ... | –def/ault [ –pname ] branch-pname ... | –def/ault brtype-selector ... | –all [ –obsolete_replica old-replica-selector ] [ –l/ong ] [ –vie/w view-tag ] master-replica-selector }

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 the Help.

The chmaster command requires a view context. If you are not in a set view or working directory view on Linux® and the UNIX system 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.

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:

• Object creator (except for replicas)
• Object owner (except for replicas)
• VOB owner
• root (Linux and the UNIX system)
• Member of the VersionVault administrators group (Windows)

Locks: Restrictions depend on the kind of object:

Object whose mastership is changing	Locks on these objects cause the chmaster command to fail
Element	Element, element type, VOB
Branch	Branch, branch type, VOB.
Type object	Type object, VOB
Hyperlink	Hyperlink type, VOB
Baseline	Baseline, VOB, replica, components associated with the baseline
Stream	Stream, activity
Component	Component, VOB, replica
Policy	Policy, VOB
Rolemap	Rolemap, VOB

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:

• There are reserved checkouts on that branch.
• There are unreserved checkouts on that branch made without the –nmaster option.

Exceptions to restrictions on the transfer of branch type mastership

• At replica boston_hub, transfer mastership of label type V1.0_BUGFIX to the sanfran_hub replica.

  
  
  multitool chmaster sanfran_hub lbtype:V1.0_BUGFIX
  
  
  
  Changed mastership of "V1.0_BUGFIX" to "sanfran_hub"
  
  

• At replica sanfran_hub, transfer mastership of element list.c to the sydney replica.

  
  
  multitool chmaster sydney list.c@@
  
  
  
  Changed mastership of "list.c" to "sydney"
  
  

• At replica sanfran_hub, transfer mastership of the stream v2.1.bl5 and its associated objects to the boston_hub replica.

  
  
  multitool chmaster –stream boston_hub@/vobs/dev
  stream:v2.1.bl5@/vobs/dev
  
  

• At the replica that is the master of replica sanfran_hub, make sanfran_hub self-mastering.

  
  
  multitool chmaster sanfran_hub replica:sanfran_hub
  
  
  
  Changed mastership of "sanfran_hub" to "sanfran_hub"
  
  

• At replica buenosaires, transfer mastership of branch cache.c@@/main/v3_dev to boston_hub.

  
  
  multitool chmaster boston_hub cache.c@@/main/v3_dev
  
  
  
  Changed mastership of branch "/vobs/dev/cache.c@@/main/v3_dev" to
  "boston_hub"
  
  

• For all objects mastered by the current replica, transfer mastership to sanfran_hub.

  
  
  multitool chmaster –all sanfran_hub
  
  
  
  Changed mastership of all objects
  
  

• Same as the preceding example, but have chmaster list each object whose mastership is changing, and specify a view context.

  
  
  multitool chmaster –all –long sanfran_hub@/view/jtg/vobs/dev
  
  
  
  Changed mastership of branch type sydney_main
  Changed mastership of label type SYDNEY_V2.0
  Changed mastership of replica sydney
  Changed mastership of all objects
  
  

• Return mastership of a branch to the replica that masters the branch type and then remove its explicit mastership.

  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\HCL\CCM\VersionVault\var\shipping\ms_ship\outgoing
  \sync_bangalore_19-Aug-02.09.33.02_3447_1
  ...
  
  

  At the replica that masters the branch type:

  
  
  multitool syncreplica –import –receive
  
  
  
  Applied sync. packet
  /var/adm/hcl/versionvault/shipping/ms_ship/incoming/
  sync_bangalore_19-Aug-02.09.33.02_3447_1
  to VOB /net/minuteman/vobstg/dev.vbs
  
  
  multitool chmaster –default brtype:v3_bugfix
  
  
  
  Changed mastership of branch type "v3_bugfix" to "default"
  
  

reqmaster, syncreplica.