Laurence John McKown gave you a rather long explanation.
A shorter one - from which John's points can be derived - is that the TSO session supporting the 3270 data stream was *never* designed to support file transfer. It was designed to support conversational interaction with an end user keying into typically a small number of fields and then leisurely reading the resulting output. "File transfer" this ain't - if you'll excuse my appalling grammar! On the other hand, FTP is specifically designed to perform file transfer - I guess that had something to do with the problem of what name to give to the protocol which characterises FTP programs! In addition to which John appears to have made the understandable assumption that your TSO session over an SNA network will be concatenated to a TELNET TCP connection over the IP network. FTP simply uses the IP network. Referring to the recent half-marathon from Newcastle-upon-Tyne to South Shields, grandiloquently named "The Great North Run" - probably a reference to "The Great North Road" as the A1 used to be known, I would liken IND$FILE to the "fun-runner" who strapped a refrigerator to his back while FTP would correspond to the two East Africans who made a contest of the last few yards - meters in some geographies - of the course for the honour of being the winner. Chris Mason On Wed, 19 Sep 2012 19:34:40 +0800, Tsai Laurence <[email protected]> wrote: >Dear listers , >as the subject, test file transfer through TSO IND$FILE & TCP/IP FTP , and >found TSO IND$FILE is much slower than FTP. Any idea why ? > > >Regards, >Laurence ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
