Daylight Saving Time produces in an incorrect timestamp when exporting Rational ClearQuest query results to Microsoft Excel or to a text file
This technote identifies an issue that can occur in the IBM Rational ClearQuest Web client when the time zone offset for a date-time field is different from the user's current time zone offset because of Daylight Saving Time (DST) transitions.
This issue is identified as a product defect under APAR PM08377.
Resolving the problem
This problem has been fixed in IBM Rational ClearQuest Web version 220.127.116.11.
When the user logs in, the ClearQuest Web client now determines when their DST transitions occur and from that finds the IANA time zone identifier. This time zone is used for Export and Print procedures and for base ClearCase "ExecuteQuery" and "GetRecords" operations.
When the long date format preference is set, ClearQuest Web 18.104.22.168 includes an appropriate time zone abbreviation with date-time values (such as "EDT") instead of the user's current time zone offset (such as "GMT+4:00").
The user's time zone and offset are also made available to hooks through the session variables "_CQ_WEB_TIMEZONE" and "_CQ_WEB_TZOFFSET". For example, the following hook code retrieves the user's time zone ID and their current time zone offset:
$timezoneID = $session->GetNameValue( "_CQ_WEB_TIMEZONE" ); // e.g. "America/Detroit"
$gmtOffset = $session->GetNameValue( "_CQ_WEB_TZOFFSET" ); // e.g. "GMT-4:00"
More support for:
Web Client (7.1)
Software version: 7.1, 22.214.171.124, 126.96.36.199, 7.1.1, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 7.1.2, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 8.0, 126.96.36.199
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1422042
Modified date: 26 February 2010