Points to be noted

(1) Unsupported Operations

For some environments, depending on the file server, exclusive control cannot be applied when the shared mode for files that are opened by the CreateFile() function from a Windows environment via a network is used at the same time as the lock on a byte range set by the lockf() function from a UNIX/Linux environment.

In such an environment, if files are operated from HULFT and another application at the same time, exclusive status will not be recognized correctly on either side even if the conditions explained in Prerequisites are met. Therefore, it is possible that the target file might become corrupted. HULFT does not support the simultaneous operation of the same file in both HULFT and another application, in the operation environment described above.

(2) Cautions concerning exclusive control files

When HULFT networked file locking is applied, an Exclusive Control file (.#HULLOCK.target file name) is automatically created in the directory that is at the same level as the target file. Exclusive control is applied according to the Exclusive Control file. Therefore, caution is required, because HULFT does not apply exclusive control correctly if the Exclusive Control file is deleted while networked file locking is applied.

(3) When networked files cannot be shared

When receiving multiple files, or when managing Receive files in generations, you cannot share networked files in multiple HULFT systems.