Fixes are available
Rational ClearCase Fix Pack 09 (7.1.2.9) for 7.1.2
Rational ClearCase Fix Pack 05 (8.0.0.5) for 8.0
Rational ClearCase Fix Pack 14 (7.1.2.14) for 7.1.2
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearCase Fix Pack 15 (7.1.2.15) for 7.1.2
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 16 (7.1.2.16) for 7.1.2
Rational ClearCase Fix Pack 17 (7.1.2.17) for 7.1.2
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 18 (7.1.2.18) for 7.1.2
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 19 (7.1.2.19) for 7.1.2
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0
APAR status
Closed as program error.
Error description
When you change the Extended Naming Suffix in the IBM Rational ClearCase Control Panel's MVFS tab from @@ to ?? on a Microsoft Windows 32-bit operating system, you will see the following results in both a dynamic and snapshot view when running a cleartool ls ?file_name? C:\views\?view?\?vob?\dir1?cleartool ls foo.c foo.cc??\main\br1\2 RULE: ?your config spec rule? You receive incorrect results when performing the same operation on a windows 64 bit operating system: C:\views\?view?\?vob?\dir2?cleartool ls bar.c bar.c@@\main\br2\2 RULE: ?your config spec rule? WORKAROUND: None.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Changing the Extended Naming Suffix was not working on 64-bit Windows machines. So, the default suffix (@@) would still be in effect. This was due to the particular Windows registry location that was being used for this configuration value.
Problem conclusion
This problem is fixed in ClearCase 7.1.2.9 and 8.0.0.5. Please refer to tech note #1618052 for information regarding properly reconfiguring the desired non-default suffix after upgrading to either of these versions from a preceding version.
Temporary fix
Comments
APAR Information
APAR number
PM56094
Reported component name
CLEARCASE WIN
Reported component ID
5724G2900
Reported release
712
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-16
Closed date
2012-12-15
Last modified date
2012-12-15
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
R712 PSN
UP
Document Information
Modified date:
15 December 2012