On Fri, 8 Jun 2007 09:08:43 -0500, Paul Gilmartin wrote: >On Fri, 8 Jun 2007 07:59:40 -0500, McKown, John wrote: >> >>The method is documented and is simple. The downloaded file is >>especially encoded as it is downloaded. With a very simple encoding >>method. Each data byte in the range 0x00-0xFE comes down unchanged. A >>0xFF data byte is encoded as two bytes: 0xFFFF. A logical end of record >>is encoded as 0xFF01. End of file is encoded as 0xFF02. 0xFF03 is >>end-of-record combined with end-of-file. That's it. It works regardless >>of anybody else's opinion. It is not often implemented in ASCII based >>systems such as Windows or Linux or UNIX because they don't have RECORD >>oriented architectures. But it does work for the z/OS ftp server. I >>never said anywhere that it worked for any other server. >>
>This doesn't seem to come from RFC 959. I'll look in IBM It is in RFC 959. See 3.4.1 STREAM MODE. "In a record structured file EOR and EOF will each be indicated by a two-byte control code. The first byte of the control code will be all ones, the escape character. The second byte ..." Bill ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
