Product | Command type |
---|---|
ClearCase | cleartool subcommand |
ClearCase LT | cleartool subcommand |
MultiSite | multitool subcommand |
The cd command works differently depending on whether you are using a dynamic view or a snapshot view.
The cd command changes the current working directory, as does the UNIX cd(1) command. In ClearCase and MultiSite, this command is intended for use in interactive cleartool and multitool sessions and in shell scripts or batch files that simulate interactive sessions.
With a view-extended pathname, cd also changes your working directory view. The specified view's config spec determines which versions of elements are visible in your new working directory.
With a version-extended pathname that specifies an element or branch, cd changes your current working directory to a location in version-extended namespace, wherein element and branch names are treated like directories in a read-only file system. The best way to leave version-extended namespace is to change directories to a full pathname. Typing cd .. does not exit version-extended namespace until you ascend past the VOB root directory. (See the pathnames_ccase reference page.)
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.
Copyright© 2003 Rational Software. All Rights Reserved.