Fixes Defects:

PI23043,PI44560,PI65279,PI68209,PI70376,PI74040,PI87042,PI88267,PI92686,PI93110,PI93610,PI95266,PI99133,PM05393,PM78187



This patch contains the following software changes:


PI23043:

   Problem: The Rational Software Architect ClearCase Remote Client extension integration allows model files to be removed using the
"Delete" key from the RSA workspace. This should not be allowed in this perspective and is blocked in the GUI context menu.

   Fix: With this change when Delete key is pressed with multiple selections, the Delete Action will be triggered only for non-model files.   On the GUI context menu, the current functionality is retained. On the context menu of multiple selection, if the selection contains at least one model file, then Remove option is disabled.


PI44560:

   Problem: A MultiSite syncreplica -import may fail on an rmver oplog with the error "string buffer too small."

   Fix: Importing an rmver oplog should no longer hit this error.


PI65279:

   Problem: MultiSite syncreplica import will occasionally fail with "Segmentation Fault" for a mkbaseline oplog having a nonzero value for the num_reorder_ents field.

   Fix: MultiSite syncreplica import will no longer fail with "Segmentation Fault" for such an oplog.


PI68209:

   Problem: ClearCase clearmake may run out of memory when a make file contains a large number of macros.

   Fix: Changes were made to do a better job of freeing up memory when the memory was no longer required and this will allow clearmake to better handle makefiles with a large number of macros.


PI70376:

   Problem: ClearCase clearmake, in an automatic view, incorrectly attempts to contact a VOB looking for derived objects to re-use.

   Fix: ClearCase clearmake was modified to skip checking for derived objects when an automatic view is used.


PI74040:

   Problem: Under certain circumstances, ClearCase omake does not properly handle memory allocation errors and was not freeing up no longer used memory.

   Fix: ClearCase omake was modified to correct one scenario to now exit in the event of a memory allocation error, and was also modified to free up memory for one scenario when the memory is no longer needed.


PI87042:

   Problem: Certain sequences of ClearCase UCM baseline operations could cause a segmentation violation.

   Fix: This fixes a possible segmentation violation during ClearCase UCM baseline operations.


PI88267:

   Problem: In ClearCase ClearTeamExplorer (CTE) the paths shown in the pending changes view may sometimes be incorrect specially when there are major similarities between directory names in the VOB root directory. For example "/vob/a" and "/vob/ab".

   Fix: The fix addresses the path display issue in ClearTeam Explorer's Pending Changes view.


PI92686:

   Problem: A ClearCase database incompatibility was introduced for UCM PVOBs on Windows between versions 9.0.1.0 and 9.0.1.1.

   Fix: This fixes a database compatibility issue introduced on Windows PVOBs between version 9.0.1.0 and 9.0.1.1.  With this fix, databases created on version 9.0.1.0 are now compatible.


PI93110:

   Problem: When you are working in the Rational ClearCase/Microsoft Visual Studio 2017 Integration, you may find that the solution files are not handled correctly.

   Fix: The integration was fixed to properly handle solution files.


PI93610:

   Problem: Corrupted ClearCase view databases could be treated as valid.

   Fix: Fixes issues where corrupt view databases could be treated as valid.


PI95266:

   Problem: ClearCase MVFS used the same locking resource to protect the file disposition flag and the cache state. When a process tried to delete a file with its cache enabled, it acquires a lock to set the file disposition and send a call to the view server. The view server will open the cleartext file and cause the cache to become invalid, this would cause the lock to be acquired again to update the cache state, but the lock is never acquired.

   Fix: Because file disposition does not deal with the actual file content, an exclusive locking resource has been created to protect the cache state, so that the file disposition can be changed regardless of the cache state.


PI99133:

   Problem: The ClearQuest API GetEnabledEntityDefs can return a null value if there are no entity defs selected by the call.  It should return an empty set of entitydefs instead.  This can cause performance and other problems for consumers of the API such as CQ Web, especially if the ClearQuest database table ownership was not configured correctly.

   Fix: The ClearQuest API GetEnabledEntityDefs now returns an empty set of entitydefs in all cases when there are no entitydefs returned by the call.


PM05393:

   Problem: ClearCase triggers firing on deliver_cancel and rebase_cancel are not working as designed in CCRC.

   Fix: ClearCase triggers will now work on deliver_cancel and rebase_cancel.


PM78187:

   Problem: When an IBM Rational ClearCase Unified Change Management (UCM) deliver is in progress and that view is inaccessible, starting a second deliver from a different view on the same streams will allow you to reset the original deliver but will not give any information about the view that started the original deliver. 


   Fix: ClearCase UCM deliver will now give information about the view that started the original delivery.