Fixes are available
Rational ClearCase Fix Pack (7.1.2.6) for version 7.1.2
Rational ClearCase Fix Pack (8.0.0.2) for version 8.0
Rational ClearCase Fix Pack (7.1.1.9) for version 7.1.1
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
The IBM Rational ClearCase command 'cleartool lsstream -ancestor -in <PROJECT SELECTOR>' incorrectly cascades the output in a manner such as the following: ----- m:\>cleartool lsstream -ancestor -in FirstProject@\ucmPVOB RootFolder folder 'Root folder' FirstProject project *FP_Integration stream RootFolder folder 'Root folder' FirstProject project *FP_Integration stream FP_Development stream ----- This can become unintelligible with deeply nested projects. The formatting is also inconsistent with similar ClearCase commands such as 'cleartool lsstream -ancestor -invob <VOB>' which left-justifies each 'RootFolder' node as follows: ----- m:\>cleartool lsstream -ancestor -invob \ucmPVOB RootFolder folder 'Root folder' FirstProject project *FP_Integration stream RootFolder folder 'Root folder' FirstProject project *FP_Integration stream FP_Development stream ----- Steps to reproduce the issue: 1) Create a ClearCase UCM project consisting of at least one integration stream and two child streams. 2) Run 'cleartool lsstream -ancestor -in <PROJECT SELECTOR>. WORKAROUND: Consider using a small script to re-parse the data into a more readable format. One example of a small perl script on a Windows platform that could be utilized as a starting point can be seen below. EXAMPLE ancInProj.pl script (call via 'perl ancInProj.pl projectName@\pvob'): ----- foreach(`cleartool lsstream -anc -in $ARGV[0]`) { $padding = ($_ =~ m/(\s*)RootFolder/) ? $1 : $padding; $_ =~ s/^$padding//; print $_; } -----
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** The IBM Rational ClearCase command "cleartool lsstream -ancestor -in ?PROJECT SELECTOR?" incorrectly cascades the output.
Problem conclusion
A fix is available in ClearCase versions 7.1.1.9, 7.1.2.6 and 8.0.0.2
Temporary fix
Comments
APAR Information
APAR number
PM54324
Reported component name
CLEARCASE WIN
Reported component ID
5724G2900
Reported release
712
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-13
Closed date
2012-04-05
Last modified date
2012-04-05
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:
05 April 2012