Fixes Defects:

PM80884,PM80982,PM81826,PM84648,PM84918,PM85562



This patch contains the following software changes:


PM80884:

   Problem: ClearCase cleartool relocate is not duplicating attributes that are being stored on branch types and label types.

   Fix: ClearCase cleartool relocate now duplicates attributes that are placed on branch and label types.


PM80982:

   Problem: Rational ClearTeam Explorer incorrectly handles cases in which a user removes the data for a particular version (using "cleartool rmver -force -data -ver <version> <element>") and then tries to open that version in ClearTeam Explorer (for instance, from the vtree).

Under these circumstances, the local copy of the latest version loaded into the view ends up renamed, and appears hijacked.  The user must run an update with the "replace hijacked files" option to recover.

   Fix: ClearTeam Explorer now correctly handles the situation in which version data has been removed by the user.  A message is displayed to the user, and the latest version in the view is not modified.


PM81826:

   Problem: When you run "lsof /proc/locks" on a Suse Linux Enterprise System 10 server with IBM Rational ClearCase MVFS installed, you experience a kernel panic.

   Fix: This release fixes a problem in which the Linux kernel would panic when running lsof on /proc/locks.


PM84648:

   Problem: After checked in of an element via the IBM Rational Base ClearCase/ClearQuest V2 integration, you may receive and error:

Tk::Error: element "Name/A and B (all)" already exists

   Fix: IBM Rational Base ClearCase/ClearQuest V2 Integration does a refresh of the query name list to resolve the issue.


PM84918:

   Problem: In ClearCase, a cleartool rebase -complete may fail with deadman lock timeouts in a UCM environment with multiple project VOBs.

   Fix: This fix ensures that cleartool does not open read transactions in multiple VOBs at the same time, thus preventing deadlocks.


PM85562:

   Problem: Reformatting a VOB or making a new replica on ClearCase 7.1.2 and later may fail with an out-of-memory error.

   Fix: The ClearCase db_dumper program was fixed to manage memory more efficiently.