edcs

Edits the config spec of a view

APPLICABILITY

SYNOPSIS

• ClearCase and Attache-Edit the config spec of a dynamic view:

edcs [ -tag view-tag ] [ file ]

• ClearCase, ClearCase LT, and Attache-Edit the config spec of a snapshot view:

edcs [ file ]

DESCRIPTION

For information on 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 (ClearCase and ClearCase LT) or by downloading a config spec into a temporary file and invoking a text editor on an existing config spec (Attache). 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.)

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:

Set config spec for view "view-tag"? [yes]

For snapshot views, this prompt is:

Set config spec and load snapshot view "view-tag"? [yes]

If you answer yes:

• In ClearCase and ClearCase LT, 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 on this logfile). To execute this command on the command line, you must be in or under the root directory of the snapshot view.

• In Attache, the changed file is uploaded and a remote setcs command is issued.

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

ClearCase, ClearCase LT, and Attache 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.

RESTRICTIONS

None.

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.

SPECIFYING THE CONFIG SPEC FILE.  Default: Edits the view's current config spec.

file

The pathname of a file to be used as input to the edit session.

(ClearCase and ClearCase LT) If the file does not exist, edcs creates it.

(Attache) If the file does not exist locally, edcs downloads it if it exists remotely, or creates it locally if it does not exist. The named file is saved both locally and remotely. Both the local and remote temporary files are deleted after the file has been uploaded.

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. In Attache, cmd-context represents the workspace prompt.

• Edit the config spec of the current view.

cmd-context edcs

• Edit the config spec of the dynamic view with the view-tag jackson_fix.

cmd-context edcs -tag jackson_fix

• Use a text file named cspec_rel3 as input to an edit session, producing a new config spec for the current view.

cmd-context edcs cspec_rel3

SEE ALSO

attache_command_line_interface, attache_graphical_interface, catcs, config_spec, lsview, mktag, setcs, setview, update