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

91 lines
5.4 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="reference" />
<meta name="DC.Title" content="SENDPASV (Specify Whether to send a PASV Subcommand)" />
<meta name="DC.Relation" scheme="URI" content="rzaiqclientsu.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiqsendport.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiqcsubcs.htm" />
<meta name="DC.Relation" scheme="URI" content="http://www.rfc-editor.org/rfcsearch.html" />
<meta name="DC.Relation" scheme="URI" content="http://www.rfc-editor.org/" />
<meta name="DC.Relation" scheme="URI" content="rzaiqsendport.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="rzaiqsendpasv" />
<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>SENDPASV (Specify Whether to send a PASV Subcommand)</title>
</head>
<body id="rzaiqsendpasv"><a name="rzaiqsendpasv"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">SENDPASV (Specify Whether to send a PASV Subcommand)</h1>
<div><div class="section"><h4 class="sectiontitle">FTP client subcommand</h4><p>To specify whether or not
to send a PASV subcommand to the FTP server when doing a data transfer or
issuing the DIR and LS subcommands, enter the SENDPASV FTP client subcommand:</p>
<div class="figborder"><p>SENDPAsv [ 0 | 1 ]</p>
</div>
<p>If there is no parameter SENDPASV works like a toggle switch. The
SENDPASV value toggles from 1 (ON) to 0 (OFF) or from 0 to 1.</p>
<p>When there
is a parameter, the valid values are:</p>
<dl><dt class="dlterm">0</dt>
<dd>Do not send a PASV subcommand.</dd>
<dt class="dlterm">1</dt>
<dd>Send a PASV subcommand. This is the default.</dd>
</dl>
<p>iSeries™ default (on) is to send the PASV subcommand.
When SENDPASV is off, then the server does not send the PASV subcommand.</p>
<div class="note"><span class="notetitle">Notes:</span> <ol><li>This subcommand supports RFC 1579, "Firewall-Friendly FTP." Use of the
PASV subcommand to establish a data connection is a better method when a data
transfer must go through a firewall. In some scenarios, a data transfer through
a firewall might not be possible without use of PASV.</li>
<li>Some FTP servers might not support the PASV subcommand. When this is the
situation and SENDPASV is ON, then the FTP client will display a message that
indicates that the server does not support PASV. The system will attempt to
establish the data connection without sending the PASV subcommand.</li>
<li>When SENDPASV is OFF or disabled, then the server sends the PORT subcommand
when SENDPORT is ON.</li>
<li>FTP servers that do not support PASV are not compliant with RFC 1123.</li>
</ol>
</div>
<div class="restriction"><span class="restrictiontitle">Restriction:</span> <p>When connected to
an FTP server through a SOCKS server, you can only use the SENDPASV subcommand
before you issue a data transfer subcommand or a list directory subcommand.
If you use SENDPASV after one of these subcommands, then the client cannot
be able to establish a data connection to the FTP server.</p>
<p>After the
client has issued a data transfer or list directory subcommand, then close
the connection to the FTP server through a SOCKS server before you issue SENDPASV
again.</p>
<p>You can use the SENDPASV subcommand when the FTP client is disconnected
from an FTP server.</p>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqclientsu.htm" title="Use File Transfer Protocol (FTP) client subcommands to establish a connection with a remote FTP server, navigate libraries and directories, create and delete files, and transfer files.">File Transfer Protocol client subcommands</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzaiqsendport.htm">SENDPORT (Specify Whether to Sends a PORT Subcommand)</a></div>
<div><a href="rzaiqcsubcs.htm" title="The File Transfer Protocol (FTP) client subcommands described in this topic make use of syntax conventions:">File Transfer Protocol client syntax conventions</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="http://www.rfc-editor.org/rfcsearch.html">RFC index search engine</a></div>
<div><a href="http://www.rfc-editor.org/">RFC editor</a></div>
</div>
</div>
</body>
</html>