Fixes Defects:

CS0003102,CS0003102,CS0003966,PH02243,PH05925,PH10188,PH14795,PH16660,PH17193,PH17266,PH17597,PH17973,PH18122,PH19721,PH20085,PH20800,PH21656,PH21997,PH22017,PI38327,PI42664,PI73696,PI82754,PI90393,PI95706,PI98203



This patch contains the following software changes:


CS0003102:

   Problem: ClearCase clearmake, when executed in a distributed or parallel manner, may exit with "Error 141".  (pipe write failed)

   Fix: It was determined that under some circumstances, clearmake may enter a race condition due to a multithreading condition and writing to pipes.  This condition has been corrected, and clearmake should no longer encounter this specific race condition.


CS0003102:

   Problem: ClearCase Clearmake does not adjust the build concurrency, and it is causing an excessive number of abes and not making appropriate use of abes.

   Fix: Clearmake has been changed to limit the number of abe processes to be equal to the -J value or the number of build server hosts, which ever is smaller.  Previously, clearmake would start abe processes based on the number of build server hosts, regardless off the -J value, and when a build override situation is encountered, not all of the existing abes were terminated, leaving more abe processes around consuming file descriptors.  This change introduces better abe management and limits the number of abes.


CS0003966:

   Problem: ClearCase clearmake, during a distributed build, may fail with "Too many open files" on Solaris, as a result of too many clearmake abe processes starting.   This situation has a greater tendency to occur when a "build override" situation is encountered, which is when a makefile has the CCASE_BLD_HOST variable set so that some targets are directed to specific servers to be built.   

   Fix: clearmake has been changed to limit the number of abe processes to be equal to the -J value or the number of build server hosts, which ever is smaller.  Previously, clearmake would start abe processes based on the number of build server hosts, regardless off the -J value, and when a build override situation is encountered, not all of the existing abes were terminated, leaving more abe processes around consuming file descriptors.  This change introduces better abe management and limits the number of abes.


PH02243:

   Problem: Patch document needed a note indicating that 8.0.0.8  was the last patch for that version

   Fix: Technote  http://www.ibm.com/support/docview.wss?uid=swg27023148     was updated.


PH05925:

   Problem: ClearCase change management integrations (CMI) could fail on Windows when connecting to a change management server with an SSL certificate that expires in year 2038 or later


   Fix: ClearCase CMI has been corrected to handle SSL certificates expiring in year 2038 or later


PH10188:

   Problem: Send and receive buffer size when entered in KB/MB  was not read correctly and creating problem while launching the Multistite applet.

   Fix: Tokenizing the receive & send buffer values solved the problem.


PH14795:

   Problem: After creating a ClearCase snapshot view on Linux using a registered view storage location with a Windows based view server host the view owner is unable to remove the view.

   Fix: The rmview function has been fixed.


PH16660:

   Problem: Using ClearCase ClearTeam Explorer to show CMI activities may result in NullPointerExceptions in RTC Integrated environment.

   Fix: We did a rollback on FILTERING feature which was the root cause for this NULL POINTER EXCEPTION.


PH17193:

   Problem: ClearCase ALBD controlled processes may not start when needed.

   Fix: The ClearCase ALBD process cleanup code was fixed.


PH17266:

   Problem: When creating a new stream and adding non-modifiable components using ClearCase ClearTeam Explorer, the original baseline(s) seem to get lost.

   Fix: ClearTeam Explorer now correctly manages baselines and components.


PH17597:

   Problem: Executing the ClearCase clearprojtool binary creates a duplicate key "Atria " in registry. 

   Fix: ClearCase clearprojtool registry use / management was corrected.


PH17973:

   Problem: ClearCase mainframe TSO client operations may fail with "No such file or directory".

   Fix: The ClearCase mainframe TSO client was modified to use correct syntax.


PH18122:

   Problem: ClearCase MVFS was not correctly forwarding lock key information to the underlying file system, resulting in a lock conflict when writing to the INI file.

   Fix: The lock key is now forwarded to the underlying file system and the write completes successfully.


PH19721:

   Problem: When adding large numbers of files to source control via ClearCase ClearTeam Explorer, some files "disappear" from the expected directories after the operation completes.

   Fix: ClearCase ClearTeam Explorer now correctly adds large numbers of files to source control.


PH20085:

   Problem: When files are added/removed to a web view using the command line or a GUI other than ClearTeam Explorer, the changes may not be reflected in ClearTeam Explorer, particularly if there are any "unusual" issues with the web view (like a checked-out-but-removed file).

   Fix: Client-side code which reads a web view directory, now ignores not-found errors for local copies of files that are known to the server and continues reading.  This resolves the problem.


PH20800:

   Problem: When using ClearCase to build software using Visual Studio 2017 or newer on Microsoft Windows, the build audit may be incorrect.  This would cause some build target's configuration records to be incomplete, and also could cause build targets to fail to rebuild even though another component on which the target depends has changed. 

   Fix: Audit pointer management was corrected.


PH21656:

   Problem: When upgrading the version of ClearCase on a Windows system, a reboot is required to complete the upgrade installation.  After that reboot, the system may crash shortly after restarting.   It may enter a loop of crashing and restarting, in which case it must be booted in safe mode to allow manual manipulation of files in order to work around the problem. 

   Fix: The crash is caused by incomplete cleanup of a previous version which is being replaced during the upgrade.


PH21997:

   Problem: Right clicking on an excluded file in a ClearCase / VS 2017 project throws *8* unhandled exceptions .

   Fix: While debugging we found that we are passing NULL value while accessing the list whithout checking the NULL condition. We just check the NULL condition and it works fine.


PH22017:

   Problem: After installing ClearCase 9.0.2 on Windows 10 or newer, the installation will succeed, but after reboot MVFS filesystem will not be started.    This message is observed in the system event log: The IBM Rational ClearCase Multi-Version FS for NT10.0 x86_64 service failed to start due to the following error:  Windows cannot verify the digital signature for this file. 



   Fix: This was a product packaging error and the MVFS driver in 9.0.2.1 is correctly signed.


PI38327:

   Problem: The ClearCase command "cleartool getlog -around", may miss the first event (if you compare it to a different cleatool getlog command output).

   Fix: Internal file pointer / record management was corrected.


PI42664:

   Problem: ClearCase clearexport_ccase commands may crash when the length of an attribute name+value exceeds an internal buffer size of 4096.

   Fix: During cvt_data file generation, when attribute name and value is copied to buffer having size 4096, checked if total number of characters exceeds 4096. If so, a warning is generated and attribute value is truncated so that it fits into the buffer and would not result in buffer overflow/crash.


PI73696:

   Problem: The ClearCase "cleartool rmtag" command may fail on a network mapped drive due to insufficient return code validation

   Fix: Return code are now validated correctly and "cleartool rmtag" command executes successfully on network mapped drive


PI82754:

   Problem: If a Windows ClearCase CCRC WAN server is installed to a directory without spaces (i.e., not the default c:\Program Files or c:\Program Files (x86) directory),  a ClearCase upgrade, which cause a preserve and restore of the local CCRC WAN server view storage, damages the view storage security information (because the preserve/restore on Windows does not correctly handle the file/dir security information, including ACLs).

   Fix: The CCRC WAN server preserve/restore code was changed to use the Windows robocopy command, which correctly preserves/restores the security information of the local view storage files.


PI90393:

   Problem: A problem associating a ClearQuest record to a ClearCase UCM activity gives an incorrect error message in a Japanese language environment.

   Fix: The error message has been corrected.


PI95706:

   Problem: ClearCase Clearaudit error string - when launched in snapshot view, which is unsupported and documented, was generic and not very informative.

   Fix: The ClearCase Clearaudit error string was updated to inform user about the exact issue.


PI98203:

   Problem: When a file was being moving to "lost+found" directory, file was getting renamed and new filename was exceeding the filename length limit supported by OS.

   Fix: Before moving a file to "lost+found" directory, check if the new filename will exceed max supported filename length limit. If so, then truncate the filename before renaming the file.