Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!MSU!08071TCP From: 08071TCP@MSU.BITNET (Doug Nelson) Newsgroups: bit.listserv.ibmtcp-l Subject: Re: VM-to-VM FTP: Corrupted module Message-ID: Date: 2 Feb 90 22:59:37 GMT Sender: IBM TCP/IP For VM List Reply-To: IBM TCP/IP For VM List Lines: 18 Approved: NETNEWS@PSUVM Gateway X-To: "Edward J. Rovera" , IBM TCP/IP For VM List In-Reply-To: Message of Fri, 2 Feb 90 13:07:17 PST from > In the midst of doing some FTP's between the production 4381 and >the new machine we discovered that MACLIBS were getting corrupted. >The reported symtom was that X'FF' was being converted to X'07'. >Since we are running VANILLA FAL code right off the tape (and I have >not done any futzing with any translate tables) I strongly suspect >that what happened happened due to something that came with FTP and is >due to something we didn't do during the FTP process. Does one have >to issue a BINARY command before FTP'ing between VM systems? If so, >why? Yes, you have to issue a BINARY command if you're transferring binary data. Why? Because the FTP spec says that ASCII is the default, that's why, plain and simple. In general, binary files are going to be useless when sent from one OS to another, and there's no way to determine for sure that both systems are running the same OS. Doug Nelson Michigan State University