PI64788: TIMING CHANGES IN THE MVFS MAY CAUSE AN ISSUE WITH A TRIGGER

Rational ClearCase Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearCase Fix Pack 4 (9.0.0.4) for 9.0
Rational ClearCase Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearCase Fix Pack 5 (9.0.0.5) for 9.0
Rational ClearCase Fix Pack 6 (9.0.0.6) for 9.0
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

• If you have a trigger script that sets the access and modify
  time of a file in an IBM Rational ClearCase dynamic view, you
  may see a difference in behavior between ClearCase versions
  8.0.1.8 and earlier and 8.0.1.9 and later.
  
  In version 8.0.1.8 and earlier, you would see the following:
  
                                                             file,
  access,       modify
  orig time:                                        test.txt
  , 1466609881, 1466633281
  time changed file/before uname:   test.txt       , 1466702614,
  1466702614
  after uname 0sec wait                   test.txt       ,
  1466609881, 1466633281
  after uname 10sec wait                 test.txt       ,
  1466609881, 1466633281
  
  In version 8.0.1.9 and later, you will see:
  
  
  file,         access,       modify
  orig time:                                         test.txt
  , 1466609881, 1466633281
  time changed file/before uname:   test.txt      , 1466704430,
  1466704430
  after uname 0sec wait                    test.txt     ,
  1466609881, 1466633281
  after uname 10sec wait                 test.txt      ,
  1466609881, 1466704430
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of ClearCase on Microsoft Windows.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The use case described in detail is a ClearCase trigger      *
  * script which is being used to set the access and modify      *
  * times on a file.  The trigger script is not successful in    *
  * setting these times on ClearCase versions after 8.0.1.9.     *
  * The underlying cause of the problem is that any application  *
  * which sets file attributes after writing to a file and       *
  * closing it, will see attributes revert to the values in      *
  * place at the time the file was closed.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This problem is fixed in ClearCase 8.0.1.14 and 9.0.0.4.
  The MVFS logic has been corrected to allow attribute changes
  made by the application to persist.
  

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

• R801 PSY

     UP

• R900 PSY

     UP