Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.

Why should I lock my VCM session?

Why should I lock my VCM session?

It should be seen as a best practice process to lock a VCM Session.
The reason for this is that when running a VCM Promote, Rebase or Replicate session, there is a clear expectation that the target view state remain unchanged for those files, CRs etc which are participating in the merge.  If these change before the session is committed, then the actual commit will fail and throw exceptions.

To ensure that the target state is unchanged when a VCM compare is run, the administrator should lock the target items that contribute to differences and should break other user locks if necessary during the session.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2015-12-17 16:23
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.