Fixes are available
Rational ClearCase Fix Pack 6 (8.0.1.6) for 8.0.1
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 7 (8.0.1.7) for 8.0.1
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 8 (8.0.1.8) for 8.0.1
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 9 (8.0.1.9) for 8.0.1
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
Summary: ---------- While rebasing a stream which has foundations on multitple composite baselines the user may receive multiple occurrences of cleartool: Warning: Unable to get explicit composite baseline which has unclear meaning and makes the other command output extremely difficult to read. ---------- Steps to reproduce: This issue is reproducible only in very complex UCM environments, so full details on reproducing it from scratch are omitted. 1. The UCM must be configured using composite baselines from multiple other projects. 2. The other projects must be configured using common shared components Rebase a stream onto a composite baseline (Prj_A_v7r1m2f9_Comp_A) that overrides or augments a component (Comp_A) foundation in the current configuration. If this component contains a dependency on a component (SubComp_1) that is already in the stream's configuration through dependency of a composite baseline (Prj_B_v7r1m2f8_Comp_B) in some OTHER component (Comp_B) AND Prj_A_v7r1m2f9_Comp_A and Prj_B_v7r1m2f8_Comp_B depend on different baselines of SubComp_1, then 'rebase' shall detect a 'conflict' and log the following: --------------------- cleartool: Error: Conflicts in configuration: Component 'SubComp_1@/vobs/pvob' baselines: 'v7r1m2f9_Prj_A_SubComp_1@/vobs/pvob' (member of 'Prj_A_v7r1m2f9_Comp_A@/vobs/pvob') 'v7r1m2f8_Prj_B_SubComp_1@/vobs/pvob' (member of 'Prj_B_v7r1m2f8_Comp_B@/vobs/pvob') cleartool: Error: Unable to rebase stream 'prj_1.0_int'. --------------------- Now suppose there is also a Comp_C developed in Prj_C, which also depends on SubComp_1 but the foundation in use by stream 'prj_1.0_int' also depends on baseline 'v7r1m2f8_Prj_B_SubComp_1' Then our attempt to rebase stream 'prj_1.0_int' onto baseline 'Prj_A_v7r1m2f9_Comp_A' of component 'Comp_A', instead of failing with --------------------- cleartool: Error: Conflicts in configuration: Component 'SubComp_1@/vobs/pvob' baselines: 'v7r1m2f9_Prj_A_SubComp_1@/vobs/pvob' (member of 'Prj_A_v7r1m2f9_Comp_A@/vobs/pvob') 'v7r1m2f8_Prj_B_SubComp_1@/vobs/pvob' (member of 'Prj_B_v7r1m2f8_Comp_B@/vobs/pvob','Prj_C_v7r1m2f8_Comp_C@/vobs/ pvob') cleartool: Error: Unable to rebase stream 'prj_1.0_int'. --------------------- or --------------------- cleartool: Error: Conflicts in configuration: Component 'SubComp_1@/vobs/pvob' baselines: 'v7r1m2f9_Prj_A_SubComp_1@/vobs/pvob' (member of 'Prj_A_v7r1m2f9_Comp_A@/vobs/pvob') 'v7r1m2f8_Prj_B_SubComp_1@/vobs/pvob' (member of *** multiple composite baselines ***) cleartool: Error: Unable to rebase stream 'prj_1.0_int'. --------------------- will actually fail with --------------------- cleartool: Error: Conflicts in configuration: Component 'SubComp_1@/vobs/pvob' baselines: 'v7r1m2f9_Prj_A_SubComp_1@/vobs/pvob' (member of 'Prj_A_v7r1m2f9_Comp_A@/vobs/pvob') 'v7r1m2f8_Prj_B_SubComp_1@/vobs/pvob' cleartool: Warning: Unable to get explicit composite baseline cleartool: Error: Unable to rebase stream 'prj_1.0_int'. --------------------- If the rebase is introducing conflicts in multiple components, and/or the dependency paths of common components are the output be quickly becomes useless / unreadable. Workaround: Write some scripting to extract the useful parts of the message from the useless parts.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of IBM Rational ClearCase UCM. * **************************************************************** * PROBLEM DESCRIPTION: * * While rebasing an IBM Rational ClearCase stream which has * * foundations on multiple composite baselines, the user may * * receive multiple occurrences of the message * * "cleartool: Warning: Unable to get explicit composite * * baseline" * * which has unclear meaning and makes the other command output * * extremely difficult to read. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
A fix is available in ClearCase versions 8.0.0.13 and 8.0.1.6 More detailed error reporting can be enabled by setting a special environment variable, CCASE_EXPANDED_MSGS to any non-empty string. If CCASE_EXPANDED_MSGS is empty or non-existent, the behavior and messages are unchanged.
Temporary fix
Comments
APAR Information
APAR number
PM95042
Reported component name
CLEARCASE UNIX
Reported component ID
5724G2901
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-14
Closed date
2014-12-16
Last modified date
2014-12-16
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:
02 November 2021