This portion of the command_key_definition determines if the cleartool command or command group that is definition applies to. The pulldown is limited to only it's valid values.
NOTE: For certain operations that can appear as element operations or type operations, the operation might have multiple definition options (i.e. chevent, chmaster and lock) such that:
Example Operation | Would apply to... |
---|---|
lock_ele | only element definitions |
lock_type | only and type definitions |
lock | both element definitions and type definitions |
The Commands and command groups match the ClearCase command groups defined as per cleartool man mktrtype with an additional "mv" command.
Command Group | Contains... |
---|---|
MODIFY_ELE | checkout reserve uncheckout unreserve mv MODIFY_DATA MODIFY_MD |
MODIFY_DATA | checkin chtype lnname lock_ele mkbranch mkelem mkslink protect rmbranch rmelem rmname rmver unlock_ele |
MODIFY_MD | chevent_ele chmaster_ele mkattr_ele mkhlink mklabel mktrigger rmattr rmhlink rmlabel rmtrigger |
MODIFY_TYPE | chevent_type chmaster_type lock_type mkattr_type modtype rmattr rmhlink mktype rmtype rntype unlock_type |
MODIFY_UCM | deliver_cancel deliver_complete deliver_start rebase_cancel rebase_complete rebase_start mkactivity chactivity rmactivity setactivity mkstream chstream rmstream mkbl chbl rmbl mkproject chproject rmproject mkcomp rmcomp mkfolder chfolder rmfolder |
This value is combined with the command_key_type to build the Command Key Operation token.
pre_checkin;While to start a command key that is to apply to checkins that are the result of UCM commands one would start the key similar to the one below:
pre_checkin_u;Finally, to start a command key that is to apply to base checkins and checkins that are the result of a UCM command one would start the key similar to the one below:
pre_checkin pre_checkin_u;