Config.db

In remote applications, many workstations run a VTS application. Each workstation sharing the application must have the ability to make changes to the files, pages, and tags. To enable this process to occur, VTS provides a locking scheme. Config.db, known as the configuration database, keeps track of all the locking information for a remote VTS application.

Stored for each item are:

•      The name of the item;

•      The workstation that has the item locked;

•      The server that allowed the item to be locked;

•      Various lock classifiers; and,

•      The date and time of the last modification of each item (known as a "revision value").

VTS places tag and/or page locks on all files except those listed below:

•      PageHist.txt

•      PageList.txt

•      DB-1.run

•      SecurityManager.ini

•      SecMgr.ini

•      And any files with the extension: *.BAK, *.OLD, *.DAT, *.LOG, *.DB, *.MDB, *.LDB, *.XLS, *.VAL, *.WIF, *.UDO.

In the event that you are experiencing client synchronization problems, please refer to the section that follows for instructions.

Note: It is strongly recommended that you do not modify the configuration database directly, as it is strictly for use by VTS; you should never attempt to edit Config.db.

Topics in this section:

Configuration Database Regeneration - All Clients

Configuration Database Regeneration - One Client