× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: FTP - To Transfer as EBCDIC
  • From: Tim McCarthy <TimM@xxxxxxxxxxxxxxxxxx>
  • Date: Thu, 25 Feb 1999 12:36:41 -0500


> As you're running the process in batch you will probably want to scan
> the
> log within your program. The "  226  Transfer complete " message is
> exactly
> what you're looking for. If you find that in the log you can assume
> that
> the PUT request was successful.
          
        [Tim McCarthy]  Actually you can't. The 226 message indicates
the transfer was complete (the text of the message can vary from server
to server) but it does not guarantee that the file was successfully
stored on the server. ABOR or other exception notifications can be
issued by the server either before or after a 226 message is issued.

        FTP file transfers take place over two separate connections -
one is a TELNET session for commands, the other is the data link.
Parsing text output from the command session can give you a good picture
of what happened in an FTP session but output varies from server to
server. Unless you know what happens in the "data" link you can't be
100%.

        As for file transfers in EBCDIC, this can only be done if the
remote server supports EBCDIC. You may perform a binary transfer which
will give you an exact image of the file on the remote system but this
is not the same as EBCDIC. Just like an ASCII transfer, an EBCDIC file
transfer will try to maintain record integrity by inserting record
separators so the transfer size will vary from the actual byte size of
the file depending on the number of records.    

> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.