IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    PI64788

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-23

  • Closed date

    2017-03-16

  • Last modified date

    2017-03-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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"801","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 June 2020