ClearTrigger Performance Alias Enhancers

In order to improve ClearTrigger performance on commands that have no policy defined region-wide you can tell ClearTrigger to ignore those commands. ClearTrigger will not perform itís preprocessing of those commands, exception is to check for parent clearbits files so that any parent clearbits file policy is not circumvented. For example, the proper use of these aliases will significantly speed the up the performance the recursive mklabel command for regions that have no policy on the cleartool mklabel command.

Performance AliasPurpose
#!cleartrigger_alias ABS_cleartrigger_preop_activeEnables ClearTrigger preop processing only for the included commands
#!cleartrigger_alias ABS_cleartrigger_preop_inactiveDisables ClearTrigger postop processing only for the included commands
#!cleartrigger_alias ABS_cleartrigger_postop_activeEnables ClearTrigger postop processign only for the included commands
#!cleartrigger_alias ABS_cleartrigger_postop_inactiveDisables ClearTrigger postop processing only for the included commands


If associated preop aliases (i.e. ABS_cleartrigger_preop_active and ABS_cleartrigger_preop_inactive) are both placed in the clearbits file, then only the first one encountered in the file is used.

Examples of appropriate values and what they would mean are in the table below:

Performance AliasvalueExample value(s)
ABS_cleartrigger_preop_active checkin checkout uncheckout Enables ClearTrigger preop processing for the checkin, checkout and uncheckout commands.
ABS_cleartrigger_preop_active "NONE" Disables ClearTrigger preop processing for all commands.
ABS_cleartrigger_postop_active checkin checkout uncheckout Enables ClearTrigger postop processing for the checkin, checkout and uncheckout commands.
ABS_cleartrigger_preop_inactive mklabel mkhlink Disables ClearTrigger preop processing for the mklabel and mkhlink commands.
ABS_cleartrigger_postop_inactive mklabel mkhlink Disables ClearTrigger postop processing for the mklabel and mkhlink commands.