66 lines
3.6 KiB
HTML
66 lines
3.6 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="reference" />
|
||
|
|
<meta name="DC.Title" content="PORT (Data Port)" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqserversu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqsscsc.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="rzaiqport" />
|
||
|
|
<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>PORT (Data Port)</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiqport"><a name="rzaiqport"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">PORT (Data Port)</h1>
|
||
|
|
<div><div class="section"><h4 class="sectiontitle">FTP server subcommand</h4><p>To identify the
|
||
|
|
port on which the client will listen for a data connection, use the PORT FTP
|
||
|
|
server subcommand in this format:</p>
|
||
|
|
<div class="figborder"><p>PORT h1,h2,h3,h4,p1,p2</p>
|
||
|
|
</div>
|
||
|
|
<dl><dt class="dlterm">h <em>n</em></dt>
|
||
|
|
<dd>Represents the system IP address and is a character string that is a decimal
|
||
|
|
value between 0 and 255.</dd>
|
||
|
|
<dt class="dlterm">p <em>n</em></dt>
|
||
|
|
<dd>Represents the TCP port number and is a character string that is a decimal
|
||
|
|
value between 0 and 255.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>To convert the <samp class="codeph">p1</samp> and <samp class="codeph">p2</samp> values
|
||
|
|
to a TCP port number, use this formula:</p>
|
||
|
|
<pre> port = ( p1 * 256 ) + p2</pre>
|
||
|
|
<p>For
|
||
|
|
example, in this PORT subcommand:</p>
|
||
|
|
<pre> PORT 9,180,128,180,4,8</pre>
|
||
|
|
<p>the
|
||
|
|
port number is 1032 and the IP address is 9.180.128.180.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> After the
|
||
|
|
server closes the connection, it cannot connect to the same client IP address
|
||
|
|
and port number until a two-minute time delay has occurred as specified in
|
||
|
|
TCP/IP RFC 1122. The server can make a connection to the same client IP address
|
||
|
|
on a different port number without this restriction.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqserversu.htm" title="These subcommands represent communication between the client and server. This topic includes descriptions for iSeries CL-equivalent subcommands that are unique to iSeries FTP server.">File Transfer Protocol server subcommands</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzaiqsscsc.htm" title="The File Transfer Protocol (FTP) server subcommands described in this topic make use of syntax conventions:">File Transfer Protocol server syntax conventions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|