Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!UVVM!KLASSEN
From: KLASSEN@UVVM.BITNET (Melvin Klassen)
Newsgroups: bit.listserv.ibmtcp-l
Subject: Re: VM-to-VM FTP:  Corrupted module
Message-ID: <IBMTCP-L%90020516553967@CUNYVM>
Date: 5 Feb 90 17:52:13 GMT
Sender: IBM TCP/IP For VM List <IBMTCP-L@CUNYVM>
Reply-To: IBM TCP/IP For VM List <IBMTCP-L@CUNYVM>
Lines: 20
Approved: NETNEWS@PSUVM Gateway

>On Fri, 2 Feb 90 17:59:37 EST Doug Nelson said:
>>>In the midst of doing some FTP's between the production 4381 and
>>>the new machine, we discovered that MACLIBS were getting corrupted.
The directory for a MACLIB contains non-standard, non-displayable
characters.
>>>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, because the FTP spec says that ASCII is the default.
It's necessary, but not sufficient, to issue the BINARY command.
See Table 2-1 on page 2-2 of GC09-1204-02 'IBM TCP/IP for VM Command
Reference Manual, Release 1.2'.
Basically, it recommends to use 'TYPE EBCDIC' and 'MODE STREAM'
when transferring "text" between two VM systems.
(Experimentally, "text" can be any of the 256 hex. codes, except X'15';
although the manual states that "text" excludes X'1E'.  Hmmm.)
It recommends to use 'TYPE EBCDIC' and 'MODE BLOCK' when transmitting
"binary" files, e.g., MODULE, TXTLIB, and LOADLIB files.
In this case, I recommend to do what IBM says, and you'll be OK.