208 lines
14 KiB
HTML
208 lines
14 KiB
HTML
|
<?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="Trace the FTP server" />
|
||
|
|
<meta name="abstract" content="You can use the DBUG subcommand to track down problems on the FTP server." />
|
||
|
|
<meta name="description" content="You can use the DBUG subcommand to track down problems on the FTP server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqlogserr.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqreport.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqdbug.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="rzaiqtraceserver" />
|
||
|
|
<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>Trace the FTP server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiqtraceserver"><a name="rzaiqtraceserver"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Trace the FTP server</h1>
|
||
|
|
<div><p>You can use the DBUG subcommand to track down problems on the FTP
|
||
|
|
server.</p>
|
||
|
|
<p>The FTP server can be traced from any iSeries™ or non-iSeries server that runs
|
||
|
|
TCP/IP. There are two ways to trace the FTP server. The FTP server DBUG subcommand
|
||
|
|
traces within an FTP server session. The Trace TCP/IP Application (TRCTCPAPP)
|
||
|
|
command allows system wide tracing of all the FTP servers.</p>
|
||
|
|
<div class="section" xml:lang="en-us" id="rzaiqtraceserver__traceftpserver"><a name="rzaiqtraceserver__traceftpserver"><!-- --></a><h4 class="sectiontitle">Trace the FTP server
|
||
|
|
with the DBUG subcommand</h4><p>To trace the FTP server, follow these steps:</p>
|
||
|
|
<ol><li>Type <kbd class="userinput">QUOTE</kbd> <kbd class="userinput">DBUG</kbd> to start
|
||
|
|
the trace.<pre class="screen"> ___________________________________________________________________________________
|
||
|
|
| |
|
||
|
|
| File Transfer Protocol |
|
||
|
|
| |
|
||
|
|
| Previous FTP subcommands and messages: |
|
||
|
|
| Connecting to host name xxxxxnnn.xxxxxxxx.xxx.xxx at address |
|
||
|
|
| n.nnn.nn.nnn using port 21. |
|
||
|
|
| 220-QTCP at xxxxxnnn.xxxxxxxx.xxx.xxx. |
|
||
|
|
| 220 Connection will close if idle more than 5 minutes. |
|
||
|
|
| 215 i5/OS is the remote operating system. The TCP/IPversion is |
|
||
|
|
| "V4R4M0". |
|
||
|
|
| > |
|
||
|
|
| 331 Enter password. |
|
||
|
|
| 230 TEST logged on. |
|
||
|
|
| 250 Now using naming format "0". |
|
||
|
|
| 257 "QGPL" is current library. |
|
||
|
|
| > quote dbug |
|
||
|
|
| 250 Debug mode is now ON. |
|
||
|
|
| Enter an FTP subcommand. |
|
||
|
|
| ===> quote dbug |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
| F3=Exit F6=Print F9=Retrieve |
|
||
|
|
| F17=Top F18=Bottom F21=CL command line |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
|__________________________________________________________________________________|
|
||
|
|
</pre>
|
||
|
|
</li>
|
||
|
|
<li>Perform the FTP operation that you want to trace.</li>
|
||
|
|
<li>Type <kbd class="userinput">QUOTE </kbd><kbd class="userinput">DBUG</kbd> again to
|
||
|
|
end the trace. The trace creates a spooled file called QTMFFTRC. The default
|
||
|
|
output queue contains the spooled file. The user is always the name of the
|
||
|
|
user who was logged on to the FTP server when the trace was ended.</li>
|
||
|
|
<li>Type <kbd class="userinput">QUIT</kbd> to end the FTP session.</li>
|
||
|
|
<li>Enter the following command to find the output queue.<pre>DSPSYSVAL QPRTDEV</pre>
|
||
|
|
<p>For
|
||
|
|
example, the following display appears:</p>
|
||
|
|
<pre class="screen"> __________________________________________________________________________________
|
||
|
|
| |
|
||
|
|
| Display System Value |
|
||
|
|
| System value . . . . . : QPRTDEV |
|
||
|
|
| Description . . . . . : Printer device description |
|
||
|
|
| <span class="uicontrol">Printer</span> <span class="uicontrol">device</span> <span class="uicontrol">.</span> <span class="uicontrol">.</span> <span class="uicontrol">.</span> <span class="uicontrol">.</span> <span class="uicontrol">:</span> <span class="uicontrol">PRT01</span> <span class="uicontrol">Name</span> |
|
||
|
|
| |
|
||
|
|
</pre>
|
||
|
|
<p>The printer device is also the name of the default system output
|
||
|
|
queue.</p>
|
||
|
|
</li>
|
||
|
|
<li>Record the name of the printer device. In this example, PRT01 is the printer
|
||
|
|
device.</li>
|
||
|
|
<li>Press F12 (Cancel) to return to the display where you entered the DSPSYSVAL
|
||
|
|
command.</li>
|
||
|
|
<li>Type the following command:<pre>WRKOUTQ OUTQ(printer-device)</pre>
|
||
|
|
<p>Replace <samp class="codeph">printer-device</samp> with
|
||
|
|
the printer device recorded in the previous display. PRT01 is the output queue
|
||
|
|
in this example. For example, the following display appears:</p>
|
||
|
|
<pre class="screen"> __________________________________________________________________________________
|
||
|
|
| |
|
||
|
|
| Work with Output Queue |
|
||
|
|
| Queue: PRT01 Library: QGPL Status: RLS |
|
||
|
|
| Type options, press Enter. |
|
||
|
|
| 1=Send 2=Change 3=Hold 4=Delete 5=Display 6=Release 7=Messages |
|
||
|
|
| 8=Attributes 9=Work with printing status |
|
||
|
|
| Opt File User User Data Sts Pages Copies Form Type Pty |
|
||
|
|
| _ QTCPPRT QTCP QTMSMTP HLD 46 1 *STD 5 |
|
||
|
|
| <span class="uicontrol">_</span> <span class="uicontrol">QTMFFTRC</span> <span class="uicontrol">QSECOFR</span> <span class="uicontrol">HLD</span> <span class="uicontrol">44</span> <span class="uicontrol">1</span> <span class="uicontrol">*STD</span> <span class="uicontrol">5</span> |
|
||
|
|
|
|
||
|
|
</pre>
|
||
|
|
</li>
|
||
|
|
<li>Press F18 (Bottom) to get to the bottom of the spooled file list if More...appears
|
||
|
|
on the display.</li>
|
||
|
|
<li>Find the last file named QTMFFTRC with the same user as the user who was
|
||
|
|
logged on the FTP server when the trace was created.</li>
|
||
|
|
<li>Press F11 (View 2) to view the date and time of the file you want to work
|
||
|
|
with.</li>
|
||
|
|
<li>Verify that you are working with the most recent spooled file, QTMFFTRC.</li>
|
||
|
|
</ol>
|
||
|
|
<p>Indicate in the problem report that the trace was tried and it failed.
|
||
|
|
Send whatever trace information there is with the problem report.</p>
|
||
|
|
<p>The
|
||
|
|
following example uses the FTP server DBUG subcommand:</p>
|
||
|
|
<pre class="screen"> ___________________________________________________________________________________
|
||
|
|
| |
|
||
|
|
| File Transfer Protocol |
|
||
|
|
| |
|
||
|
|
| Previous FTP subcommands and messages: |
|
||
|
|
| Connecting to host name xxxxxnnn.xxxxxxxx.xxx.xxx at address |
|
||
|
|
| n.nnn.nn.nnn using port 21. |
|
||
|
|
| 220-QTCP at xxxxxnnn.nnnnnnnn.nnn.nnn. |
|
||
|
|
| 220 Connection will close if idle more than 5 minutes. |
|
||
|
|
| 215 i5/OS is the remote operating system. The TCP/IPversion is |
|
||
|
|
| "V4R4M0". |
|
||
|
|
| > |
|
||
|
|
| 331 Enter password. |
|
||
|
|
| 230 TEST logged on. |
|
||
|
|
| 250 Now using naming format "0". |
|
||
|
|
| 257 "QGPL" is current library. |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
| Enter an FTP subcommand. |
|
||
|
|
| ===> quote dbug |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
| F3=Exit F6=Print F9=Retrieve |
|
||
|
|
| F17=Top F18=Bottom F21=CL command line |
|
||
|
|
| |
|
||
|
|
| |
|
||
|
|
|__________________________________________________________________________________|
|
||
|
|
</pre>
|
||
|
|
</div>
|
||
|
|
<div class="section" xml:lang="en-us" id="rzaiqtraceserver__TRCTCPAPP"><a name="rzaiqtraceserver__TRCTCPAPP"><!-- --></a><h4 class="sectiontitle">Trace the FTP server with
|
||
|
|
the Trace TCP/IP Application (TRCTCPAPP) command</h4><p>The Trace TCP/IP
|
||
|
|
Application (TRCTCPAPP) command allows <em>system-wide</em> tracing of <em>all</em> the
|
||
|
|
FTP servers.</p>
|
||
|
|
<p>The TRCTCPAPP command is provided specifically for trained
|
||
|
|
service and development personnel. *SERVICE special authority is required
|
||
|
|
to use this command. Use TRCTCPAPP in situations that require the capturing
|
||
|
|
of trace data for service and development use. This command allows experienced
|
||
|
|
personnel to dynamically start and stop tracing for applications.</p>
|
||
|
|
<div class="p">With
|
||
|
|
the use of TRCTCPAPP, trace information can be captured for the FTP TCP/IP
|
||
|
|
application:<ul><li>Internal trace information can be captured for the iSeries FTP server. The information that
|
||
|
|
can be captured for the FTP server can be filtered using remote IP address
|
||
|
|
and port or iSeries user
|
||
|
|
profile. Only one trace can be active at a time on the system.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>Here are two examples of the use of the TRCTCPAPP command:</p>
|
||
|
|
<p><strong>Example
|
||
|
|
1:</strong></p>
|
||
|
|
<pre> TRCTCPAPP APP(*FTP) SET(*ON)</pre>
|
||
|
|
<p>This
|
||
|
|
will start tracing for all FTP servers. Tracing for all other TCP applications
|
||
|
|
is not affected.</p>
|
||
|
|
<p><strong>Example 2:</strong></p>
|
||
|
|
<pre> TRCTCPAPP APP(*FTP) SET(*CHK)</pre>
|
||
|
|
<p>This
|
||
|
|
command is used to check the status of the tracing for the FTP server job(s).
|
||
|
|
Assume that the last command entered was: > </p>
|
||
|
|
<pre> TRCTCPAPP APP(*FTP) SET(*ON) USER(JOECOOL)</pre>
|
||
|
|
<p>The
|
||
|
|
format of the response to this command would be a set of messages that would
|
||
|
|
look similar to the following commands: </p>
|
||
|
|
<pre> TCP45B7 TRCTCPAPP APP(*FTP) SET(*ON) USER(JOECOOL)
|
||
|
|
MAXSTG(*DFT) TRCFULL(*WRAP)
|
||
|
|
TCP45B1 Tracing active for *FTP.
|
||
|
|
TCP45B2 Data capture begun for *FTP.
|
||
|
|
TCP45B3 Data buffer wrapped for *FTP. </pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaiqreport.htm" title="This topic describes the information that the IBM service representative might require to resolve an FTP problem.">Materials required for reporting FTP problems</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzaiqdbug.htm">DBUG (Turn on the FTP Server Trace)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|