Fixes Defects:

PM48938,PM56094,PM59537,PM66907,PM67147,PM67399,PM68052,PM68213,PM68658,PM68896,PM69279,PM69503,PM70374,PM70948,PM71714,PM72260,PM72979,PM74119,PM76372



This patch contains the following software changes:


PM48938:

   Problem: When a time out occurs in a communication from ClearCase dynamic view client to the view server, then there might be EIO errors in the system log on the client and performance of the view server process could degrade.

   Fix: Fixes a problem in ClearCase which leads to degraded performance of the view server process and EIO errors in the system log of the ClearCase dynamic view client machine.


PM56094:

   Problem: Changing the Extended Naming Suffix was not working on 64-bit Windows machines. So, the default suffix (@@) is still in effect.

   Fix: Corrects a Clearcase problem where a registry key was redirected, so it was invisible to MVFS. The registry key was changed to a nonredirected location.


PM59537:

   Problem: ClearCase and ClearQuest removed the original MSI packages used to install 3rdParty components, upon cleanning up the Windows MSI cache, the packages had problems to perform Installation Manager Operations.

   Fix: Updated the ClearCase / ClearQuest to keep a copy of the original MSI packages inside the Install directory in case the machine's MSI cache is cleared, in this situation the MSI system will have the original MSI path and prevent problems on the Installation Manager Operations.


PM66907:

   Problem: mklbtype -acquire -global allows you to acquire a lbtype that is locked
The end result is a unlocked global lbtype with a locked local copy

   Fix: An inconsistency in the handling of locked label types was fixed; if the client type is locked, it is reported as not acquirable, and the operation continues with other types.


PM67147:

   Problem: When attempting to create a Managed Code "wrapper" for the CCPolicy put_value() method, there seems to be no way to get Visual C++ 2010 to accept the CCPolicy::put_value method.

   Fix: The definition of the CCPolicy put_value variable was changed from BSTR* to BSTR, to correct a problem with use of that method with some compilers.


PM67399:

   Problem: ClearCase Automation library crashes when called from Multi-threaded code

   Fix: A race condition caused by incorrect locking was fixed in the ClearCase Automation Library.


PM68052:

   Problem: The ClearCase registry may contain files with .new and .old extensions.

   Fix: This fix attempts to clean up these .new and .old registry files when the albd_server is starting, by restoring the registry file corresponding to the .new or .old file, and then removing the .old and .new files.


PM68213:

   Problem: The IBM Rational ClearCase type manager for text files (text_file_delta) can handle individual lines up to 8000 bytes or characters in length. Normally if a user attempts to check in a text file containing a line over 8000 characters an error will be presented and the checkin will fail. In a case where a text file is checked in containing only 7998 bytes and no newline character the checkin will also fail.

   Fix: A problem in an edge case when calculating line length in the text_file_delta type manager has been corrected.


PM68658:

   Problem: ClearCase online help might fail to launch properly after being used once, the system will throw back an error about library relocation.

   Fix: Updated the underlying runtime to a version that correctly handles the library relocation.


PM68896:

   Problem: User will see label of type "label_name" already on element error when mklabel recursively if some branch is locked with -nuser while the user is not in the -nuser list.

   Fix: A change was made in the transaction handling of certain use cases of cleartool mklabel, to prevent incorrect error messages.


PM69279:

   Problem: Lock manager tables can become corrupt and non-recoverable without manual intervention.

   Fix: Certain system-level error conditions can trigger this defect; sanity checking was added in the code to avoid the possible deadlock.


PM69503:

   Problem: After manually selecting one or more file/folder elements in the "ClearTeam Details" tab in the ClearCase Remote Client (CCRC)/ClearTeam Explorer (CTE), and then changing the sort criteria, results in the selected elements being different ones from the initial ones.

   Fix: In CCRC/CTE, the current selection in the Details view is now maintained when the columns are resorted.


PM70374:

   Problem: Clearmake failures occur when the view_db_crs file grows past 2 GB.

   Fix: The maximum size of the view_server's configuration record file was increased from 2Gb to 4Gb.


PM70948:

   Problem: The IBM Rational ClearCase Information Center describes how to use a script to clean up logfiles older than 30 days on the CM Server. For 7.1.2.x releases, the script does not exist in the product location mentioned in the documentation.

   Fix: The cleanup script is now installed in the location mentioned in the ClearCase Information Center.


PM71714:

   Problem: When running an IBM Rational ClearCase server on Microsoft Windows 2008 or 2008 R2, a sporadic port allocation failure may occur. 

   Fix: Logic was added to correctly interpret winsock errors in certain conditions on Windows 2008 and 2008 R2.


PM72260:

   Problem: SQUID tracing does not work through the CCBE.

   Fix: A problem with the logging calls used in the server code was corrected.  Please refer to technote #1127287 for additional details on correctly enabling tracing.


PM72979:

   Problem: Using the IBM Rational ClearCase Remote Client (CCRC) plugin to migrate to Rational Application Developer (RAD) 8.x from Rational Software Architect (RSA) 7.5.x succeeds, but a blocking dialog showing a property error and requiring additional user intervention appears.

   Fix: The property is now being fetched when needed resulting in no blocking error dialog.


PM74119:

   Problem: The Microsoft patch KB2633952-v2 can cause a condition with some eastern Asian timezones where time conversions to GMT are off by one hour in non summer months (months correlated with daylight savings times in other zones where DST is honored).  As example this would convert a Tokyo timezone GMT+8 instead of GMT+9 and since ClearQuest saves dates in GMT these times may be off by one hour.  NOTE - This not a problem with ClearQuest 8.0.0.x.

   Fix: The ICU libraries used to determine date/time values have been updated in ClearQuest and ClearCase to handle this Windows update.


PM76372:

   Problem: When a user intends to start ClearCase Mainframe Connectors (CCz) rccTSOServer in certain environment where more than one network adapters are configured, sometimes addrinfo list returned from  getaddrinfo() has IPV4 address as the first one and IPV6 address as the second one. But if IPV6 network is not configured well, socket creation will fail using IPV6 protocol and exception is thrown. And then rccTSOServer has no opportunity to create socket using IPV4 protocol. So at last rccTSOServer will fail to start.

   Fix: When socket creation  fails using IPV6 protocol, CCz  rccTSOServer does not throw exception any more while we return with an error code and then  rccTSOServer can have an opportunity to create socket using IPV4 protocol.