Soft - is your software and documentation
Man page notes:
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 IBM Rational ClearCase Administrator's Guide and the reference pages for msdostext_mode and mkeltype.
Views and UCM streams
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.
Setting the cache size for views
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 IBM Rational ClearCase Administrator's Guide.
Reconfiguring a view
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 IBM Rational ClearCase Administrator's Guide.
Backing up a view
For information about performing view backups, see the IBM Rational ClearCase 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.
Deleting a view
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.
Information specific to products, view types, and platforms
This section contains information about view creation that differs depending on the product, view type, and platform you are using.
ClearCase dynamic views: Using express builds
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 the IBM Rational ClearCase Guide to Building Software.
ClearCase dynamic views on UNIX: Marking a view for export
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.
ClearCase dynamic views on UNIX: Activating a view
Creating a view tag also runs 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.)
ClearCase dynamic views on Windows: Activating a view
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.)
ClearCase and ClearCase LT snapshot views: Activating a view
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.
ClearCase and ClearCase LT snapshot views: Location of the view storage directory
When you create a snapshot view that you intend to use when connected over a WAN, performance of some operations can be improved if you create the view storage directory on a host that remains on the local area network, as described here.
Create the snapshot view directory on the client host (the computer that may sometimes be connected on a wide area network, rather than the local area network that hosts the VOBs).
Create the view storage directory in a location that is consistently connected to the local area network, on a host where ClearCase or ClearCase LT has been installed or on a NAS device that provides storage for such a host. This location could be a server storage location (specified by –stgloc) or a location specified by the –vws option. Do not use –colocated_server; this option creates the view storage directory as a subdirectory of the snapshot view directory (where it can be disconnected from the network).
ClearCase and ClearCase LT on UNIX: View creator identity and umask permissions
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.
ClearCase: View storage directory on a network attached storage device
You can create a view with storage on a supported network attached storage (NAS) device. Use 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. For details, see the IBM Rational ClearCase Administrator's Guide.
A. The mkview command creates a new view as follows:
Creates a view storage directory. The view storage directory maintains information about the view. Along with other files and directories, the directory contains the view's config spec and the view database. In ClearCase LT, the locations of view storage directories are restricted to the ClearCase LT server host. Creates a view tag, the name by which users access a dynamic view. Snapshot views also have view tags, but these are for administrative purposes; users access snapshot views by setting their working directory to the snapshot view directory (for example, using the cd command. For a snapshot view, creates the snapshot view directory. This is the directory into which your files are loaded when you populate the view using update. This directory is distinct from the view storage directory. Places entries in the network's view registry; use the lsview command to list view tags. Starts a view_server process on the specified host. The view_server process manages activity in a particular view. It communicates with VOBs during checkout, checkin, update, and other operations.
B. Specifies a name for the view as it is recorded in the registry.
C. Specifies a name for the view, in the form of a simple file name. This name appears in the local host's file system as a subdirectory of the viewroot directory. For example, the view experiment appears as /view/experiment (UNIX) or M:\experiment (Windows).
D. VOBs that are to be accessed by interop text mode views must be enabled to support such views. See the msdostext_mode reference page.
E. Creates an insert_cr interop text mode view. The view converts <NL> line terminators to the <CR><NL> sequence when reading from a VOB, and <CR><NL> line terminators to single <NL> characters when writing to the VOB.
F. Creates a strip_cr interop text mode view. The view converts <CR><NL> line terminators to <NL> when reading from a VOB, and <NL> line terminators back to the <CR><NL> sequence when writing to the VOB.
G. A transparent interop text mode view is created. The line terminator for text files is a single <NL> character. The view does not transform text file line terminators in any way.
H. Restriction: 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.
I. An error occurs if the region does not exist. (Cannot be used with –str/eam .)
J. Creates the .s directory at the location specified by remote-storage-dir-pname. A UNIX-level symbolic link to pname is created at view-storage-dir-pname/.s, providing access to the remote storage area.
remote-storage-dir-pname must be a valid path name on every host (regardless of its network region) from which users will access the view.
This view cannot be used to export a VOB to a non-ClearCase host. (See the exports_ccase reference page.)
Some operations performed by root in this view may fail. This is another symptom of the root-becomes-nobody problem explained in ClearCase and ClearCase LT on UNIX: View creator identity and umask permissions. This mechanism is independent of the network storage registry facility. The path name to a remote storage area must be truly global, not global within a particular network region.
K. Assigns an export ID to the view tag.
L. Specifies a size for the view_server cache. size is an integer number of bytes, optionally followed by the letter k to specify kilobytes or m to specify megabytes; for example, 800k or 3m.
M. The initial default for the time stamps of files copied into the view as part of the snapshot view update operation is the time at which the file is copied into the view. Using the update command, users can change the default time-stamp mode: 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.
N. Specifies that DOs created in the dynamic view cannot be winked in by other views
O. Changes the initial default for file time stamps copied into the snapshot view to the time at which the version was created (as recorded in the VOB).
P. Specifies a UCM stream. The view being created is attached to this stream. (Cannot be used with –reg/ion.) stream-selector is of the form [stream:]stream-name[@vob-selector], where vob-selector specifies the stream's project VOB.
Q. 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.
R. Specifies a view storage directory that is colocated with the snapshot view directory; specifically, the view storage directory is created as a subdirectory of the snapshot view directory (snapshot-view-pname).
See cleartool mkview for an explanation of how -auto selects a storage location .
T. Server storage location must have been created previously with mkstgloc.
U. ClearCase snapshot views: An automatically selected server storage location, if any can be found; else –colocated_server
V. Specifies the location for the snapshot view storage directory. On Windows systems, this must be a UNC name. For information on using this option to create snapshot views for disconnected use, see ClearCase and ClearCase LT snapshot views: Location of the view storage directory under Information specific to products, view types, and platforms. Use –stgloc rather than this option whenever possible.
W. 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:
Server storage locations that have no global path (–ngpath) are disqualified.
Server storage locations on heterogeneous hosts are disqualified.
Local server storage locations are preferred over remote ones.
A server storage location is selected at random from the remaining candidates.
Note: All the command below rely on there being a ccviewstore directory, in the root directory at UNIX or as a Shared drive in Windows. The /net/samecs mount assumes a hostname of samecs, which has been either hard mounted or auto-mounted on /net in UNIX.
cleartool mkview –tag gbush_view –tco “Geoff Bush ClearCase View no unauthorised access” /ccviewstore/gbush_view.vws
cleartool mkview –tag gbush_view –tco “Geoff Bush ClearCase View no unauthorised access” -host viewserver.samecs.com
-hpath /net/samecs/ccviewstore/gbush_view.vws -gpath /net/samecs/ccviewstore/gbush_view.vws
cleartool mkview –tag gbush_view –tco “Geoff Bush ClearCase View no unauthorised access” -host viewserver.samecs.com
-hpath \\samecs\ccviewstore\gbush_view.vws -gpath \\samecs\ccviewstore\gbush_view.vws
cleartool mkview –tag gbush_view –tco “Geoff Bush ClearCase View no unauthorised access” –stgloc samecs_view_storage