Re: FTP Fails with "426 Transfer cancelled"

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Sam

There are actually 2 timeouts, CHGFTPA handles only one. The other is a 
transfer timeout, and that is often the culprit.

I found a link to something - it seems it has my name on it - heh - I 
forget - but give it a look -

http://search400.techtarget.com/tip/Setting-FTP-time-outs

HTH
Vern

On 1/16/2012 7:41 PM, Sam_L wrote:
> We FTP a small file (<  5,000 bytes) from the iSeries to a remote box.
> Occasionally, after connecting successfully and doing a PUT, the
> transmission fails with "426 Transfer cancelled".
>
> The remote session records 10054, if I read correctly what the remote
> support guys sent me. (There is a slight language barrier.)  I think
> 10054 means "connection reset by peer".  So tt looks like the transfer
> is being ended from our end.
>
> Our network guy suggests that we are timing out somewhere in the
> transfer because the remote system isn't getting back to us quickly
> enough.  Where would I configure how long we wait before cancelling the
> transmission?
>
> Is CHGFTPA the right place to look?  If so, all I see there related to
> time is INACTTIMO, which is set to 300.
>
>
>
> Sam
>
> This is what our log looks like when it fails:
>
> 331 Enter password
> 230 User logged in
> UNIX
> Enter an FTP subcommand.
>   >  cd xxxxx
> 250 Command CWD succeed
> Enter an FTP subcommand.
>   >  SENDEPSV 0
> SENDEPSV is off.
> Enter an FTP subcommand.
>   >  put xxxxlib/excordhd.ORH16046 ORH16046.txt
> 227 Entering Passive Mode (nnn,nnn,57,233,246,122).
> 426 Transfer cancelled
> Enter an FTP subcommand.
>   >  quit
> 221 bye