Why are directory files not moved when I use Digital's Movefile file movement method with Diskeeper?

Users of OpenVMS VAX Version 5.5 and above, and OpenVMS Alpha V6.1, have the choice of using Digital's MOVEFILE primitive for file relocation, or the Diskeeper proprietary file movement method.

As of OpenVMS V6.0, the MOVEFILE primitive allows movement of directory files, as long as no node in the cluster has data from these files cached. Unfortunately, Digital has discovered a problem within the mechanism that performs the cluster-wide check for this condition. The problem could potentially result in cache incoherency and consequent directory file corruption.

Digital has released an operating system patch (patch #1096) to correct this problem on OpenVMS VAX V6.0, but had not completed the patches for OpenVMS VAX and Alpha V6.1 prior to the release of Diskeeper V7.0.

For this reason, when the MOVEFILE primitive is enabled as described in Section 2.9.2.15 of the Diskeeper Manual, Diskeeper does not attempt to move directory files. This may affect the ability of Diskeeper to consolidate free space.

When the Diskeeper proprietary file movement method is used, Diskeeper will move directory files. This may result in improved consolidation of free space.

If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail

Executive Software Europe