startview

Starts or connects to a dynamic view's view_server process

APPLICABILITY

SYNOPSIS

startview view-tag ...

DESCRIPTION

Prerequisite: The dynamic view being started must already have a view-tag in the network's view-tag registry file. See the mkview and mktag reference pages.

The startview command enables processes on the local host to access a dynamic view, as follows:

• Establishes an RPC connection between the local host's MVFS (ClearCase multiversion file system) and the dynamic view's view_server process.

• Creates a view-tag entry in the local host's viewroot directory. If a view_server process is not already running, startview invokes one on the host where the view storage area physically resides.

The default name of the viewroot directory is

• UNIX-/view. (See the init_ccase reference page for more information.)

• Windows-M:\.

Thus, starting a dynamic view that has been registered with view-tag main creates the directory entry /view/main or M:\main. After this directory entry is created, any process on the local host can access the view through view-extended pathnames.

The dynamic view's view-tag must already be registered, which is accomplished either at view creation time (with a mkview command) or subsequently (with mktag -view).

NOTE:  startview is not applicable to a snapshot view. To activate a snapshot view, change to the views's view-storage directory and issue a ClearCase command.

When to Use startview

Both mkview and mktag invoke startview. Typically, startview is used to establish view-extended naming access. There are two main cases:

• Because mkview and mktag invoke startview on the local host only, remote users who want only view-extended naming access to the dynamic view must use startview.

• After your system has been stopped and restarted (see EXAMPLES), both local and remote users can use startview to reestablish view-extended naming access to a dynamic view.

NOTE TO UNIX USERS: setview also invokes startview, if necessary. Therefore, it is rarely necessary to invoke startview explicitly. startview is used to establish view-extended naming access without creating a process that is set to the view (as happens with setview).

RESTRICTIONS

None.

OPTIONS AND ARGUMENTS

SPECIFYING THE VIEW.  Default: None.

view-tag ...

One or more currently registered view tags (that is, view tags visible to lsview).

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.

• The dynamic view anne_Rel2 is registered, but its view_server process went down in a system crash. Restart anne_Rel2, and make it the working directory view.

cmd-context startview anne_Rel2

C:\> M:

M:\> cd \anne_Rel2\vob_pr2

• Create a dynamic view on the local host, and establish view-extended naming access to the view on host3.

cmd-context mkview -tag mainRel2 /view_store/mainRel2.vws
Created view.
Host-local path: host2:/view-store/mainRel2.vws
Global path: /net/host2/view-store/mainRel2.vws
It has the following rights:
User : anne : rwx
Group: dev :
% rsh host3 cleartool startview mainRel2

On host3, enter the following command:

cmd-context startview mainRel2

SEE ALSO

endview, lsview, setview, Administrator's Guide