No "Initialization Complete" message

If the EZY2702I Server-FTP Initialization completed at … message does not appear on the system console within a few minutes after starting the FTP daemon, verify that the daemon background job is still running. For example, if you started FTP with a procedure called FTPD, you can use the D A,L command to see whether the job FTPD1 is active.

If the background daemon job is running (for example, FTPD1), verify that TCP/IP is running. If it is not, start TCP/IP. The FTP initialization completes when TCP/IP starts.

If the background daemon job is not running, check the system console for nonzero exit codes from the background job. Look for messages in message or trace output from syslogd for an EZY error message from FTP. The following are possible exit codes and the appropriate responses:

0012
FTP is unable to use the port specified for the control connection. Look in the syslogd messages for the specific reason. Possible errors include the following:
- EZYFT13E bind error…Operation not permitted
  Ensure that FTP has BPX.DAEMON authority.
- EZYFT13E bind error…Address already in use
  Ensure that FTP is trying to use the correct port. The FTP server trace with the INT option indicates the port the daemon expects to use. If this is the correct port, you can use the TSO NETSTAT CONN command to determine the job that is currently using that port.
- EZYFT13E bind error…Permission denied
  Ensure that the port you want FTP to use has been reserved for the FTP background job name. For example, if your start procedure is called FTPD and you want FTP to use port 21, the PORT statement in your hlq.PROFILE.TCPIP data set must specify 21 TCP FTPD1.
0028
This FTP daemon is not available because the IBM® TCP/IP is not enabled.