Fixes Defects:

PM39111,PM50299,PM64043,PM67902,PM76505,PM76509,PM77216,PM77795,PM78704,PM79080,PM79091,PM79892,PM80242



This patch contains the following software changes:


PM39111:

   Problem: In ClearQuest Web, when using the "DieWithCustomMessage" function in a field value change hook , its web dependent field does not update when clicking "OK" on the custom message window popup.

   Fix: When using the "DieWithCustomMessage" function in a ClearQuest Web field value change hook, its web dependent field can now be updated with a custom message window popup.


PM50299:

   Problem: A failed login (typo) using the ClearCase  / ClearQuest (V2) base integration on a Korean locale with CQ Web (CQCC_CQWEB_ONLY) causes a parsing error and then the login prompt no longer appears.

   Fix: After a failed login using the ClearCase  / ClearQuest (V2) base integration on a Korean locale, a CQ Web login dialog now pops-up requesting the user to renter their username / password.


PM64043:

   Problem: ClearQuest Web is not parsing some characters (for example, Vertical Tab-VT) into valid XML when using OSLC to pull information.

   Fix: ClearQuest Web now parses these characters into valid XML.


PM67902:

   Problem: In ClearQuest Web, the GSU_CQXE_SubmitRecord function does not work properly when the pre-populated  field value is a sub-string of " <Field><Name><![CDATA[ " or " ]]></Name><Value><![CDATA[ " or " ]]></Value></Field> ".  None of the fields on the new cloned record are populated.

   Fix: The GSU_CQXE_SubmitRecord function will now work properly on ClearQuest Web.  All the fields on the new cloned record are populated.


PM76505:

   Problem: When the Rational  MultiSite shipping server encounters a connection or other TCP/IP socket error on Microsoft Windows, an incorrect error message is printed in the shipping server logs.

   Fix: Rational MultiSite shipping server now correctly logs (in the shipping server logs) connection and other TCP/IP socket errors on Microsoft Windows.


PM76509:

   Problem: Rational MultiSite shipping server failed to send packet file due to the "deferred behavior" introduced from MicroSoft Windows 2008 server OS.  Even if with a "good" binding port,  socket connection could still fail for <b>WSAEADDRINUSE</b> error.

   Fix: MultiSite shipping server can now handle the "deferred bind on connect" behavior introduced in MicroSoft Windows 2008 server OS.


PM77216:

   Problem: In the ClearQuest Web 7.1.2.x integration with Rational Team Concert 3.x or Rational Team Concert 4.x deployed on WebSphere Application Server,  creating a ClearQuest query gadget with Internet Explorer 8 and running a selected query will show a "403 Error" and display no results.

   Fix: After creating a ClearQuest query gadget with IE8 in the ClearQuest Web / Rational Team Concert integration, running a selected query will now display all results.


PM77795:

   Problem: When using the "Browse..." button to associate a record to a ClearQuest Web form via a query, the button does not work when trying to do it a second time.

   Fix: The ClearQuest Web "Browse..." button works normally when trying to associate a record via a query.  You can now do it more than once.


PM78704:

   Problem: ClearQuest record type families group entities with common fields together for querying across records of different types.  If any of those common fields have database names which are different than the default value, then those queries may fail.  This is only the case when the field is used for an "in" type of sql query filter.   For example:  if you have the field name "ucm_stream_object" which has a database field name of "ucm_stream_object_1", a query on the record type family All_UCM_Activities will fail if you filter on that field.

   Fix: ClearQuest has been fixed to filter on the actual database field name instead of the visible field name as defined in the record type family.


PM79080:

   Problem: In ClearQuest Web, if your schema has the same field repeated on more than 1 tab, changing it's value does not update on all tabs until the record is saved/refreshed.  As example:  if you have the same date/time field "DUE DATE" on multiple tabs, and you change it on one tab, after you go to the other tab, "DUE DATE" will still have the old value.

   Fix: ClearQuest Web now immediately changes the field value on all the tabs where it appears.


PM79091:

   Problem: During periods of heavy usage, ClearQuest Web may experience "Out of Memory" exceptions, become unresponsive, and prevent users from logging in.  ClearQuest Web sometimes does not recover from this condition in a timely manner and often requires an administrator to manually kill the ailing cqrpc.exe process where the problem occurred.

   Fix: When "Out of Memory" exceptions occur in ClearQuest Web, this condition is now detected and the ailing cqrpc.exe process is recycled.  This means CQ Web users performing operations in the bad cqrpc.exe, as well as new users, are routed to a new cqrpc.exe process.


PM79892:

   Problem: ClearQuest Web 7.1.2.x date field values are not displayed in a query result sets if your CQ Web server is on a Chinese or Korean locale.

   Fix: ClearQuest Web 7.1.2.x date field values now display correctly in query result sets for Chinese and Korean locales.


PM80242:

   Problem: ClearQuest Web sometimes incorrectly collects information about lost record changes and throws an exception even when changes have not actually been lost.

   Fix: A ClearQuest Web fix has been made to properly throw the 'CRVSV1100E The changes to the following resource are lost due to a server problem' exception when changes actually have been lost.