Changing parameter values on Windows®

About this task

On Windows® hosts, the default values of lock manager parameters are defined internally. To override the defaults, you create a string value in the Windows registry.

Procedure

  1. Using a Windows® registry editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Atria\ClearCase\CurrentVersion.
  2. Click Edit > New > String Value.
  3. Select the new value and rename it LockmgrCmdLine. By default, the type of the new value is REG_SZ.
  4. Right-click the LockmgrCmdLine value and select Modify to open the Edit String window.
  5. In the Edit String window enter the following string, substituting appropriate values for num.
    -a almd -f num -u num -q num
    –a almd

    Specifies almd as the leaf name of the socket created by the lock manager. Never change this value.

    –f num (Default: 1320)

    Specifies the maximum number of database files that can be open concurrently by the lock manager. Each VOB database consists either of seven database files (in VOB schema 54) or nine database files (in VOB schema 80). The default value allows the lock manager to handle a maximum of 188 VOBs (schema 54) or 144 VOBs (schema 80). If there are more VOBs on the host, the lock manager cannot service requests for all of the VOBs concurrently and fails with the error message,

    Error from VOB database.

    If this happens, you can move some of the VOBs to another host or increase the value of -f to 7*V or 9*V (depending on the schema version) where V is the number of VOBs on the host.

    –u num (Default: 1024)

    Specifies the maximum number of simultaneous db_server or vobrpc_server connections to the lock manager. Each active view_server process accesses a VOB through a vobrpc_server process, which has a single connection per process. In addition, end-user operations use a db_server process to access a VOB, and a single db_server can have up to four connections to the lock manager. Poor user response time and messages of this form in the db_server_log or vobrpc_server_log files can indicate that the value of the –u option should be raised:

    db_VISTA database -922: lockmgr is busy

    You can roughly estimate a worst case value for –u by calculating V*(N + 5), where V is the number of VOBs on the host and N is the number of processes that access those VOBs simultaneously.

    To obtain a more realistic value (one that does not cause the lock manager to unnecessarily consume virtual memory on the VOB server host), monitor the total number of db_server and vobrpc_server processes running on the VOB server host for an extended period of typical use (perhaps a week or two). Then multiply the peak value by a factor that can accommodate growth. Due to operating system constraints, –u cannot be set higher than 2042.

    –q num (Default: 4096)
    Specifies the number of lock requests that can be queued. When there are more than num lock requests outstanding, the excess requests are dropped. Poor user response time and messages of the form

    db_VISTA database -922: lockmgr is busy

    in the db_server_log or vobrpc_server_log files may indicate that the value of –q should be raised, as follows:
    • Schema 80 VOBs: seven times the value of –u.
    • Schema 54 VOBs: no less than five times the value of –u.
  6. Click OK to set the string value.
  7. Stop and restart HCL VersionVault; this step is necessary for the changes to take effect.

Results

The new registry value is preserved when a new version of VersionVault is installed.