The cleartool user profile (.clearcase_profile) is an ordered set of rules that determine certain command option defaults for one or more cleartool commands. An option you supply in a command line overrides the command option default specified in .clearcase_profile.
For example, many cleartool commands accept user comments with the –c, –cfile, –cq, –cqe, or –nc option. If you specify none of these options, cleartool invokes one of them by default. The option invoked is different for each command, but is always one of –cq, –cqe, or –nc. If cleartool finds a file named .clearcase_profile in your home directory, it checks to see whether the file contains a comment rule that applies to the current command. If so, it invokes the comment option indicated by that rule. No error occurs if this file does not exist; cleartool invokes the command's standard comment default.
An alternative name for the user profile can be specified with the environment variable CLEARCASE_PROFILE. Its value must be a full pathname.
For a given command, cleartool consults the user profile to determine which rule, if any, applies to a command. The method is similar to the one used by the view_server process to evaluate a config spec:
cleartool uses the first rule that applies. Therefore, the order of rules in the user profile is significant. For example, to ensure that you are always prompted for a comment when you create a directory element, you must place a rule for the mkdir command before any more general rule that may also apply to mkdir, such as * –nc.
Rules must be placed on separate lines. Extra white space (space, tab) is ignored.
Comments begin with a number sign (#). For example:
Each rule consists of two tokens, separated by white space:
When specifying a comment rule:
If you do not provide a comment rule for one of these commands, cleartool uses –cqe as its default comment option. cleartool uses –nc as the default for all other commands that accept comments.
When specifying a rule for the state of a checked-out version:
If one rule only is specified, all checkouts are reserved or unreserved by default. If the rules are specified as
then a reserved checkout is attempted. If there is a conflict, an unreserved checkout is performed.
Copyright© 2003 Rational Software. All Rights Reserved.