Rational ClearCase Commands Referenceannotate
apropos
catcr
catcs
cc.icon
cc.magic
cd
chactivity
chbl
checkin
checkout
checkvob
chevent
chflevel
chfolder
chmaster
chpool
chproject
chstream
chtype
chview
clearaudit
clearbug
cleardescribe
cleardiffbl
cleardiff
clearexport_ccase
clearexport_cvs
clearexport_pvcs
clearexport_rcs
clearexport_sccs
clearexport_ssafe
clearfsimport
cleargetlog
clearhistory
clearimport
clearjoinproj
clearlicense
clearmake
clearmake.options
clearmrgman
clearprojexp
clearprompt
cleartool
clearviewupdate
clearvobadmin
comments
config_ccase
config_spec
cptype
credmap
creds
deliver
describe
diffbl
diffcr
diff
dospace
edcs
endview
env_ccase
events_ccase
export_mvfs
exports_ccase
file
find
findmerge
fmt_ccase
getcache
get
getlog
help
hostinfo
init_ccase
ln
lock
lsactivity
lsbl
lscheckout
lsclients
lscomp
lsdo
lsfolder
lshistory
ls
lslock
lsmaster
lspool
lsprivate
lsproject
lsregion
lsreplica
lssite
lsstgloc
lsstream
lstype
lsview
lsvob
lsvtree
makefile_aix
makefile_ccase
makefile_gnu
makefile_pmake
makefile_smake
makefile_sun
man
merge
mkactivity
mkattr
mkattype
mkbl
mkbranch
mkbrtype
mkcomp
mkdir
mkelem
mkeltype
mkfolder
mkhlink
mkhltype
mklabel
mklbtype
mkpool
mkproject
mkregion
mkstgloc
mkstream
mktag
mktrigger
mktrtype
mkview
mkvob
mount_ccase
mount
msdostext_mode
mvfslog
mvfsstorage
mvfstime
mvfsversion
mv
omake
pathnames_ccase
permissions
profile_ccase
promote_server
protect
protectvob
pwd
pwv
query_language
quit
rebase
recoverview
reformatview
reformatvob
register
relocate
rename
reqmaster
reserve
rgy_backup
rgy_check
rgy_passwd
rgy_switchover
rmactivity
rmattr
rmbl
rmbranch
rmcomp
rmdo
rmelem
rmfolder
rmhlink
rmlabel
rmmerge
rmname
rmpool
rmproject
rmregion
rmstgloc
rmstream
rmtag
rmtrigger
rmtype
rmver
rmview
rmvob
schedule
schemes
scrubber
setactivity
setcache
setcs
setplevel
setsite
setview
shell
snapshot.conf
softbench_ccase
space
startview
type_manager
umount
uncheckout
unlock
unregister
unreserve
update
version_selector
view_scrubber
vob_restore
vob_scrubber
vob_sidwalk
vob_snapshot
vob_snapshot_setup
wildcards_ccase
winkin
xclearcase
xcleardiff
xmldiffmrg
reqmaster
Sets access controls for mastership requests, or requests mastership of a branch or branch type
SYNOPSIS
DESCRIPTION
This command has three forms: two forms to configure access controls for mastership requests and one form to request mastership of a branch or branch type from the replica that masters the object. For more information, see the Administrator's Guide for Rational ClearCase MultiSite.
Setting Access Controls
To allow requests for mastership, the MultiSite administrator must set access controls at each replica:
- Add developers to the replica's access control list (ACL). Use the –acl option with –edit or –set to edit the ACL.
- Enable replica-level access. By default, replica-level access is not enabled. To enable it, use the –enable option.
Also, the type and the object must allow mastership requests. By default, type-level and object-level access are enabled. You can enable replica-level access, but deny requests for mastership of specific branches or branch types, or all branches of a specific type. Even if replica-level access is enabled, the reqmaster command fails if requests are denied at the type level or object level. Use the –deny option to deny requests at the type and object level.
Note: Mastership request settings are not replicated. The describe command and the Mastership tab in the Properties Browser on Windows display the current replica's settings.
Requesting Mastership of a Branch or Branch Type
This form of the reqmaster command contacts a sibling replica and requests that the replica transfer mastership to the current replica. You can also use reqmaster to display information about whether a mastership request will succeed.
If you specify multiple branches or branch types and the request fails for one or more items, reqmaster prints error messages for the failures and continues processing the other items.
Troubleshooting
If the reqmaster command fails, the error message indicates whether the failure occurred at the current replica or the sibling replica.
If the reqmaster command fails with the message can't get handle, reenter the command. If it continues to fail, ask the sibling replica's administrator to check the status of the VOB server.
When you request mastership, the reqmaster command may complete successfully, but the mastership is not transferred to your current replica. In this case, verify that the synchronization packet was sent from the sibling replica and that your current replica imported it successfully.
Errors that occur during the mastership request process, including errors occurring during the synchronization export, are written to the msadm log file. To view this log, use the cleartool getlog command or the ClearCase Administration Console (Windows).
For more information about error messages from the reqmaster command, see the Administrator's Guide for Rational ClearCase MultiSite.
RESTRICTIONS
Setting Access Controls
Identities
To set the ACL, you must have write permission on the ACL or have one of the following identities:
To enable mastership requests at the replica level, you must have one of the following identities:
Mastership
The replica must be self-mastering. For you to allow or deny mastership requests for a branch or branch type, your current replica must master the object.
Requesting Mastership of a Branch
Locks
An error occurs if one or more of these objects are locked (even if you are on the —nusers list): branch, branch type, VOB.
Other
An error occurs in any of the following cases:
- Mastership requests are denied at any of the following levels: replica, type object, object.
- There are checkouts on the branch (except for unreserved, nonmastered checkouts).
- You specify a branch associated with a stream.
- Your client host is running a later major version of ClearCase than the master replica's host.
Requesting Mastership of a Branch Type
Locks
An error occurs if one or more of these objects are lockedd (even if you are on the —nusers list): branch type, VOB, branch instances that have default mastership.
Other
An error occurs in any of the following cases:
- Mastership requests are denied at any of the following levels: replica, type object, any branch type instances with default mastership.
- There are checkouts on any branch type instances with default mastership (except for unreserved, nonmastered checkouts).
- You specify a branch type associated with a stream.
- Your client host is running a later major version of ClearCase than the master replica's host.
OPTIONS AND ARGUMENTS
Displaying or Setting Access Controls
- Default
- None. You must specify access controls.
Specifying –acl with no other option displays the ACL
for the current replica in the VOB family specified by vob-selector.
- –acl [ –edi·t | –set pname | –get ] vob-selector
- By default or with –get,
displays the ACL for the current replica in the VOB family specified by vob-selector.
With –edit, opens the ACL for the current replica in
the editor specified by (in order) the WINEDITOR (UNIX), VISUAL, or EDITOR environment
variable. With –set, uses the contents of pname to
set the ACL for the current replica.
Specify vob-selector in the form vob:pname-in-vob
- –enable vob-selector
- Allows mastership requests to be made to
the current replica in the VOB family specified by vob-selector.
- –dis·able vob-selector
- Denies all mastership requests made to
the current replica in the VOB family specified by vob-selector.
- { –deny | –allow } [ –inst·ances ] branch-type-selector ...
- Denies or allows requests for mastership
of the specified branch type. With –instances, denies
or allows requests for mastership of all branches of the specified type. Specify branch-type-selector in
the form brtype:type-name[@vob-selector]
- { –deny | –allow } branch-pname ...
- Denies or allows requests for mastership of the specified branch object. Specify branch-pname in the form file-pname@@branch. For example:
Requesting Mastership
- Default
- Sends a request for mastership to the master
replica of the object.
- –lis·t
- Displays information about whether a request
would succeed, but does not send a request for mastership.
- branch-pname
- Branch whose mastership you are requesting. For example:
- branch-type-selector
- Branch type whose mastership you are requesting. For example:
EXAMPLES
- Display
the ACL for the current replica in the VOB family /vobs/dev,
and then change it to give full access to ccadmin and
permission to request mastership to gail and paul.
multitool reqmaster –acl –get vob:/vobs/dev
# Replica boston_hub@/vobs/dev
# Request for Mastership ACL:
Everyone: Read
cat > /tmp/boston_hub_aclfile
# Replica boston_hub@/vobs/dev
# Request for Mastership ACL:
User:purpledoc.com/ccadmin Full
User:purpledoc/ccadmin Full
User:purpledoc.com/gail Change
User:purpledoc/gail Change
User:purpledoc.com/paul Change
User:purpledoc/paul Change
multitool reqmaster –acl –set /tmp/boston_hub_aclfile vob:/vobs/dev
multitool reqmaster –acl –get vob:/vobs/dev
# Replica boston_hub@/vobs/dev
# Request for Mastership ACL:
User:purpledoc.com/ccadmin Full
User:purpledoc/ccadmin Full
User:purpledoc.com/gail Change
User:purpledoc/gail Change
User:purpledoc.com/paul Change
User:purpledoc/paul Change - Allow
requests for mastership for all branches and branch types mastered by the
current replica in VOB family \tests, except for the
branch type v2.0_integration and all branches of
that type.
multitool reqmaster –enable vob:\tests
Requests for mastership enabled in the replica object for "vob:\tests"
multitool reqmaster –deny –instances brtype:v2.0_integration@vob:\tests
Requests for mastership denied for all instances of
"brtype:v2.0_integration@vob:\tests"
multitool reqmaster –deny brtype:v2.0_integration@vob:\tests
Requests for mastership denied for "brtype:v2.0_integration@vob:\tests" - Allow requests for mastership for all branches and branch types mastered by the current replica in VOB family \dev, except for the branch cmdsyn.m@@\main\v1.0_bugfix.
- Deny requests for mastership for all branches and branch types mastered by the current replica.
- Deny requests for mastership of the branch type v2.0_integration.
- Display mastership information about the branches include.h@@\main\integ and acc.c@@\main.
- Request mastership of the branch cmdsyn.m@@/main/v2.6_dev.
- Request mastership of the branch type v2.0_integration.