Determine problems with File Transfer Protocol

You can view a list of steps to determine whether your Simple Mail Transfer Protocol (SMTP) is working correctly.

If you detect a problem when using File Transfer Protocol (FTP), use the following flow chart to identify the cause after using the flow chart for general TCP/IP problems. The cause lists that follow list steps to help you identify the cause of the problem.

Figure 1. FTP problem analysis
FTP problem analysis flow chart

Cause list A

Is there is a long delay between connecting to the iSeries™ FTP server and receiving a prompt for a user id? If so, check the configuration of the domain name server on your iSeries. The FTP server performs a DNS query as soon as a new connection is received. DNS problems can cause the server to hang for several minutes before a response is received.
Check to see if an exit program has been added to the FTP Server Logon Exit Point. If yes, then check if the logon that is unsuccessful is allowed by the exit program.
Check to see if the remote logon requires a password if a password was requested. Some systems request a password, but the connection can fail because it is not required.
Set up a password on the remote system if required. You might need to restart if you change the security information about the system.
Check your user ID and password by attempting to sign on to your remote system. If you are unable to do so, contact the system owner to verify that your user ID and password are correct.

Cause list B

Make sure binary mode is in effect if you are transferring binary files.
Check to be sure the mapping tables on both the client and server systems are compatible. You need only do this if you are using your own mapping tables.
Check to see that the correct CCSID has been specified for the transfer. If not, use the TYPE or LTYPE subcommand to set the correct CCSID value before the transfer is performed.
Create a file on the system that you are planning to store data into. Set the proper record length, number of members, and number of increments. Try the data transfer again and verify that it was successful.
Make sure that you are authorized to use the file and the file members.
Check to see if the transfer file contains packed decimal or zoned decimal data.
If you are transferring a Save file, verify that the appropriate method was used.

Cause list C

Check file size limits on the remote system.
Check to see if the FTP server timer ended. The iSeries server time-out value can be set using the QUOTE TIME command.
Use the NETSTAT command to verify that the *LOOPBACK interface is active. Then re-create the problem doing FTP LOOPBACK (iSeries-to-iSeries internally).
- If the problem cannot be recreated, it is probably a remote system problem.
- If you can re-create the problem, complete the following steps:
  1. If the problem is an FTP server problem, then start the FTP server trace using the TRCTCPAPP command.
  2. Create the problem again.
  3. End the FTP connection. Refer to the Starting and stopping the FTP server.
  4. End the FTP server trace using the TRCTCPAPP command.
  5. Find a spooled file with the following characteristics:
    - The file name is QTMFFTRC
    - The username associated with the file is the name of the user who issued the TRCTCPAPP command.
    The trace is a spooled file in the default output queue of the system associated with the FTP server job.
  6. Send in that spooled file.
  7. If the problem was on the iSeries FTP client, a trace can be obtained using the DEBUG 100 client subcommand.
  8. When running the FTP client interactively, use the F6 (Print) key to create a spool file that contains a history of the FTP client subcommands entered, and the associated FTP server replies. When the FTP client is run in batch unattended mode, then this history of subcommands and server replies is written to the specified OUTPUT file.