edcs

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:

• The view's current config spec
• A text file that you want to edit and then make the view's config spec. (If you don't need to edit the file, use setcs.)

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 runs 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 executes 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.

In ClearCase, 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.

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.)

If you answer no, the command is canceled; the view retains its current config spec.

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.

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, web, or automatic view, you must be in that view. In a snapshot view, you can use this option to edit the config spec of a dynamic view.

Default

Edits the view's current config spec.

file

The path name of a file to be used as input to the edit session. If the file does not exist, edcs creates it.

Default

All hijacked files are left in the view with their current modifications.

-ove/rwrite

Overwrites all hijacked files with the version selected by the config spec.

-ren/ame/

Renames hijacked files to filename.keep and copies the version in the VOB selected by the config spec into the view.

Default

The initial default is set by the mkview command. Thereafter, the most recently used time scheme is retained as part of the view's state and is used as the default behavior for the next update.

-cti/me

Sets the time stamp of a file element to the current time, that is, the time at which the version is copied into the view. -ctime has no effect on directories (directories always use the current time).

-pti/me

Sets the time stamp of a file element to the time at which the version was checked in to the VOB. -ptime has no effect on directories. (Directories always use the current time.)