The dce_db_lock() routine acquires the lock associated with the handle.
There is an advisory lock associated with each handle. The routines for storing and deleting backing stores apply the lock before updating a backing store. This routine provides a means to apply the lock for other purposes, such as iteration.
Advisory locks allow cooperating threads to perform consistent operations on backing stores, but do not guarantee consistency; that is, threads may still access backing stores without using advisory locks, possibly resulting in inconsistencies.
Functions: dce_db_delete(3dce), dce_db_delete_by_name(3dce), dce_db_delete_by_uuid(3dce), dce_db_store(3dce), dce_db_store_by_name(3dce), dce_db_store_by_uuid(3dce), dce_db_unlock(3dce).