Confusing FTP client behaviour

[r***@t-systems.com]

Dear newsgroup,

we recently observed a confusing client behaviour. We are fetching
files from a remote site using a take file ( $ FTP host /USER=... /
PASSWORD=... /TAKE=... ), where the take file essentially contains a
"cd", "get", and "delete" command. We now observed, that the "get"
command results in MULTINET-F-ETIMEOUT message, but the following
"delete" command was executed.

So my questions are:
- why does the fatal error not result in a immediate client
termination,
- is there any logical which might force the client to abort in the
case of a fatal error?

The system environment is: Alpha GS1280 , VM 7.3-2 , Multinet 4.4

Any other ideas, beside avoiding the usage of a take file, to delete
the remote file after a successful transfer?

Thanks

Ralf

[d***@unn.ac.uk]

FTP can be made to exit on an error by including the line

exit-on-error on

before the point at which an error might occur (such as at the beginning
of the TAKE file). If an error does occur, FTP will exit with $STATUS
containing the error code.

David

Post by r***@t-systems.com
Dear newsgroup,
we recently observed a confusing client behaviour. We are fetching
files from a remote site using a take file ( $ FTP host /USER=... /
PASSWORD=... /TAKE=... ), where the take file essentially contains a
"cd", "get", and "delete" command. We now observed, that the "get"
command results in MULTINET-F-ETIMEOUT message, but the following
"delete" command was executed.
- why does the fatal error not result in a immediate client
termination,
- is there any logical which might force the client to abort in the
case of a fatal error?
The system environment is: Alpha GS1280 , VM 7.3-2 , Multinet 4.4
Any other ideas, beside avoiding the usage of a take file, to delete
the remote file after a successful transfer?
Thanks
Ralf

[Christoph Gartmann]

Post by r***@t-systems.com
we recently observed a confusing client behaviour. We are fetching
files from a remote site using a take file ( $ FTP host /USER=... /
PASSWORD=... /TAKE=... ), where the take file essentially contains a
"cd", "get", and "delete" command. We now observed, that the "get"
command results in MULTINET-F-ETIMEOUT message, but the following
"delete" command was executed.

It looks like some firewall "feature".

Post by r***@t-systems.com
- why does the fatal error not result in a immediate client
termination,
- is there any logical which might force the client to abort in the
case of a fatal error?
The system environment is: Alpha GS1280 , VM 7.3-2 , Multinet 4.4
Any other ideas, beside avoiding the usage of a take file, to delete
the remote file after a successful transfer?

You could implement the functionality with Kermit. There you have a status
after each command and a lot more programming logic to achieve what you want.

Regards,
Christoph Gartmann