Type of view supported

UNIX computers support dynamic views and snapshot views.

Windows 98 and Windows Me computers support only snapshot views.

Windows NT and Windows 2000 computers always support snapshot views and can be set up to support dynamic views as well.

For a comparison of dynamic views and snapshot views, refer to Developing Software.

Starting dynamic views

Use setview or startview. The setview command starts a new shell that uses a set of rules to identify the correct version of files that appear in a VOB. The startview command starts a process that is consulted when accessing files by means of a view-extended pathname to a VOB.

In ClearCase Explorer, click Start View. Starting a dynamic view adds a folder below the dynamic-views drive (drive M by default), which is accessible through Windows Explorer or a command shell.

There is no equivalent to the cleartool setview command. However, mapping a drive letter to a view or browsing for a view using Network Neighborhood is similar.

Accessing active dynamic views

Access all views active on the current computer through the /view directory.

Access all dynamic views active on the current computer from the dynamic-views drive (drive M by default), or map each active view to its own drive letter.

Each active view-tag also appears under the UNC name \\view\viewname.

Activating VOBs

All users can mount all public VOBs. Private VOBs can be mounted only by the VOB owner (or by the root user).

All users can mount all VOBs, public or private. Public VOBs are distinguished only by the fact that they can be mounted with the command cleartool mount -all.

Accessing active VOBs

From a shell started with the setview command, access each VOB mounted on the current computer using the vob-tag path name.

When using the startview command, access VOBs through the pathname /view/view-tag/vob-tag.

Access each VOB mounted on the current computer through a specific view-tag. For example, M:\view-tag\vob-tag or D:\vob-tag.

Security model for modifying VOBs

A VOB inherits the user, primary group, and additional group list of the user who runs the mkvob command.

When you create it, a VOB does not include the "additional group" list. Only the creator's UID and primary group are assigned ownership of the VOB.

Windows VOBs must be created by a user whose primary group is the same as the primary group of all other users who will be writing to the VOB. As an alternative, Windows users can use the CLEARCASE_PRIMARY_GROUP environment variable to set - and guarantee - the correct primary group.

For more information, see the chapters on Windows/UNIX interoperation in the Administrator's Guide.

Symbolic links and hard links

UNIX file systems support symbolic links and hard links.

Windows does not support OS-level symbolic links or hard links. Therefore, remote storage pools (mkpool -ln) and remote view-private storage (mkview -ln) are disallowed on Windows VOBs and views. Dynamic views do support VOB symbolic links and VOB hard links.

Wildcard characters

Standard command shells support wildcard characters (*, ?, and so on) on the command line.

Because standard Windows command shells do not expand pathname wildcard characters (*, ?, and so on) on the command line, cleartool commands cannot include pathname wildcards unless issued in interactive mode, where cleartool itself processes the command line. For more information, see the wildcards_ccase reference page.

Case sensitivity

File creation and file lookups are case-sensitive.

File-creation operations typically preserve case, but file lookups are not case sensitive.

Note that cleartool is case sensitive on Windows. For more information, see the chapters on Windows/UNIX interoperation in the Administrator's Guide.

Line termination

Line termination sequences in most text editors are typically a single newline (<NL>) character or a line feed (<LF>) character.

Line termination sequences in most text editors are typically <CR><LF>.

Take note of how your text editors handle line termination. For more information about line termination issues, see the discussion of miscellaneous tasks in the manual Developing Software and the msdostext_mode reference page.