If the FTP process has failed you will find the following:

•A message in the joblog “Error sending files via FTP”. If you press F1 on the message you will see the reason for the failure

•A print of the FTP log for each document that failed. This is written to File Name QSYSPRT with User Data FTPLOGPRT and will be sent to the output queue defined in the FTPLOGOUTQ data area. Also in library QTEMP, for the job running the FTP commands, there will be a file called APPDFTP. This will have two members:

FTPCMDS – containing the last FTP instructions

FTPLOG – FTP conversation

FTPLOGOUTQ Data Area Definition

This data area holds the library name and output queue name for the error log produced by the FTP function e.g.

You may change the data area to hold a different Output Queue and Library Name but they must be valid.

Resolving Errors

229 Entering Extended Passive Mode. No response from remote host; all connections closed.

This error usually happens if you have not configured your Firewall to allow FTP Passive mode. Please see the following extract from the IBM Manual.

FTP on IBM i is a Passive mode FTP Client when transferring something directly to/from the IBM i Platform. By FTP Specification, sessions only occurs over TCP not UDP communications.

As in all FTP protocol there is a Command Channel and a Data Channel involved to provide the file transfer process. Port 21 is the command port by Architectural definition. To start the connection to setup the characteristics of the FTP session, ie the source IP Address requests the destination IP Address to connect on its port 21. The Firewall must be configured to allow this source IP/local arbitrary port number to connect to destination IP Address/port 21. As this is passive FTP, the port for data is not port 20 (as it is in Active FTP) but an arbitrary high number port that the server returns back to the FTP Client (in response to the PASV command the client sends to the server) for the FTP Client to use in connecting and sending data over. You have to ensure the firewall is not filtering/blocking either flow.