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 mktrigger command attaches a trigger to one or more elements or UCM objects. An attached trigger fires (executes the trigger action) when the element (or any of its versions) or the UCM object is involved in an operation specified in the trigger type definition. For example, if a trigger type is defined to fire on a checkin command, the attached trigger fires when the specified element is checked in. If a VOB operation causes multiple attached triggers to fire, the order of firing is undefined.
Note: A trigger type object, created with mktrtype –element must already exist in the VOBs containing the specified elements. Similarly, you use mktrtype –ucmobject to create a trigger type object in the project VOB containing the specified UCM objects before you can use this command.
Element Trigger Inheritance
By means of a trigger inheritance scheme, newly created elements (but not existing elements) inherit the triggers that are currently associated with their parent directory element. But a simple inherit-all-triggers strategy does not suit the needs of many sites. For example:
- You may not want some of a directory's triggers to propagate to its subtree.
- You may want some triggers to fire only for file elements, not for directory elements.
To enable such flexibility, each directory element has two independent lists of trigger types:
- Its attached list specifies triggers that fire on operations involving the directory element.
- Its inheritance list specifies triggers that elements created within the directory inherit.
By default, attaching a trigger to a directory element updates both lists:
cmd-context mktrigger trig_co proj
Added trigger "trig_co" to inheritance list of "proj".
Added trigger "trig_co" to attached list of "proj".
Each file element has only an attached list:
You can use the –ninherit and –nattach options to control exactly which triggers on a directory element are inherited. (And you can make adjustments using the –ninherit and –nattach options of the rmtrigger command.)
RESTRICTIONS
Identities
You must have one of the following identities:
Locks
An error occurs if one or more of these objects are locked: VOB (for an element trigger), project VOB (for a UCM object trigger), object type, object, trigger type.
Mastership
(Replicated VOBs only) No mastership restrictions.
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.
Attaching Element Triggers to an Entire Subdirectory Tree
- Default
- If a pname argument
names a directory element, the trigger is attached only to the element itself,
not to any of the existing elements within it.
- –r·ecurse
- Processes the entire subtree of each pname that
is a directory element (including pname itself).
UNIX VOB symbolic links are not traversed during the recursive descent into
the subtree.
Controlling Element Trigger Inheritance
- Default
- For a directory element, the specified
trigger type is placed both on the element's attached list and its inheritance
list. (For a file element, the trigger type is placed on its attached list,
which is its only trigger-related list.) The following options apply to directory
elements only.
- –nin·herit
- The trigger is placed on the element's
attached list, but not on its inheritance list. This option is useful when
you want to monitor operations on a directory, but not operations on the files
within the directory.
- –nat·tach
- The trigger is placed on the element's
inheritance list, but not on its attached list. This option is useful when
you want to monitor operations on the files within a directory, but not operations
on the directory itself.
Observing Type Restrictions
- Default
- If trigger-type-name is
defined with a restriction to one or more object types, mktrigger refuses
to process an object of another type.
- –f·orce
- Attaches a trigger to an object whose
type does not match the definition of the trigger type. Such a trigger does
not fire unless you change the object's type (chtype)
or you redefine the trigger type (mktrtype –replace).
Specifying the UCM Object
- Default
- None.
- ucm-object-selector ...
- The name of the UCM object. Specify ucm-object-selector in
the form [ucm-object-type:]type-name[@vob-selector].
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.