× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.