Region Special Access

This portion of the license file contains the list of Special Users/Groups/Elements/VOBs/Replicas/Views/Times/Regions/Hosts for the ClearTrigger region. This allows special users to avoid notification, certain logging and certain command restrictions.

Any listed users or user groups are designated such that ClearTrigger will immediately stop its processing of commands for that user or for members for group to prevent the policy defined in the clearbits file from being applied for that user or group.

Any listed VOBs, Replicas or elements are designated such that ClearTrigger will immediately stop its processing of commands in a particular VOB to prevent the policy defined in the clearbits file from being applied to those VOBs or elements. The UNIX VOBTAG style or Windows VOBTAG style or both can be used.

Any listed Views are designated such that ClearTrigger will immediately stop its processing of commands in a particular view to prevent the policy defined in the clearbits file from being applied while in the view.

Any listed Times are designated such that ClearTrigger will immediately stop its processing of commands during a particular time to prevent the policy defined in the clearbits file from being applied at the designated time.

Any listed Regions are designated such that ClearTrigger will immediately stop its processing of commands from within a matching ClearCase region to prevent the policy defined in the clearbits file from being applied while in the matching ClearCase regions.

Any listed Hosts are designated such that ClearTrigger will immediately stop its processing of commands from a matching ClearCase host to prevent the policy defined in the clearbits file from being applied while on a matching ClearCase host.

The format for this section is a list of zero or more user-ids, group names, VOBs, replicas, element names, views, times or regions enclosed by semicolons (;). User names are surrounded with parenthesis (i.e. (cclarke) ), group names are surrounded with brackets (i.e. <groupname>), VOB tags and VOB:replicas are surrounded with square brackets (i.e. [/vobs/a_vob], [\a_vob] or [\some_vob:some_replica]), element names are surrounded with curly braces (i.e. {/vobs/a_vob/foo.c} or {\a_vob\foo.c}, view names are surrounded with percent characters (i.e. %night_build_view% or %import_view%), times are surrounded with 'at' characters (@) (i.e. @D20050211@ or @d4@), ClearCase region names are surrounded with single quotes (i.e. 'unix_dev_region' ), and hostnames are surrounded with 'pipe' characters (@) (i.e. |earth| or |mars|).

Additionally, this section can contain a pattern match for the current environmental variable ABS_TRIGGER_POLICY (i.e. ^development_phase^ or ^urgent_delivery^),

The use of Dynamic Variables is also allowed (i.e. so (&) can be used to represent the current VOB_owner).

Pattern Matching is also allowed; the '*' char matches any string, the '?' character match any single chararacter and the '#' character matches any single digit. All users can be represented by a "(*)" string, all groups can be represented as <*> all VOBs can be represented as [*], all elements can be represented as {*}, all views can be represented as %*%, all ClearCase regions can be represented as '*' and all ClearCase hosts can be represented as |*|.

The use of Alias Names is also allowed; an ~alias may be used to identify a large number of (users), <groups>, {elements}, [VOBs], [VOB:replicas], %views%, @times@, 'regions', |hosts| or ^ABS_TRIGGER_POLICY_match^. Alias references (i.e. ~interns must have a trailing space after the alias name in the reference.