Fixes Defects:

PI05061,PI05128,PI15885,PI18072,PI21997,PI27347,PI44668,PI44788,PI45277,PI45450,PI46674,PI47193,PI48531,PI48655,PI48860,PI50303,PI50567,PI50590,PM77414



This patch contains the following software changes:


PI05061:

   Problem: When you attempt to remove an IBM Rational ClearCase Unified Change Management (UCM) composite baseline, cleartool.exe may  crash with an application error.

   Fix: Cleartool no longer tries to remove a non-exist baseline from the baseline hash table.


PI05128:

   Problem: IBM ClearCase Perl applications do not properly report new versions of Windows operating systems.

   Fix: The Win32. perl module was updated to properly report new versions of Windows operating systems.


PI15885:

   Problem: When using IBM Rational ClearCase 8.0.1.x and there are more than 30 VOBs hosted on a VOB host, for some platforms (such as 32 bit Solaris),  the vob_scrubber will print "too many open file" errors in the vob_scrubber log.

   Fix: With this change, the file descriptor leak in the vob_scrubber has been corrected.


PI18072:

   Problem: When running the IBM Rational ClearCase command "rcleartool lsact" on a Unified Change Management (UCM) stream, you may see a performance issue when there are a large number of activities on the stream.

   Fix: Incorrect initialization code in the sub command that fetch the full activity list for a stream, even when explicit activities were specified, has been removed.


PI21997:

   Problem: Unexpected Microsoft Windows STOP errors (BSOD) may occur during audited builds on IBM Rational ClearCase.  These errors are more likely to occur if the MVFS parameter UseCacheManager is set to 1.

   Fix: A race condition which allowed process audit data to be read incorrectly has been corrected.


PI27347:

   Problem: Unexpected Microsoft Windows STOP errors (BSOD) may occur during audited builds on IBM Rational ClearCase.  These errors are more likely to occur if the MVFS parameter UseCacheManager is set to 1.

   Fix: A race condition which allowed process audit data to be read incorrectly has been corrected.


PI44668:

   Problem: When you are in an IBM Rational ClearCase dynamic view and cd'd into the vob tag, you may receive an error when running the net use M: command in a view/vob context.

   Fix: IBM Rational Clearcase was modified to show the correct information.


PI44788:

   Problem: When using the IBM Rational ClearCase Remote Client command line interface -- rcleartool -- attempts to use rcleartool mkattr to create or update a string attribute may fail.

   Fix: Fix made to rcleartool to be sensitive to escape characters that must be preserved for subsequent processing.


PI45277:

   Problem: When using the Perl-based integration between IBM Rational ClearCase and IBM Rational ClearQuest on Microsoft Windows, the user's ClearQuest login credentials may be intermittently invalidated if the user name used to log in to Windows is not an exact case-match for the user name stored on the domain.

   Fix: The Windows version of the integration now performs a case insensitive comparison of the user's ClearQuest login credentials.


PI45450:

   Problem: Running a .Net 4.x executable in a IBM ClearCase dynamic view (either as a view private file or under source control) you may encounter a runtime error.

   Fix: IBM Rational ClearCase was modified to avoid the runtime error.


PI46674:

   Problem: IBM ClearCase chtype operations fail with INTERNAL ERROR when ndata versions present.

   Fix: The ClearCase chtype command has been fixed to work correctly when ndata versions are present.


PI47193:

   Problem: A Windows system crash may occur during IBM Rational ClearCase dynamic views with Symantec 12.1.6 and cache manager enabled.

   Fix: A memory leak condition in ClearCase, which could cause a system crash, was corrected.


PI48531:

   Problem: When running a UCM deliver using IBM Rational ClearTeam Explorer, automatic merges may not occur and it would appear that a manual merge must happen. A manual merge is not actually required in this case and the deliver will appear to stop.

   Fix: Fixes a problem in the ClearTeam Explorer where UCM Deliver sometimes stops due to inability perform manual merges in a situation where no manual merge should be required.


PI48655:

   Problem: IBM Rational ClearCase CCRC Wan Server process consumes 14mb memory when it is started up, but over time the memory it consumes keeps increasing steadily. 

   Fix: Memory leaks have been fixed.


PI48860:

   Problem: If you are running an audited build in an IBM Rational ClearCase dynamic view, you may receive a Microsoft STOP error (BSOD) RDR_FILE_SYSTEM.

   Fix: A race condition in the IBM Rational ClearCase MVFS which caused reference to incorrect audit structures has been fixed.


PI50303:

   Problem: If you checkout a file in an IBM Rational ClearTeam Explorer web view before connecting to ClearCase and then try to connect, you will find that ClearTeam Explorer hangs and is unresponsive.

   Fix: Fixes a problem in the ClearTeam Explorer that causes the application to hang when the user navigates to a folder within a view without connecting to the server.


PI50567:

   Problem: When you are using an IBM Rational ClearCase Automatic view, you may find that you do not see an error as expected in the update log when some files do not load using the load rules.

   Fix: During an automatic view load or update operation, failures to retrieve loaded files are now reported in the update log file.


PI50590:

   Problem: When setting the Microsoft prompt to show the remote name on IBM Rational ClearCase Dynamic View,  you may receive an "unknown", instead of the remote name for the drive.

   Fix: IBM Rational ClearCase was modified to show the correct remote name.


PM77414:

   Problem: When using IBM Rational ClearCase and accessing or executing a program in a dynamic view via a Windows symbolic link, Windows may crash with a BSOD in the MVFS. This is when using Microsoft NTFS symbolic link NOT ClearCase symbolic link.

   Fix: IBM Rational ClearCase was modified to avoid BSOD when using Windows Symbolic Link.