ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaiq_5.4.0.1/rzaiqtroubledetermine.htm

125 lines
7.9 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Determine problems with File Transfer Protocol" />
<meta name="abstract" content="You can view a list of steps to determine whether your Simple Mail Transfer Protocol (SMTP) is working correctly." />
<meta name="description" content="You can view a list of steps to determine whether your Simple Mail Transfer Protocol (SMTP) is working correctly." />
<meta name="DC.Relation" scheme="URI" content="rzaiqlogserr.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiq501_desc.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiqlepi.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiqonavnote.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaiqtroubledetermine" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Determine problems with File Transfer Protocol</title>
</head>
<body id="rzaiqtroubledetermine"><a name="rzaiqtroubledetermine"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Determine problems with File Transfer Protocol</h1>
<div><p>You can view a list of steps to determine whether your Simple Mail
Transfer Protocol (SMTP) is working correctly.</p>
<p>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.</p>
<div class="fignone"><span class="figcap">Figure 1. FTP problem analysis</span><br /><img src="rzaiq501.gif" longdesc="rzaiq501_desc.htm" alt="FTP problem analysis flow chart" /><br /></div>
<div class="section" xml:lang="en-us" id="rzaiqtroubledetermine__CauseListA"><a name="rzaiqtroubledetermine__CauseListA"><!-- --></a><h4 class="sectiontitle">Cause list A</h4><ol><li>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.</li>
<li>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.</li>
<li>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.</li>
<li>Set up a password on the remote system if required. You might need to
restart if you change the security information about the system.</li>
<li>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.</li>
</ol>
</div>
<div class="section" xml:lang="en-us" id="rzaiqtroubledetermine__CauseListB"><a name="rzaiqtroubledetermine__CauseListB"><!-- --></a><h4 class="sectiontitle">Cause list B</h4><ol><li>Make sure binary mode is in effect if you are transferring binary files.</li>
<li>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.</li>
<li>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.</li>
<li>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.</li>
<li>Make sure that you are authorized to use the file and the file members.</li>
<li>Check to see if the transfer file contains packed decimal or zoned decimal
data.</li>
<li>If you are transferring a Save file, verify that the appropriate method
was used.</li>
</ol>
</div>
<div class="section" xml:lang="en-us" id="rzaiqtroubledetermine__CauseListC"><a name="rzaiqtroubledetermine__CauseListC"><!-- --></a><h4 class="sectiontitle">Cause list C</h4><ol><li>Check file size limits on the remote system.</li>
<li>Check to see if the FTP server timer ended. The iSeries server time-out value can be
set using the QUOTE TIME command.</li>
<li>Use the NETSTAT command to verify that the *LOOPBACK interface is active.
Then re-create the problem doing FTP LOOPBACK (iSeries-to-iSeries internally).<ul><li>If the problem cannot be recreated, it is probably a remote system problem.</li>
<li>If you can re-create the problem, complete the following steps: <ol type="a"><li>If the problem is an FTP server problem, then start the FTP server trace
using the TRCTCPAPP command.</li>
<li>Create the problem again.</li>
<li>End the FTP connection. Refer to the Starting and stopping the FTP server.</li>
<li>End the FTP server trace using the TRCTCPAPP command.</li>
<li>Find a spooled file with the following characteristics: <ul><li>The file name is QTMFFTRC</li>
<li>The username associated with the file is the name of the user who issued
the TRCTCPAPP command.</li>
</ul>
<p>The trace is a spooled file in the default output queue of the system
associated with the FTP server job.</p>
</li>
<li>Send in that spooled file.</li>
<li>If the problem was on the iSeries FTP client, a trace can be obtained
using the DEBUG 100 client subcommand.</li>
<li>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.</li>
</ol>
</li>
</ul>
</li>
</ol>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzaiq501_desc.htm">Description: FTP problem analysis flow chart</a></strong><br />
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqlogserr.htm" title="This topic provides basic troubleshooting techniques for problems that occur with the FTP server or FTP client.">Troubleshoot FTP</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzaiqonavnote.htm" title="You can start and stop the File Transfer Protocol (FTP) server by using iSeries Navigator.">Start and stop the File Transfer Protocol server</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzaiqlepi.htm" title="You can control the authentication of users to a TCP/IP application server with the TCP/IP Application Server Logon exit point.">Server logon exit point</a></div>
</div>
</div>
</body>
</html>