Handling of the send file
For the send file, the locking method differs depending on the value specified for Send File Mode in the Send Management Information.
(1) When Send File Mode is set to "Keep"
In HULFT for Mainframe
HULFT allocates the send file in shared mode.
If a HULFT or non-HULFT job has already operated the send file in exclusive mode, HULFT retries to access the file, based on the settings for Retry Count for Accessing Send Files and Retry Interval for Accessing Send Files. When the HULFT or non-HULFT job releases the control of the send file, the file allocation is carried out.
In HULFT for IBMi
HULFT opens the file without locking the send file.
The locking status of the opened file becomes *SHRRD for a physical data file and *SHRNUP for a save file, respectively.
In HULFT for UNIX/Linux or HULFT for NSK
HULFT opens the file without locking the send file.
At that time, checking whether the file is locked by a non-HULFT process is also omitted.
In HULFT for Windows
HULFT opens the file in shared-for-read mode without locking the send file with a mutex object.
If a non-HULFT process has opened the send file without sharing, HULFT retries the opening based on the setting for Retry Count on Locked Send File and Retry Interval on Locked Send File.
(2) When Send File Mode is set to "Clear" or "Lock"
In HULFT for Mainframe
HULFT allocates the send file in exclusive mode.
When another HULFT or non-HULFT job has already operated the send file in exclusive mode, HULFT retries to access the file based on the settings for Retry Count for Accessing Send Files and Retry Interval for Accessing Send Files. When the HULFT or non-HULFT job releases the control of the file, the file allocation is carried out.
In HULFT for IBMi
For a physical data file
HULFT locks the send file with lock status as *EXCL before it opens the file.
If another HULFT or a non-HULFT job has already locked the send file, the file is locked based on the setting of Wait Time on Locked Send File.
For a save file
HULFT opens the file without locking the send file. In such cases, the locking status of the opened file becomes *SHRNUP.
In HULFT for UNIX/Linux or HULFT for NSK
For a local file
HULFT locks the send file after the file is opened.
If another HULFT or a non-HULFT process has already locked the send file, the process stops until the file is unlocked.
For a network file
HULFT applies HULFT networked file locking. In addition, HULFT locks the send file after the file is opened. If another HULFT or a non-HULFT process has already locked the send file, the process stops until the file is unlocked.
You can use the networked file if HULFT8 Enterprise grade is installed. You cannot use it with HULFT for NSK.
In HULFT for Windows
For a local file
HULFT opens the send file not in sharing state, without locking it with a mutex object.
If a non-HULFT process has already opened the send file without sharing, HULFT retries for opening the file based on the setting of Retry Count on Locked Send File and Retry Interval on Locked Send File.
For a network file
HULFT applies HULFT networked file locking, and then opens the file without sharing.
If a non-HULFT process has already opened the send file without sharing, HULFT retries for opening the file based on the setting of the Retry Count on Locked Send File and the Retry Interval on Locked Send File.
You can use the networked file if HULFT8 Server grade is installed.
(3) When the Send File Mode is set to 'Delete'
In HULFT for Mainframe
Same as in (2) When Send File Mode is set to "Clear" or "Lock" in Handling of the send file.
In HULFT for IBMi
Same as in (2) When Send File Mode is set to "Clear" or "Lock" in Handling of the send file.
In HULFT for UNIX/Linux or HULFT for NSK
Same as in (2) When Send File Mode is set to "Clear" or "Lock" in Handling of the send file.
In HULFT for Windows
For a local file
After locking the send file with a mutex object, HULFT opens the file without sharing.
If another HULFT or a non-HULFT process has already locked the send file with a mutex object or they have opened the file without sharing, HULFT retries to open the file based on the setting for Retry Count on Locked Send File and Retry Interval on Locked Send File.
For a network file
After the send file is locked with the mutex object, HULFT applies HULFT's networked file locking to the file. Then, the file is opened without sharing.
In either of the following conditions is met, HULFT retries to open the file based on the setting for Retry Count on Locked Send File and Retry Interval on Locked Send File.
-
If another HULFT or a non-HULFT process has already applied the lock with the mutex object or HULFT's networked file locking to the send file
-
If the file is opened without sharing
You can use networked files if HULFT8 Server grade is installed.