PM89935: omake -L does not properly handle rebuilds of entire dependency tree

Rational ClearCase Fix Pack 8 (8.0.0.8) for 8.0
Rational ClearCase Fix Pack 1 (8.0.1.1) for 8.0.1
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 4 (8.0.1.4) for 8.0.1
Rational ClearCase Fix Pack 5 (8.0.1.5) for 8.0.1
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
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

APAR status

• Closed as program error.

Error description

• When using IBM Rational ClearCase omake to build applications,
  timestamp-only rebuild decisions are handled incorrectly.
  
  If a source file is changed, only the target that directly
  depends on the 'newer' file is rebuilt. Any targets that
  depended on the rebuilt target are not rebuilt.
  
  This behavior happens:
  - In a dynamic view when using the -L (Disable config
  management) option.
  - In a snapshot view or non-ClearCase location, since
  configuration lookup is not possible in those locations.
  
  Workaround:
  1) Do not use this option in a ClearCase Dynamic View.
  2) Use a non-ClearCase build tool when not in a Dynamic View.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using IBM Rational ClearCase omake to build
  applications, timestamp-only rebuild decisions are handled
  incorrectly.
  

Problem conclusion

• A fix is available in ClearCase versions 8.0.0.8 and 8.0.1.1
  

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

• R800 PSN

     UP