The locking scheme instigated by VTS for remote or networked applications uses the Config.db configuration database to store information on locked items. Stored for each item is the following information:
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.
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 edit Config.db.
You should never try to connect directly to Config.db with a db system call, even if your application is not running. If you must view within Config.db, use Safe View, a VTS application that has been created for the purpose of scoping into the accessor module. The accessor module is a special module used by VTS that uses an active system call to access the data within Config.db. This accessor module is the only handle allowed to access Config.db.