Fixes Defects:

PI18297,PI58632,PI59089,PI64278,PI65782,PI68289,PI68935,PI70235,PI70255,PI70333,PI70543,PM98062,PM98488



This patch contains the following software changes:


PI18297:

   Problem: After raising a VOB family to Feature Level 8, the ClearCase view_server logs show a warning on chmaster/protect events for new UCM types: "Unexpected vob event on vobserver."

   Fix: The view_server will no longer log warnings for these events for the new UCM types.


PI58632:

   Problem: When opening a Visual Studio (VS) project created without a solution file, the ClearCase (CC) plugin is not available in Visual Studio 2013-2015.

   Fix: The CC-VS integration was not installed correctly, that has been fixed.


PI59089:

   Problem: In the ClearCase Knowledge Center, the ClearCase section Administering the CCRC WAN server > Configuring ClearQuest integration with ClearCase UCM topic states that:  "A sample ClearQuest database map file that you can use as a template is installed here: clearcase_home/config/ccrc/ClearQuest-db-mapfile.conf.sample."

   Fix: The correct statement is: "A sample ClearQuest database map file that you can use as a template is installed here: clearcase_home/config/ccrc/cq-db-mapfile.conf.sample."


PI64278:

   Problem: When performing a distributed or parallel build using the ClearCase clearmake utility, the build may fail with automated build executor (abe) process errors.

   Fix: Code that checks automated build executor (abe) process ids has been fixed.


PI65782:

   Problem: When using ClearTeam Explorer (CTE) and entering a directory for the first time, it can take a very long time to list the content. This is most visible if there is a huge number of files, symlinks or sub-directories.

   Fix: There is improved performance especially when browsing parents with large number of symlinks underneath them.


PI68289:

   Problem: When you are working in the ClearCase and Visual Studio 2013 integration, you may find that the ClearCase context menu items are greyed out after performing your first ClearCase operation.

   Fix: The CC-VS integration was not installed correctly, that has been fixed.


PI68935:

   Problem: ClearCase checkin failure due to a missing source container reports cleartext path.

   Fix: The source container is now correctly included in the error message.


PI70235:

   Problem: When working in the Rational ClearCase ClearTeam Explorer (CTE), you may find that doing a "merge to" in the CTE Version Tree will launch the Diffmerge GUI and will not detect the merge as a "trivial merge".

   Fix: A new preference is introduced which will let the user control this behavior. And by default the merges from Version Tree will be done automatically.
Preference location: Team->IBM Rational ClearTeam Explorer->Integration->Compare/Merge


PI70255:

   Problem: When using the ClearCase/ClearQuest (CC/CQ) UCM integration through ClearQuest Web, there is a login error when trying to view a change set.

   Fix: Change sets can now be viewed in ClearQuest Web using the CC/CQ UCM integration.


PI70333:

   Problem: When using the Change Management Integration with ClearQuest some CMI provider errors were not appearing in the cmi_log and required tracing to properly debug.

   Fix: CMI provider errors that were previously not appearing in the cmi_log are now properly logged.


PI70543:

   Problem: When working in the ClearCase integration with Visual Studio 2015, you may find that the application crashes if you try to close a view private file that is either a .c or .h file in Visual Studio.

   Fix: Faulty string manipulation has been fixed.


PM98062:

   Problem: If a stream in a replicated UCM project VOB has "POLICY_CHSTREAM_UNRESTRICTED" enabled, then users at multiple sites are able to upgrade it to incrementally/fully labeled which causes multiple labels to be created/attached and the label status becomes "unavailable".

   Fix: Mastership will be checked if POLICY_CHSTREAM_UNRESTRICTED is enabled.


PM98488:

   Problem: When running the ClearCase cleartool protectvob command against an ClearCase VOB stored over NFS, you may encounter an  error if the hostname of the storage device and the root of the NFS share are greater than 64 characters combined.

   Fix: Faulty string manipulation has been corrected.