Path: utzoo!utgpu!ugw.utcs.utoronto.ca!CUNYVM!IBMTCP-L Date: Fri, 2 Feb 90 16:07:17 EST Reply-To: IBM TCP/IP For VM List Sender: IBM TCP/IP For VM List From: "Edward J. Rovera" Subject: VM-to-VM FTP: Corrupted module To: UofToronto LAN redistribution Message-ID: <90Feb2.171155est.58665@ugw.utcs.utoronto.ca> Newsgroups: list.ibmtcp-l Distribution: ut Approved: devnull@gpu.utcs.toronto.edu We are running FAL 1.2.1 on our production 4381-92E and have just connected up our new 3090-200S to the ethernet. Both machines are running VM/XA 2.0 with VM/HPO 5 running underneath. The FAL code is running on the HPO systems, not in XA. 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? I also encountered a specification exception running a module that I had FTP'ed to the 3090 that disappears when I used the sneakernet (i.e, VMFPLC2 DUMP to tape and sneaker it down to the new machine room) to move the module. I don't know if this was a random glitch or related to the MACLIB translation problem. Had I had more time, I would have done more detectiving but I was in a hurry and just got what I needed done. Thanks.