| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Is it possible to use ftp reply codes to tell if a file transfer was completed successfully? example: Doing a get of a file from a remote system gives me a: '226 Transfer completed. 3032 (8) bytes transferred.' Is it reaonable that looking at just the 226 we say that the transfer is correct or do i need to count bytes on each side? Counting bytes on each side is easy for vms and unix its difficult for mnw and mvs. This particular transfer was from vms to digital unix the file has 2933 bytes on unix so just parsing the output doesnt work. BTW: what does the (8) signify ? thanks tom
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9042.1 | See rfc 959 | NETRIX::"[email protected]" | Brian Haley | Wed Mar 05 1997 14:18 | 29 |
Hi,
According to RFC 959 (and our code), 226 will be sent on success.
Be warned that a successful abort (^c during transfer) is also a
226 code:
ftp> get vmunix
200 PORT command successful.
150 Opening BINARY mode data connection for vmunix (16.140.64.151,1050)
(9026320 bytes).
^c
receive aborted
waiting for remote to finish abort
426 Transfer aborted. Data connection closed.
226 Abort successful
488844 bytes received in 1 seconds (4.8e+02 Kbytes/s)
Anyhow, according to RFC 959 (http://ds.internic.net/rfc/rfc959.txt):
226 Closing data connection.
Requested file action successful (for example, file
transfer or file abort).
> BTW: what does the (8) signify ?
You'll have to ask someone in VMS - it's printed by the client.
-Brian
[Posted by WWW Notes gateway]
| |||||
| 9042.2 | thanks | MAIL2::YATES | Wed Mar 05 1997 14:29 | 6 | |
Thank you very much for the quick reply.
tom
| |||||