Path: utzoo!mnetor!uunet!husc6!necntc!ames!ucbcad!ucbvax!BNR.BITNET!BMURPHY
From: BMURPHY@BNR.BITNET ("B.J. Bernie  Murphy")
Newsgroups: comp.protocols.ibm
Subject: re:ftp problems
Message-ID: <8712221541.AA03727@jade.berkeley.edu>
Date: 22 Dec 87 15:15:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "B.J. Bernie  Murphy" <BMURPHY%BNR.bitnet@jade.berkeley.edu>
Organization: The ARPA Internet
Lines: 25

Regarding file transfer between Macs, PCs and VM mainframes using FTP:

When using FTP between a PC and VM you should use the Binary option
to move executable files.  You have to be careful with the LRECL and
RECFM options on the mainframe.  I find that RECFM V works best as
RECFM F will get you in all sorts of trouble.

Moving files created on the Mac to anywhere else is a real pain!  The
reason is that a Mac file  has 'Resource Fork' and a 'Data Fork'.
One way that works quite well is to use the Mac BINHEX utility to
convert the file to ASCII prior to file transfer. This utility combines
the resource and data forks as well. Having converted the file, use the
FTP ASCII option.  The resulting uploaded BINHEX file (ASCII text)
on the VM machine can be archived or sent via RSCS to another machine
as a text file.  I find that storing the file with RECFM F and LRECL 80
attributes works well on VM/CMS.  Getting the files back to the Mac is
the reverse process.  Make sure to use the same version of BINHEX.
There are several versions of BINHEX floating around.

I hope the above information  helps...

Regards,
Bernie Murphy,
Distributed Systems Services Group
Bell-Northern Research