Fixes are available
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 10 (8.0.1.10) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 11 (8.0.1.11) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 12 (8.0.1.12) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 13 (8.0.1.13) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0
Rational ClearCase Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearCase Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearCase Fix Pack 16 (8.0.1.16) for 8.0.1
Rational ClearCase Fix Pack 17 (8.0.1.17) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.1.18) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.1.19) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.1.20) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.1.21) for 8.0.1
Rational ClearCase Fix Pack 22 (8.0.1.22) for 8.0.1
Rational ClearCase Fix Pack 23 (8.0.1.23) for 8.0.1
Rational ClearCase Fix Pack 24 (8.0.1.24) for 8.0.1
Rational ClearCase Fix Pack 25 (8.0.1.25) for 8.0.1
APAR status
Closed as program error.
Error description
When using the Perl-based integration between IBM Rational ClearCase and IBM Rational ClearQuest on Microsoft Windows, the user's ClearQuest login credentials may be intermittently invalidated if the user name used to log in to Windows is not an exact case-match for the user name stored on the domain. (Example: "user1" vs. "User1") The Perl integration performs a case-sensitive comparison between a cached login ID and the actual user login ID as part of the validity check. On Windows, this comparison should be case-insensitive.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of the Perl-based integration between IBM Rational * * ClearCase and IBM Rational ClearQuest on Microsoft Windows. * **************************************************************** * PROBLEM DESCRIPTION: * * When using the Perl-based integration between IBM Rational * * ClearCase and IBM Rational ClearQuest on Microsoft Windows, * * the user's ClearQuest login credentials may be * * intermittently invalidated if the user name used to log in * * to Windows is not an exact case-match for the user name * * stored on the domain. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
A fix is available in ClearCase versions 8.0.0.17 and 8.0.1.10
Temporary fix
Comments
APAR Information
APAR number
PI45277
Reported component name
CLEARCASE WIN
Reported component ID
5724G2900
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-07-20
Closed date
2015-12-10
Last modified date
2015-12-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
CLEARCASE WIN
Fixed component ID
5724G2900
Applicable component levels
R800 PSY
UP
R801 PSY
UP
Document Information
Modified date:
17 October 2021