DevOps Code ClearCase commands related to DevOps Code ClearCase MultiSite
This topic lists the DevOps Code ClearCase® commands that pertain to DevOps Code ClearCase MultiSite, providing a short description of each one.
The DevOps Code ClearCase commands listed in the following table manage or display DevOps Code ClearCase MultiSite information.
| Command | Description |
|---|---|
| checkout –unreserved –nmaster –srfm | –nmaster performs a nonmastered checkout, which is an unreserved checkout on a branch not mastered by your current replica; –srfm initiates a synchronous request for mastership as part of the checkout operation |
| lscheckout –areplicas | Lists checked-out versions in all replicas of a VOB (Default: lists your current replica’s checkouts) |
| lsvob –long | Displays the VOB registry attribute of "replicated" if the VOB is replicated |
| mkattype –shared mkhltype –shared mklbtype –shared | Creates a shared type object. |
| mkelem –master mkdir –master | Assigns mastership of the main branch of the element to the replica in which you create the element. Also, if your config spec contains mkbranch rules and you do not specify the –nco option, mkelem or mkdir assigns mastership of these branches to the replica in which you create the element. |
| vob_scrubber | Scrubs oplog entries and export_sync records |
In general, all DevOps Code ClearCase commands obey DevOps Code ClearCase MultiSite mastership restrictions in a replicated VOB. In addition, the following commands work differently in replicated VOBs:
describe Lists the master replica of an object. For replicas, branch types, and branches, lists the mastership request setting.
describe vob:pname-in-vob Lists the replica name and the VOB family feature level.
You can change a directory only in the master replica of the branch on which the directory is checked out. Changes to directories include:
- Creating a VOB hard link or VOB symbolic link (ln)
- Creating a new element (mkelem)
- Removing a reference to an element or VOB symbolic link (rmname)
mkobject type –replace If a type object is shared, you cannot change its instance restrictions. For example, you cannot replace a one-per-element branch type with a one-per-branch branch type.
mkeltype –replace You cannot change the definition of an element type in a replicated VOB.
rmtype eltype:type-name You cannot delete an element type in a replicated VOB.