Re: FTP from IFS to Windows

Thanks for the clarification. I thought about binary mode, but was just not
positive. The destination is the corporate office where I work. They aren't
happy when things don't work "just right". But, that only applies to everybody
else.......

John McKee

Quoting Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>:

hi John,

When you do your FTP transfer in "binary" mode, FTP will do absolutely
no translation. It will simply copy the data byte-by-byte to the remote
system.

When you use "ascii" mode, then the system will translate from the CCSID
of the file to the remote CCSID (which is configured via the CCSID
parameter of the FTP or STRTCPFTP commands, and defaults to 819).

ASCII mode may also cause FTP to translate the end-of-line delimiter...
when FTPing a PF, for example, it will add CRLF to the end of each
record. When FTPing a stream file, the CRLF that's already in the file
may be translated to LF-only if sending to a Unix machine (but, of
course, you're sending to Windows so that wouldn't be an issue.)

If you already have the file in 1252, then it's probably intended to
already be in Windows format, so I'd recommend using binary mode. No
point in having FTP translate it from 1252 to 819!


John McKee wrote:

This will sound naive. I have a file in the IFS. CCSID is 1252.

If I FTP that file to a Windows server, will the file be readable on the other
end? Or, perhaps a better question: What determines when FTP translates the
characters in a file?

The reason I ask is the only access I have to the Windows server is via FTP. I
could retrieve the file and look at it, but how would I know if FTP did not do
a second character conversion, to "help" me?

John McKee

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.