The mkview command creates a new view as follows:
If you want to use a snapshot view on a host that is disconnected from the network:
Operating systems use different character sequences to terminate lines of text files. In UNIX, the line terminator for text files is a single <LF> character. On Windows systems, the standard line terminator is <CR><LF>. Each view has an interop text mode—specified by the –tmode option—that determines the line terminator sequence for text files in that view. The interop text mode also determines whether line terminators are adjusted before a text file is presented to the view (at checkout time, for example). For example, a text file element created by a Windows client that is accessed through a UNIX view is stripped of <CR> characters, and the <CR> characters are reinserted when the file was written to the VOB as a new version.
For more information, see the Administrator's Guide and the reference pages for msdostext_mode and mkeltype.
Views are attached to streams in the UCM model. Only views can modify a UCM stream. Views cannot be moved between streams or detached from a stream without removing the view.
Although both kinds of views use caches, cache size is more significant for a dynamic view than for a snapshot view. The dynamic view's cache size determines the number of VOB lookups that can be stored. You can set the size of the cache with the –cachesize option. This creates the following line in the .view file for the view:
When a view_server process is started, it uses this value. For more information about the view_server cache and changing its size, see the setcache and chview reference pages and the Administrator's Guide.
A view's associated view_server process reads a configuration file when it starts up. You can revise this file, for example, to make the view read-only. See the Administrator's Guide.
For information about performing view backups, see the Administrator's Guide.
If you create a snapshot view in which the view-storage directory is located outside the snapshot view directory, you must back up recursively both the view storage directory and the snapshot view directory.
The view created by this command is the root of a standard directory tree; but a view must be deleted only with the rmview command, never with an operating system file deletion command. See the rmview reference page for details.
This section contains information about view creation that differs depending on the product, view type, and platform you are using.
You can configure a dynamic view to use the express builds feature by creating the view with the –nshareable_dos option. When you invoke clearmake or omake in this kind of view, clearmake or omake builds nonshareable derived objects (DOs). Information about these DOs is not written into the VOB, so the build is faster; however, nonshareable DOs cannot be winked in by other views.
If you do not specify –shareable_dos or –nshareable_dos, mkview uses the site-wide default set in the registry (with the setsite command). If there is no site-wide default, mkview configures the view so that builds in the view create shareable DOs.
To change the DO property for an existing view, use the chview command. For more information on shareable and nonshareable DOs, see Building Software.
A dynamic view to be used for NFS export of one or more VOBs (for access by applications other than those in the ClearCase Product Family) must be marked in the registry as an export view. Each export view is assigned an export ID, which ensures that NFS-exported view/VOB combinations have stable NFS file handles across server reboots or shutdown and restart of ClearCase.
If the dynamic view is registered in multiple regions, the export marking must be on the view tag in the server host's default region. To create an export view, use the –ncaexported option. You can register an existing dynamic view or VOB for export by using mktag –replace –ncaexported. For information about exporting view-VOB combinations, see the export_mvfs reference page.
Creating a view tag also executes the startview command, which activates the dynamic view on the current host (unless the tag's target network region does not include the local host.) It also places an entry in the host's viewroot directory. (For example, specifying –tag gamma creates the entry /view/gamma.)
After it is activated, a dynamic view can be set with the setview command; it can also be accessed with view-extended naming. (For details, see the startview and pathnames_ccase reference pages.)
Creating a view tag also executes the startview command, which activates the dynamic view on the current host (unless the tag's target network region does not include the local host.) It also places an entry in the host's dynamic-views root directory (by default, drive M). (For example, specifying –tag gamma creates the entry gamma.)
After a dynamic view is activated, you can assign it to a drive letter with the net use command or by clicking Tools > Map Network Drive in Windows Explorer; it can also be accessed with view-extended naming. (For details, see the startview and pathnames_ccase reference pages.)
Snapshot views cannot be explicitly activated and cannot be accessed using view-extended naming. However, a snapshot view becomes active when you change to the view directory and issue a ClearCase or ClearCase LT command.
Avoid creating views as root. This often causes problems with remote access to a view, because root on one host often becomes user ID –2 (user nobody) when accessing other hosts.
Your current umask(1) setting determines which users can access the view. For example, a umask value of 2 allows anyone to read data in the view, but only you (the view's owner) and others in your group can write data to it—create view-private files, build derived objects, and so on. If your umask value is 22, only you can write data to the new view.
You may create a view with storage on a supported network attached storage (NAS) device. We recommend using a server storage location for this purpose. See the mkstgloc reference page for information. To use mkview to create a view that resides on a NAS device, you must specify the option set, –host –hpath –gpath. (NAS devices must be specially configured for use with ClearCase. See the Administrator's Guide for details.)
Snapshot views: A generated tag.
Snapshot view—Specifies a name for the view as it is recorded in the registry.
ClearCase—If your network has multiple regions, use the mktag command to create an additional view tag for each additional region.
ClearCase LT: –snapshot (The ClearCase LT synopsis for this command retains this option, even though it is the default, for easier migration of view-creation scripts from ClearCase LT to ClearCase.)
Note: VOBs that are to be accessed by interop text mode views must be enabled to support such views. See the msdostext_mode reference page.
Caution: The view tag created with mkview must be for the network region to which the view server host belongs. Thus, use this option only when you are logged on to a remote host that is in another region. Moreover, a view tag for the view's home region must always exist.
This mechanism is independent of the network storage registry facility. The pathname to a remote storage area must be truly global, not global within a particular network region.
Dynamic views: None; a server storage location must be specified explicitly using –stgloc or indirectly using –auto.
For dynamic views, automatic server storage selection proceeds as follows:
ClearCase snapshot views: An automatically selected server storage location, if any can be found; else –colocated_server.
ClearCase LT (snapshot) views: An automatically selected server storage location.
For snapshot views, automatic server storage selection proceeds as follows:
For information on using this option to create snapshot views for disconnected use, see the section“Disconnected Use of Snapshot Views”. You cannot create a view on a remote heterogeneous host unless the view is a snapshot views that is to be created in no-global-path (–ngpath) server storage location.
We recommend that you use –stgloc rather than this option whenever possible.
For information on using this option to create snapshot views for disconnected use, see the section, “Disconnected Use of Snapshot Views”.
We recommend that you use –stgloc rather than this option whenever possible.
Note: The argument names shown above are generalizations of the argument names as they appear in the synopses for this command in association with the –colocated_server and –vws options.
When you use one or more of the –host/–hpath/–gpath options in combination with –colocated_server, the values you specify for –host/–hpath/–gpath must correspond to the snapshot view directory (snapshot-view-pname), not the colocated view storage directory.
When you use one or more of the –host/–hpath/–gpath options in combination with –vws, the values you specify for –host/–hpath/–gpath must correspond to the view storage directory (view-storage-pname), not the snapshot view directory.
To create a view that resides on a supported network attached storage (NAS) device, you must specify the option set, –host –hpath –gpath.
UNIX systems—See the description of CCASE_GPATH_HINTS in the env_ccase reference page for related information.
In addition, on Windows systems:
UNIX systems—See the description of CCASE_GPATH_HINTS in the env_ccase reference page for related information.
In addition, on Windows systems:
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.
Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.
cmd-context mkview -tag anneRel2 /view_store/anneRel2.vws
Created view.
Host-local path: host3:/view-store/anneRel2.vws
Global path: /net/host3/view-store/anneRel2.vws
It has the following rights:
User : anne : rwx
Group: dev : rwx
Other: : r-x
rsh host4 cleartool startview anneRel2
The remote shell command is named remsh on some systems.
cmd-context mkview -tag dev -snapshot ~bert/my_views
Created view.
Host-local path: peroxide:/export/home/bert/my_views/.view.stg
Global path: /net/peroxide/export/home/bert/my_views/.view.stg
It has the following rights:
User : bert : rwx
Group: user : r-x
Other: : r--
Created snapshot view directory
"/net/peroxide/export/home/bert/my_views".
cmd-context mkview -stream java_int@/vobs/core_projects -tag java_int
/usr1/views/java_int.vws
Created view.
Host-local path: propane:/usr1/views/java_int.vws
Global path: /net/propane/usr1/views/java_int.vws
It has the following rights:
User : bill : rwx
Group: user : rwx
Other: : r-x
Attached view to stream "java_int".
Copyright© 2003 Rational Software. All Rights Reserved.