A file change of status along the transfer according to the receiver or sender of the file itself. Note that the requester host can be either the receiver or sender, according to the used rule.
If the Host is the sender:
At startup, before any pre actions is taken, the file is logically instantiated:
If the transfer is in SendThrough mode, no test is done. The file is logically instantiate as is.
If not, in first try, the file is searched under the default send directory (OUT) in case of relative path.
If the file is an absolute path, it is searched according to this path.
If the file cannot be found or is not readable (except in SendThrough mode), the transfer stops in error for no file found.
After the pre actions, the file is tested again on its existence and access before the real send:
If the transfer is in SendThrough mode, no test is done. The file is logically instantiate as is.
If not, in first try, the file is searched under the default send directory (OUT) in case of relative path.
If the file is an absolute path, it is searched according to this path.
Once the transfer is over, no action is taken on the file except those implied by any post actions.
In case of error before pre actions, the restart will take the first step of checking before pre actions.
In case of error after or while the pre actions, the restart will take into account the name as stored (eventually modified by previously succesfully executed pre-actions, which will not be re-executed).
If the Host is the receiver:
At startup, before any pre actions is taken, the file is logically instantiated:
The file is logically instantiate as is.
After the pre actions, the file is modified:
If the transfer starts from zero (usual situation), a temporary unique file is created in the working directory (using the transfer id, a unique number and the extension ".r66"). The file is tested in write. The logical file points to this physical temporary file.
If the transfer does not start from zero (a restart occurs), the previous file name is reused. The file is again tested in write. The logical file points to this physical temporary file.
If the transfer is in RecvThrough mode, no test is done on the file. It is just instanciated logically on the basis of a temporary unique file virtually created in the working directory.
If the file is not writable (except for RecvThrough mode), the transfer stops in error.
It is not a good idea to change the name of the file during the Pre actions for the receiver. However, it is possible to do so, for instance in order to move this working file into a different directory than the working directory specified in the rule.
Once the transfer is over, the file is renamed without its temporary extension ".r66" and is moved into the receive directory (IN). The Post actions can change the name of the file (MOVE, MOVERENAME, ...). No test is done once the file transfer is over, even after a move.
In case of error before pre actions, the restart will take the first step of checking before pre actions.
In case of error after or while the pre actions, the restart will take into account the name as stored (eventually modified by previously succesfully executed pre-actions, which will not be re-executed).
A transfer can stop for several reasons:
It is possible to restart a transfer once interrupted.
It is generally recommanded that the requester host takes the decision of restarting the transfer. However, both hosts can try to restart the transfer.
There is several ways to do so: