RE: FTP PUT creates a FLAT file

Also be careful about trimming trailing blanks on the records. Look at LOCSITE TRIM 0 for the PUT and QUOTE SITE TRIM 0 for GET if you're not doing a Binary transfer.

Paul Morgan

Principal Programmer Analyst
IT Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, January 12, 2011 4:46 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: FTP PUT creates a FLAT file

On 1/12/11 1:19 PM, Tom Deskevich wrote:

I am trying to FTP to a remote system and put a file there. The put
works, but the file comes in as a flat file, a DSPFFD shows 1 field.
I try to do a CPYF to an empty file with DDS, but the to file is
garbage. I tried to create the files first, but I guess you cannot
do a PUT with a replace, at least with the research I saw. I tried to
sign on to the remote system to try a GET, but for some reason I
cannot FTP back to our system. I cannot create a save file, because
they are on 5.2 and we are on 7.1.

FTP transfers data, not files. Pre-create any file into which data
should be placed, to ensure the attributes of the file are established
as desired, before issuing the PUT of the data.

The FTP PUT subcommand effects an implicit "replace" of the data in
the target file [the target database file member, for /QSYS.LIB file
system] whereas the FTP APPEND subcommand adds data to the file.

What happens when using PUT to the file created "with DDS"? Possibly
there are data types other than character, so even a homogeneous
transport [from IBM i 7.1 to i5/OS v5r2] is likely to require minimally
setting both of Type EBCDIC and Mode Blocked to enable the FTP client
and server to effect a desirable outcome; caveat emptor:
http://archive.midrange.com/midrange-l/200803/msg00295.html

Regards, Chuck