PM45246: Invalid baselines created by Baseline Dependency Editor (no change sets)

Rational ClearCase Fix Pack 07 (7.1.2.7) for 7.1.2
Rational ClearCase Fix Pack 03 (8.0.0.3) 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

• Using the Baseline Dependency Editor to create a new composite
  component can result
   in new baselines in the rooted components it depends on, which
  do not capture the
   change sets of earlier baselines in the stream.
  
  When a component has been modified and baselined in a stream
  AND since the last baseline the stream has been rebased onto a
  new foundation for that component
  then creating a new composite baseline which depends on this
  component will create a new baseline for it
  and the new baseline will not have any change sets.
  
  Impact:
  
  1. When delivering from this stream, the preview dialog will
  show that ALL activities in the stream need to be delivered.
  That is, already delivered activities will show as needing to be
  delivered again.
  
  2. Upgrading the component baseline to fully labeled applies the
  label to the incorrect version of files.
  
  Steps to Reproduce:
  
  Simplest Case.
  Start with a stream that has its foundation on a single
  component (CompA), which it has modified.
  Its foundation should be NOT on the latest baseline in the
  stream from which it takes its foundations.
  
  1. 'Make Baseline' to make sure all changes are baselined.
  2. Rebase / Configure to add foundations on two other components
    i)  CompB which can be another rooted component, any baseline,
  and can remain non-modifiable
    ii) CompC which will hold composite baselines - use the
  INITIAL_ baseline of the component
  3. Use Baseline Dependency Editor to make CompC depend on CompA
    This will create one new baseline only, in CompC
  4. Rebase the stream onto the latest CompA baseline in the
  stream from which it takes its foundations.
  5. Use Baseline Dependency Editor to make CompC depend on CompB
    This will create two new baselines: one in CompA to eclipse
  the new foundation, and the second in CompC to capture the new
  dependency relationshisp.
  
    The problem is that the baseline in CompA does not capture the
  change sets of earlier baselines in the stream.
  
  Workaround:
  
  1. Remove the composite baseline and the incorrectly created
  baselines, then
  
  2. Make the new dependency using the command line
   cleartool mkbl -comp CompC -adepends CompB ...
  
  OR
  
  2. Make Baseline(s)  [Creates any foundation eclipsing baselines
  as a separate step]
  3. Make the new relationship with Baseline Dependency Editor
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Using the Baseline Dependency Editor to create a new
  composite component can result in new baselines in the
  rooted components it depends on, which do not capture the
  change sets of earlier baselines in the stream.
  

Problem conclusion

• A fix is available in ClearCase version 8.0.0.2
  

Temporary fix

Comments

APAR Information

• 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

• R701 PSN

     UP