To access files under HCL VersionVault source control, you set up and work in a view. A view provides a directory tree of one version of each file in your project. In the view, you modify source files, compile them into object modules for testing purposes, and format them into documents.

View tags

Each view must have a view tag, a unique, descriptive name. (The view tag must be unique within its network region.) Choose a name that helps you determine the owner and purpose of the view. Names like myview or work do not describe the view owner or contents; if you work with more than one view, such generic names can lead to confusion.

A view tag must be a simple name; that is, it must follow the format of a single file or directory name with no special characters or spaces.

Assigning views to drives (Windows® systems only)

If your makefiles or other files require absolute paths or if using a persistently mapped drive is more convenient than navigating to the view, assign it to a drive.

Setting umask (UNIX® systems and Linux® only)

Your umask(1) setting at the time you create a view affects how accessible it is to others.

View storage directories

Every view has a view storage directory. This directory is used to keep track of information such as which files are loaded into your view and which versions are checked out to it. The view storage directory is for HCL VersionVault administrative purposes only. Do not modify it.