Re: FTP creates a flat file. Mr Rogers would slap me.

On 1/13/11 10:19 AM, Scott Klement wrote:

What does BINARY mode have to do with the errors you posted?

Here's what you posted:

<<SNIP FTP426 "Cannot write to member...">>

What on EARTH does that have to do with whether you do/don't use
BINARY mode? Binary mode enables/disables translation. It has
nothing to do with whether you can send data to a server.

On 1/13/2011 10:30 AM, Tom Deskevich wrote:

I did not have it set to BINARY!!!! It works now.

<<SNIP>>

The FTP426 was noted to be a side effect of an inability to "write" [some of] the data to the target file[.member]; possibly a data mapping or similar I\O error. Sending was allowed to start, just not complete with success. Review of the error logged in the FTP server job is required to see the origin of the 426 error that was issued in the client job.

Possibly some of the specialized homogeneous capability of the TCP/IP FTP feature for the IBM i [to provide some limited support of database row transfers beyond the scope of generic FTP of either text or binary] could be influenced by the "Type" choice, perhaps by an influence on the switches used on the C Open request of the target file.mbr by the FTP server, on the C Open request of the source file.mbr, or in conjunction for negotiating read\write of database versus just plain text or binary data.?

But... unless or until the OP posts details about the failure in the server job, why the TYPE IMAGE setting might have resolved the issue with the PUT, will remain a mystery.

Regards, Chuck