setcs

Product	Command type
ClearCase®	cleartool subcommand

Platform
UNIX®
Linux®
Windows®

Description

This command does not require a product license.

The setcs command changes the config spec of a view to the contents of a user-specified or system-default file, or it causes the view's associated view_server process to flush its caches and reevaluate the current config spec.

For UCM views, the setcs command verifies that the view's configuration matches the configuration defined by the stream it is attached to and, if needed, reconfigures the view. Load rules already in the view's configuration are preserved.
For ClearCase on UNIX or Linux, if the working directory view differs from the set view (established by the setview command), setcs displays a warning message and uses the working directory view.
In a snapshot view, setcs initiates an update -noverwrite operation for the current view and generates an update logfile with the default name and location. (For information about this log file, see the update reference page.)

For more information about view contexts, see the pwv reference page. For a complete discussion of config specs, see the config_spec reference page.

UNIX and Linux —export view config specs

If you change 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: Reconfigures the current view.
–tag view-tag: The view tag of any dynamic view; the view need not be active. To set the config spec of a snapshot view, you must be in or under the snapshot view root directory (and accordingly you do not use this option). However, you can use this option to set the config spec of a dynamic view from within a snapshot view.

Specifying the kind of change

Default

None.

–cur/rent

Causes the view_server to flush its caches and reevaluate the current config spec, which is stored in file config_spec in the view storage directory. This includes:

Evaluating time rules with nonabsolute specifications (for example, now, Tuesday)
Reevaluating –config rules, possibly selecting different derived objects than previously
Re-reading files named in include rules

–def/ault

Resets the view's config spec to the contents of default_config_spec, the host's default config spec.

pname

Specifies a text file whose contents are to become the view's new config spec.

–stre/am

For a UCM view, sets the view's config spec to that defined by the stream it is attached to. This operation preserves any load rules already in the view's config spec.

Handling hijacked files

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.

Determining the modification time stamp

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

Examples

The UNIX system and Linux 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 system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.

Change the config spec of the current view to the contents of file cspec_REL3.
cmd-context setcs cspec_REL3
Change the config spec of the view whose view tag is jackson_vu to the default config spec.
cmd-context setcs –tag jackson_vu –default
Have the view_server of the current view reread its config spec.
cmd-context setcs –current

setcs

Applicability

Synopsis