IBM Support

PI44916: MVFS "USECACHEMANAGER" SETTING MAY CORRUPT BUILD OUTPUT IN DYNAMIC VIEWS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When building using IBM Rational ClearCase dynamic views, build
    output may be corrupted if the MVFS is configured to use the
    Windows cache manager by setting:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Mvfs\Parame
    ters\UseCacheManager to 1
    
    This appears to be most common if the new build output files are
    smaller than the previous build output files. instead of
    truncated files, the "extra" space in the file will either
    contain null characters or efffecctively random binary data.
    
    Removing this entry and rebooting the workstation resolves the
    issue, but will also result in degraded build performance.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Software built in a ClearCase dynamic view on Microsoft      *
    * Windows, on a system on which the value of the registry key  *
    * UseCacheManager has been modified from its default of 0, to  *
    * 1.                                                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When building using IBM Rational ClearCase dynamic views,    *
    * build                                                        *
    * output may be corrupted if the MVFS is configured to use the *
    * Windows cache manager by setting:                            *
    * HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Mvfs\Pa *
    * rame                                                         *
    * ters\UseCacheManager to 1                                    *
    *                                                              *
    * Files which are written and then truncated during a build    *
    * may not be truncated correctly.  File size and also contents *
    * beyond what had been expected to be the correctly truncated  *
    * size may be incorrect.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This problem is fixed in ClearCase 8.0.0.16 and 8.0.1.9.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI44916

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-14

  • Closed date

    2015-09-17

  • Last modified date

    2015-09-17

  • 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 PSY

       UP

  • R801 PSY

       UP

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

Document Information

Modified date:
17 September 2015