Fixes Defects:

PI19733,PI24698,PI25448,PI51355,PI72025,PI73234,PI75108,PI75470,PI76489,PI76793,PI77042,PI77492,PI77782,PI77954,PI78319,PI78918,PI79130,PI80487,PI80609,PI81268,PI82010,PI82359,PI83758



This patch contains the following software changes:


PI19733:

   Problem: When using a makefile to overwrite a file using the move command in a ClearCase Dynamic View you may notice that the source file was not removed.

   Fix: ClearCase Multi Version File System was changed to enable wniked-in files to be overwritten on move operations.


PI24698:

   Problem: When using the Rational ClearCase File Service (CCFS) as the interoperability solution to access Unix-hosted VOBS from Windows you may encounter a "Permission denied" error.

   Fix: Windows now skips permission denied ports.


PI25448:

   Problem: When performing audited builds in IBM Rational ClearCase dynamic views on Microsoft Windows, the audit record may not be complete.

   Fix: Changes were made to correct the auditing of non-cached reads.


PI51355:

   Problem: When searching for files in a ClearCase dynamic view, using the Windows Explorer Search feature, you may not see any results.

   Fix: Changes were made on ClearCase Network Provider to return correct path information.


PI72025:

   Problem: Creating or deleting hyperlinks that span VOBs (common in a UCM setup) in IBM Rational ClearCase can lead to a situation where two processes are waiting on each other for a lock on one of the VOB databases. This will lead to the Dead Man Lock Timeout to be triggered, making one of the two operations to fail.

   Fix: A ClearCase db transaction will be suspended and restarted for cross vob hlinks.


PI73234:

   Problem: The ClearCase web-based UCM/ClearQuest integration was unable to work on ClearQuest records that contained security contexts where the user was not a member of one or more of those contexts.

   Fix: The web-based UCM/CQ integration can now work on ClearQuest records that contain security contexts where the user is not a member of one or more of those contexts.


PI75108:

   Problem: Users of ClearCase dynamic views may see messages reporting stale transaction ids in the mvfs_log log file.  Unexpected application I/O errors or hangs may coincide with these messages.

   Fix: The logic for how the MVFS handles certain transient errors in communicating with a view_server process has been corrected.


PI75470:

   Problem: ClearTeam Explorer can produce the following error when attempting a directory merge when in a webview:
"As a result of a directory merge operation, one or more resources, requiring a merge, have been removed"

   Fix: A directory merge in a webview will no longer result in the error.


PI76489:

   Problem: A ClearCase checkout using the ctcmd.pm module fails with an abort.

   Fix: A ClearCase checkout using the ctcmd.pm module no longer aborts.


PI76793:

   Problem: Intermittently a ClearCase shipping_server may hang after executing a shipping order or during syncreplica -export -fship

   Fix: The shipping_server will now complete its actions without hanging.


PI77042:

   Problem: ClearCase users cannot create or use automatic views if the "http_proxy" environment variable is set.

   Fix: Automatic views now work using direct connections to the CCRC WAN server even when the "http_proxy" environment variable is set.

NOTE:  Automatic views do not support proxies, even if ClearTeam Explorer is configured to use proxies.


PI77492:

   Problem: A user is unable to connect to a ClearCase Remote Client WAN server, if the login URL contains a trailing  white space.

   Fix: Trailing white space is now removed from URLs in all cases.


PI77782:

   Problem: The ClearCase UCM/ClearQuest integration was creating multiple ClearQuest web sessions when using ClearTeam Explorer with a web-based view.

   Fix: The UCM/ClearQuest integration now uses fewer ClearQuest web sessions when using ClearTeam Explorer with a web-based view.


PI77954:

   Problem: Removing a ClearCase UCM stream while a remote site has a view attached (to the stream) causes the db dumper to fail. 

   Fix: The db dumper has been fixed.


PI78319:

   Problem: ClearCase customers are unable to use dynamic views because MVFS is not loaded on Windows 10 if Device Guard is enabled.

   Fix: The ClearCase MVFS driver was changed to adopt the requirements imposed by Device Guard.


PI78918:

   Problem: A ClearCase "RMSTREAM" of "Feature Level 5" stream after raising VOB to "Feature Level 7" FAILS WITH "ERROR FROM VOB DATABASE" FOR UCM PROJECT VOB.

   Fix: Feature Level 7 VOBs now can handle "rmstream" command from Feature Level 5.


PI79130:

   Problem: The ClearCase "xclearcase" or "xlsvtree" graphical interfaces (on Linux hosts) will hang when started with an invalid path.

   Fix: ClearCase exit handling code was fixed.


PI80487:

   Problem: A ClearCase Syncreplica -import of the modstream_cspec oplog generated by creating a child stream fails with a segmentation fault in a sibling that has removed the parent stream.

   Fix: The replay code has been modified to properly store the modstream_cspec oplog while skipping its replay if the parent stream is not found in the importing replica.


PI80609:

   Problem: ClearCase customers may experience a system crash when accessing MVFS files.

   Fix: This issue has been resolved.


PI81268:

   Problem: When ClearCase Explorer has been used to access a UCM view, but then gets left idle for a long period of time, then on resumption it hangs for a short period and then gives:
"Trouble communicating with VOB database \<PVOB-tag>".

   Fix: Users will not encounter such error messages when ClearCase Explorer client is left idle for a long period of time.


PI82010:

   Problem: The outdated Microsoft Visual Studio 2005 Visual C++ runtimes are distributed with ClearCase and ClearQuest as those products have components that depend on them.

   Fix: All dependencies on the Microsoft Visual Studio 2005 Visual C++ runtimes have been removed from ClearCase and ClearQuest, and those runtimes are no longer installed


PI82359:

   Problem: ClearCase processes crash when executed by a Windows account that is a member of a group represented by long Windows SID, such as SIDs for non-domain accounts linked to a Microsoft account  

   Fix: ClearCase processes no longer fail with such accounts, but ClearCase will ignore any group (behave as if the user is not a member of the group)  represented by a long Windows SID.


PI83758:

   Problem: The ClearCase db_server processes can behave erratically if single token lines are placed in the db.conf file.

   Fix: The db_server processes properly parse single token lines in the db.conf file.