Check for parallel versions

Parallel versions occur when two or more versions are checked out from a single file or directory.

During the receive operation, DCM optionally checks for parallel versions. Even if parallel versions are disabled in both the generating database and receiving database, when an object is checked out in one database, parallels might not be visible. However, when those new versions are later replicated to other databases, parallels that exist are visible for the first time. DCM checks for parallels for an object only when the entire history of that object is replicated. If the entire history of that object is not replicated, the history in the receiving database might be incomplete and disjointed. The history might result in falsely reporting parallel versions. The entire history is replicated when either the predefined Entire Database transfer set is used, or if the object was a history member of the transfer set.

If parallel checking is performed, and Local Parallel Notification is specified in a transfer set, then for each received object, DCM makes a list of parallel versions that were created in the destination database. Each user who owns or created such a version receives an email. This notice describes the received object and its parallel versions, one of which is owned by the email recipient.


Feedback