Fixes Defects:

PI11015,PI18840,PI19793,PI20520,PI22258,PI22822



This patch contains the following software changes:


PI11015:

   Problem: When using IBM Rational ClearTeam Explorer rcleartool, nested version selection rules and comments in webview config spec do not work.

   Fix: IBM Rational ClearTeam Explorer rcleartool has been fixed to properly read/use nested version selection rules. Comments in web view config spec are not supported.


PI18840:

   Problem: When IBM Rational ClearTeam Explorer users disconnect from the IBM Rational CCRC WAN Server, the corresponding user session is not terminated on the server.

   Fix: Disconnecting from a CCRC WAN Server in ClearTeam Explorer will now terminate the user session on the server in under five minutes.


PI19793:

   Problem: Users of  ClearCase views exported from a Linux system may see an error when mounting or accessing the view using NFS4, due to a problem with the Linux NFS4 implementation.

   Fix: ClearCase has been modified to return certain values in the attribute information for exported directories in a way which is consistent with what is expected by the Linux NFS4 implementation.


PI20520:

   Problem: IBM Rational CCRC Server and CCRC clients with locale (LANG) set to non-ASCII on both (e.g: EN_US.UTF-8 or EN_GB.GB18030) generate an error.

   Fix: The fix resolves the encoding issue on the CCRC WAN server side and it is transparent to customers (there is no additional effort required by customers).


PI22258:

   Problem: When integrating IBM Rational ClearCase Unified Change Management (UCM) with IBM Rational Team Concert (RTC) via the Change Management Integration, multiple UCM activities cannot be associated with a single RTC Work Item.

   Fix: The Change Management Integration (CMI) will now allow multiple activities on the same stream to be associated with an RTC Work Item or ClearQuest record.


PI22822:

   Problem: When using IBM Rational ClearCase remote dynamic and remote NFS4 view storage, customers would see EPERM errors on checkout.

   Fix: The problem was caused by an extra open attempt being sent to the NFS4 server. The cleartext file creation was modified to prevent that condition.