Chapter 1. File Transfer Protocol 19
Figure 1-17 Change Authority to use initiate FTP session
c. Click OK.
4. Click OK again on the Capabilities window. At this point the user glakner will not be able to
initiate an FTP session from this iSeries. If he tries to start a session the message
TCP3C8A stating,
Operation not authorized, will be found in his interactive joblog.
This ends the procedure.
1.5 TCPL0300 format for FTP server logon exit point
In V5R1, a new format for the FTP server logon exit point was added. The new format -
TCPL0300 - extends the TCPL0200 format to support the new enhanced password. Also,
provides new parameters to allow CCSID processing for password and directory fields.In
addition, when the user for the session has been authenticated with a client certificate, the
client certificate is provided to the exit program.
For more information about the new exit point format, refer to iSeries Information Center at::
Select the appropriate geography -> Language and version -> Networking -> TCP/IP
-> FTP reference information -> FTP exit programs -> Server logon exit point ->
TCPL0300 exit point format
1.5.1 FTP problem determination
The left column of Table 1-2 shows symptoms of typical FTP problems. The column on the left
give the possible cause of the problem, corrective action you can take, and/or documentation
that will need to be collected to analyze the problem.
20 V5 TCP/IP Applications on the IBM Eserver iSeries Server
Table 1-2 Problem determination for FTP
Problem Symptom Possible causes, corrective action, documentation collection
FTP Connects but cannot
transfer data,
PUTs or GETs
will not work
Is there a firewall between the FTP client and the server?
By default, iSeries/400 FTP Client uses passive ("firewall friendly")
connections, which allows the client to initiate the FTP data
connection using high-numbered ports. Some servers and network
configurations do not allow this and require that the traditional FTP
data port 20 be used. To turn off passive mode use the FTP
subcommand SENDPASV. This command toggles from ON to OFF or
visa versa.
A second option would be to open the firewall ports above 1024.
FTP from an iSeries client to a
remote FTP server failed with
message TCP10B0
This typically means that the FTP server or some intermediary
network component has rejected the connection request.
򐂰 A communication trace would show the failure very quickly and
easily. Trace could be filtered down to just FTP port 21 and
further by the IP address of the target server.
򐂰 If client send SYN (start of session 3-way handshake and an
ACK RST is returned, request was rejected. Possible causes:
There could be a Firewall or Proxy server rejecting the
Verify that the required ports for FTP are available and
allowed through the firewalls
Verify that no filter rules are configured on the iSeries that
prohibit this FTP connection or that the SOCKS client on
the iSeries is not redirecting this traffic.
Sending a SAVF file from one
iSeries to another. Savf file is
unusable on the target system
The default for FTP file creation in the QSYS.LIB file system on the
iSeries, is a PF (physical file). A savf is a file format that is unique to
the iSeries. There are several methods to ensure SAVF format is
򐂰 First, the file transfer must always be in binary (also known as
򐂰 Option 1, create the SAVF on the target system before starting
the transfer. You could telnet and create it or within the FTP
session issue the subcommand:
quote rcmd crtsavf mylib/mysavfile
issue the put with a target name of mylib/mysavf
򐂰 Option 2, set the name format to 1
issue the command NAMEFMT 1
issue the PUT command using NAMEFMT 1 as: PUT
/qsys.lib/mylib/mysavf.file /qsys.lib/tolib.lib/mysavf.savf
(Note the target file extension is savf) instead of file
Attempt to FTP a file on the
iSeries results in FTP reply
code 426
CPF5035 RC19 - An unexpected null field will be logged in the
joblog. By default FTP will attempt to compress nulls fields.
In the FTP session, do the following command to allow the FTP of
Null Fields:
Chapter 1. File Transfer Protocol 21
FTP - Message TCP106E
when doing a GET
The file naming convention in iSeries is different than some
platforms (for example, Windows® NT).
When issuing the GET, specify the name of the file as it is on the
other platform, then provide a space and enter a target file name
that is supported by iSeries.
For example:
GET #myfile.prz myfile.prz
Problem Symptom Possible causes, corrective action, documentation collection
22 V5 TCP/IP Applications on the IBM Eserver iSeries Server

Get V5 TCP/IP Applications on the IBM eServer iSeries Server now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.