config_ccase

VersionVault configuration

Applicability

Product

Command type

VersionVault

data structure

Platform

UNIX

Linux

Windows

Synopsis

Most VersionVault configuration options can be set using a cleartool command or a VersionVault GUI. Only a few require you to edit a text file (on UNIX and Linux) or a Windows registry key as described here.

Description: UNIX and Linux system files

Files in /var/adm/hcl/versionvault

Anyone can read the information in this directory, but only the root user can modify it.

license.db
(License server host only) The license database file, which defines a set of VersionVault licenses. See the Help.

Files in /var/adm/hcl/versionvault/config

Anyone can read and write information in this directory to configure the local host, with the exception of rgy_hosts.conf and rgy_region.conf. Only the root user can modify these two files to configure the local host.

alternate_hostnames
If a host has two or more network interfaces (two or more separate lines in the /etc/hosts file or the hosts NIS map), you must create a file with this name on that host to record its multiple entries. For example, suppose that the /etc/hosts file includes these entries:
159.0.10.16 widget river-005 wid
159.0.16.103 widget-gtwy river-105 

In this case, the alternate_hostnames file should contain these names:

widget
widget-gtwy

Only the first host name in each hosts entry must be included in the file. The file must list each alternative host name on a separate line. There is no commenting facility; all lines are significant. If a host does not have multiple network interfaces, this file should not exist.

automount_prefix
By default, the UNIX or Linux automount program mounts remote directories under /tmp_mnt. If automount uses a different location, you must specify it in file /var/adm/hcl/versionvault/automount_prefix. For example, if your automatic mounts take place within directory /autom, create an automount_prefix file containing this line:
/autom
bldserver.control
Controls the way in which a host is used during parallel builds. See the Help.
license_host
(Required for each VersionVault host) Contains the name of the host that acts as the VersionVault license server host for the local host.
snapshot.conf
Configuration information for semi-live VOB backup. For more information, see the vob_snapshot reference page.
admin.conf
Controls whether this host's VersionVault properties can be changed by a user logged on to a remote host.
db.conf
Configuration information for the file, vista.tjf, which is a journal of VOB updates. This file can grow large, especially as a result of such operations as rmver, rmview, rmtype, and scrubber. To limit the size of vista.tjf, create the file db.conf (in /var/adm/hcl/versionvault/config) and add the line

–journal_file_limit bytes

where bytes may not be less than 5000000. Setting this value too low may degrade performance.

lockmrg.conf
Changes the default startup options for the lockmgr. For more information, see the Help.
rgy_hosts.conf
Specifies this host's registry server and backup registry server hosts.
rgy_region.conf
Specifies this host's registry region.

Description: Windows registry keys and files

Values in registry key

The registry key is HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Atria\ClearCase\CurrentVersion.

If necessary, you can modify these values directly with a Windows Registry Editor.

Registry key

Description

snapshot

Configuration information for semi-live VOB backup. For more information, see the vob_snapshot reference page.

LockMgrCommandLine

Changes the default startup options for the lockmgr. For more information, see the Help.

DomainMappingEnabled

Enables this host to use domain mapping (to support VersionVault access by users from multiple Windows domains), as described in the Help.

Files in \var\config

Anyone can read or write to this directory.

db.conf

Configuration information for the file, vista.tjf, which is a journal of VOB updates. This file can grow large, especially as a result of such operations as rmver, rmview, rmtype, and scrubber. To limit the size of vista.tjf, create the file db.conf (in versionvault-home-dir\var\config) and add the line –journal_file_limit bytes where bytes may not be less than 5000000. Setting this value too low may degrade performance.