PM50735: stat() system call fails with EOVERFLOW when CD'd into a view-extended path. Works while set into view.

Rational ClearCase Fix Pack 03 (8.0.0.3) for 8.0
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 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
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 Permanent restriction.

Error description

• When using an IBM Rational Clearcase dynamic view and a 'view
  extended' (e.g., '/view/myview/vobs/vob1/mydirectory') path as
  the current directory, older compilers that use the 'stat'
  system call to get file information may fail to compile source
  code.
  
  If a given compile is impacted by this issue, an strace of the
  compile will show that a stat() system call failed with
  EOVERFLOW (Value too large for defined data type). Immediately
  after this failure, the compile aborts.
  
  Workaround:
  1) Use 'cleartool setview' to enter the view containing the
  source files.
  2) Contact the compiler vendor for an update to the compiler in
  question. This problem has only been observed when using a
  third-party compiler that was last updated in 2002.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The underlying problem was that the compiler was making an
  obsolete stat call that did not provide enough bits for the
  expanded device codes available in the 2.6 kernel series.
  

Problem conclusion

• The problem was the use of an obsolete compiler.  The
  customer has agreed to upgrade their compiler.
  Consequently, we are not making any changes to ClearCase.
  

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

Applicable component levels