X-no-Archive:yes
Reflection can correctly translates MPE record separators to CR/LF. If you
look at File Transfer setup, on the Translation tab / page, the Translation
from Host group box has a check box, Record Separator = CR/LF (or something
like this, depending on the version of Reflection). I don't know if WRQ's
ftp server software will do this for you or not when sending from the ftp
client on the 3000.

Is there a compelling reason to want to use some other transfer method, such
as needing to automate this with a job stream on the 3000?

When I perform an ASCII send of a file whose FOPTIONS are
ASCII,FIXED,NOCCTL,STD, I can read it successfully on my workstation. Does
your file by any chance have CCTL? If not, can you provide more detail about
the file and about the nature of the corruption, and what you mean by the
file growing? For instance, can you look at the file from a successful
Reflection transfer and a failed ftp in a hex editor, and find the
differences?

Greg Stigers
http://www.cgiusa.com

-----Original Message-----
From: Bob Bender [mailto:[log in to unmask]]
Sent: Wednesday, September 15, 1999 5:08 PM
To: [log in to unmask]
Subject: HP3000 FTP Process


Hello Everyone,

I am trying to ftp a file to a Windows 95 PC from the HP3000.  The record
size is   -300,1,f,ascii and when using Reflection transfer method it works
correctly.  If I ftp the file in ascii or binary it is not correct and will
grow in size.  Is there setting I need to use to make sure the file is not
corrupted moving to the PC?  The problem occurs with several different FTP
server software applications.


Bob Bender     [log in to unmask]
Vice President - Management Information Services
Founders Federal Credit Union   www.foundersfcu.com
92,000 members, 13 branches, Conv. 1989
Rel 28.13 & MPE 5.5 PP7
Windows 95, 98 , NT Server 4.0, OS2
Lefebure Cash Machines(14), FDR,Maestro Suite