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
DESCRIPTION
The mkcomp command creates a component. The scope of a UCM project is declared in terms of components. A project must contain at least one component, and it can contain multiple components. Projects can share components.
An ordinary component groups directory and file elements. The directory and file elements of a component are stored in a VOB. The component object is stored in a project VOB (PVOB). You organize a component's directory and file elements into a directory tree in a VOB. A component's root directory must be the VOB's root directory or one level beneath it. A component includes all directory and file elements under its root directory. To store multiple components in a VOB, make each component's root directory one level beneath the VOB's root directory. If you make a component at the VOB's root directory, that VOB can never contain more than that one component.
An initial baseline is created when you create a component. This baseline selects the /main/0 version of the component's root directory. Use this as a starting point for making changes to the component.
You can use the –nroot option to create a special type of component that holds only composite baselines and no file elements.
Elements cannot be moved from one component to another. Therefore, you cannot reorganize a component into multiple components.
A component cannot be renamed if its root directory is one level beneath the VOB's root directory .
When converting a subdirectory of an existing non-UCM VOB into a component, mkcomp checks each element recursively to see whether any are already associated with a different component. (This may occur when an element has hard links outside the component.) If any are found, the command fails. Remove such hard links with rmname and replace them with a symbolic link before proceeding.
RESTRICTIONS
Identities
You must have one of the following identities:
OPTIONS AND ARGUMENTS
Event Records and Comments
- Default
- Creates one or more event records,
with commenting controlled by your .clearcase_profile file
(default: –nc). See the comments reference
page. Comments can be edited with chevent.
- –c·omment comment | –cfi·le comment-file-pname |–cq·uery | –cqe·ach | –nc·omment
- Overrides the default with the option you specify. See the comments reference
page.
The comment is stored in the creation event of the component object.
Specifying What Type of Component to Create
- –roo·t root-dir-pname
- Specifies a component to be created to group directories and elements
and the root directory pathname for this component. To create one component
per VOB, the root-dir-pname must be the root directory
of a VOB. To create multiple components per VOB, the root-dir-pname must
be one level beneath the VOB's root directory. If the specified subdirectory
does not already exist, it is created by the mkcomp operation.
- –nro·ot
- Specifies a component to be created to hold
only composite baselines. This type of component does not contain directories
or file elements.
Specifying a Component Selector
- component-selector
- Identifies the component.
component-selector is of the form [component:]component-name[@vob-selector] where vob is the component's UCM project VOB.
If no vob-selector is given, the component is created in the project VOB if it contains the current working directory; otherwise, the component is not created.
The component name must be unique within the PVOB. All UCM objects share the same namespace. You'll get an error if the name you provide collides with the name of an existing UCM object, for example, a project.
EXAMPLES
The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.