Rational ClearCase Commands Referenceannotate
apropos
catcr
catcs
cc.icon
cc.magic
cd
chactivity
chbl
checkin
checkout
checkvob
chevent
chflevel
chfolder
chmaster
chpool
chproject
chstream
chtype
chview
clearaudit
clearbug
cleardescribe
cleardiffbl
cleardiff
clearexport_ccase
clearexport_cvs
clearexport_pvcs
clearexport_rcs
clearexport_sccs
clearexport_ssafe
clearfsimport
cleargetlog
clearhistory
clearimport
clearjoinproj
clearlicense
clearmake
clearmake.options
clearmrgman
clearprojexp
clearprompt
cleartool
clearviewupdate
clearvobadmin
comments
config_ccase
config_spec
cptype
credmap
creds
deliver
describe
diffbl
diffcr
diff
dospace
edcs
endview
env_ccase
events_ccase
export_mvfs
exports_ccase
file
find
findmerge
fmt_ccase
getcache
get
getlog
help
hostinfo
init_ccase
ln
lock
lsactivity
lsbl
lscheckout
lsclients
lscomp
lsdo
lsfolder
lshistory
ls
lslock
lsmaster
lspool
lsprivate
lsproject
lsregion
lsreplica
lssite
lsstgloc
lsstream
lstype
lsview
lsvob
lsvtree
makefile_aix
makefile_ccase
makefile_gnu
makefile_pmake
makefile_smake
makefile_sun
man
merge
mkactivity
mkattr
mkattype
mkbl
mkbranch
mkbrtype
mkcomp
mkdir
mkelem
mkeltype
mkfolder
mkhlink
mkhltype
mklabel
mklbtype
mkpool
mkproject
mkregion
mkstgloc
mkstream
mktag
mktrigger
mktrtype
mkview
mkvob
mount_ccase
mount
msdostext_mode
mvfslog
mvfsstorage
mvfstime
mvfsversion
mv
omake
pathnames_ccase
permissions
profile_ccase
promote_server
protect
protectvob
pwd
pwv
query_language
quit
rebase
recoverview
reformatview
reformatvob
register
relocate
rename
reqmaster
reserve
rgy_backup
rgy_check
rgy_passwd
rgy_switchover
rmactivity
rmattr
rmbl
rmbranch
rmcomp
rmdo
rmelem
rmfolder
rmhlink
rmlabel
rmmerge
rmname
rmpool
rmproject
rmregion
rmstgloc
rmstream
rmtag
rmtrigger
rmtype
rmver
rmview
rmvob
schedule
schemes
scrubber
setactivity
setcache
setcs
setplevel
setsite
setview
shell
snapshot.conf
softbench_ccase
space
startview
type_manager
umount
uncheckout
unlock
unregister
unreserve
update
version_selector
view_scrubber
vob_restore
vob_scrubber
vob_sidwalk
vob_snapshot
vob_snapshot_setup
wildcards_ccase
winkin
xclearcase
xcleardiff
xmldiffmrg
DESCRIPTION
For information about specifying config spec content, see the config_spec reference page. As a rule, you never edit a UCM config spec; see the config_spec reference page for exceptions to this rule.
This command does not require a product license.
General Information—The Edit Session
The edcs command revises a view's config spec by invoking a text editor on an existing config spec. The config spec can be one of the following:
ClearCase on UNIX—The Edit Session
In ClearCase, if the working directory view differs from the set view (established by the setview command), edcs displays a warning message and uses the working directory view. The text editor invoked by edcs is specified by the environment variable WINEDITOR (first choice), VISUAL (second choice), or EDITOR (third choice). If none of these EVs is set, vi(1) is invoked.
When you invoke edcs without specifying the file argument, ClearCase and ClearCase LT run the text editor from the /tmp directory. When you end the editing session and set the config spec, the config spec is stored in the view storage directory. However, if you perform other operations from within the text editor, ClearCase and ClearCase LT execute those operations from /tmp, not from the directory where you invoked edcs. For example, in a vi editing session, the command :w prev-cs copies the contents of the config spec to a file named prev-cs and stores prev-cs in /tmp.
ClearCase and ClearCase LT on Windows—The Edit Session
In ClearCase and ClearCase LT, the text editor invoked by edcs is specified by the VISUAL environment variable; if this EV is not set, edcs uses the value of the EDITOR environment variable. If neither EV is set, edcs invokes the Notepad.
After the Edit Session
At the end of the edit session, there is a confirmation step. For dynamic views, this prompt is
For snapshot views, this prompt is
If you answer yes, the modified config spec is set as the view's config spec. (In a snapshot view, there is an additional confirmation step if the edits to the config spec cause elements to be unloaded from the snapshot view.)
Note: In a snapshot view, setting the config spec initiates an update -noverwrite operation and generates an update logfile with the default name and location. (See the update reference page for information about this logfile.) To execute this command on the command line, you must be in or under the root directory of the snapshot view.
If you answer no, the command is canceled; the view retains its current config spec.
ClearCase and ClearCase LT on UNIX—Export View Config Specs
If you modify the config spec of a view that is being exported for non-ClearCase access, make sure that all users who may currently have the view mounted for that purpose unmount and remount the view. Unmounting and remounting the view ensures access to the correct set of files as specified in the updated config spec.
OPTIONS AND ARGUMENTS
Specifying the View
- Default
- Edits and sets a config spec for the current
view.
- –tag view-tag
- The view tag of any dynamic view; the view
need not be active.
Note: To edit the config spec of a snapshot view, you must be in that view. However, in a snapshot view, you can use this option to edit the config spec of a dynamic view.
EXAMPLES
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.