343 lines
16 KiB
HTML
343 lines
16 KiB
HTML
|
|
||
|
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
<html>
|
||
|
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
<title>Start TCP/IP File Transfer (FTP)</title>
|
||
|
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
|
||
|
</head>
|
||
|
<body bgcolor="white">
|
||
|
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<a name="FTP.Top_Of_Page"></a>
|
||
|
<h2>Start TCP/IP File Transfer (FTP)</h2>
|
||
|
<table width="100%">
|
||
|
<tr>
|
||
|
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
|
||
|
<b>Threadsafe: </b>No
|
||
|
</td>
|
||
|
<td valign="top" align="right">
|
||
|
<a href="#FTP.PARAMETERS.TABLE">Parameters</a><br>
|
||
|
<a href="#FTP.COMMAND.EXAMPLES">Examples</a><br>
|
||
|
<a href="#STRTCPFTP.ERROR.MESSAGES">Error messages</a></td>
|
||
|
</tr>
|
||
|
</table>
|
||
|
|
||
|
<div> <a name="STRTCPFTP"></a>
|
||
|
<p>The Start TCP/IP File Transfer Protocol (STRTCPFTP) command is used to start the File Transfer Protocol (FTP) client application that transfers files between systems using the Transmission Control Protocol/Internet Protocol (TCP/IP). FTP is an application protocol used for transferring files to and from a remote system. FTP requires a user ID, and in some cases a password, to gain access to files on a remote system.
|
||
|
</p>
|
||
|
<p><b>Mapping Parameters:</b> Mapping of data is used for all data (for example, user data and protocol data information) between the local and remote systems, except when the EBCDIC subcommand or the BINARY subcommand is in effect. In these cases, mapping of user file data is not done.
|
||
|
</p>
|
||
|
<p>The Change FTP Attributes (CHGFTPA) command can be used to specify server mapping tables for FTP.
|
||
|
</p>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<hr size="2" width="100%">
|
||
|
|
||
|
<div>
|
||
|
<h3><a name="FTP.PARAMETERS.TABLE">Parameters</a></h3>
|
||
|
<table border="1" cellpadding="4" cellspacing="0">
|
||
|
<!-- col1="10" col2="15" col3="30" col4="10" -->
|
||
|
<tr>
|
||
|
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
|
||
|
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
|
||
|
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
|
||
|
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top"><a href="#STRTCPFTP.RMTSYS"><b>RMTSYS</b></a></td>
|
||
|
<td valign="top">Remote system</td>
|
||
|
<td valign="top"><i>Character value</i>, *INTNETADR</td>
|
||
|
<td valign="top">Required, Positional 1</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top"><a href="#STRTCPFTP.INTNETADR"><b>INTNETADR</b></a></td>
|
||
|
<td valign="top">Internet address</td>
|
||
|
<td valign="top"><i>Character value</i></td>
|
||
|
<td valign="top">Optional</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top"><a href="#STRTCPFTP.CCSID"><b>CCSID</b></a></td>
|
||
|
<td valign="top">Coded character set identifier</td>
|
||
|
<td valign="top">1-65533, <b><u>*DFT</u></b></td>
|
||
|
<td valign="top">Optional</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top"><a href="#STRTCPFTP.PORT"><b>PORT</b></a></td>
|
||
|
<td valign="top">Port</td>
|
||
|
<td valign="top">1-65535, <b><u>*DFT</u></b>, *SECURE</td>
|
||
|
<td valign="top">Optional</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top"><a href="#STRTCPFTP.SECCNN"><b>SECCNN</b></a></td>
|
||
|
<td valign="top">Secure connection</td>
|
||
|
<td valign="top"><b><u>*DFT</u></b>, *NONE, *SSL, *IMPLICIT</td>
|
||
|
<td valign="top">Optional</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top"><a href="#STRTCPFTP.DTAPROT"><b>DTAPROT</b></a></td>
|
||
|
<td valign="top">Data protection</td>
|
||
|
<td valign="top"><b><u>*DFT</u></b>, *CLEAR, *PRIVATE</td>
|
||
|
<td valign="top">Optional</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top" rowspan="3"><a href="#STRTCPFTP.TBLFTPOUT"><b>TBLFTPOUT</b></a></td>
|
||
|
<td valign="top">Outgoing EBCDIC/ASCII table</td>
|
||
|
<td valign="top">Single values: <b><u>*CCSID</u></b>, *DFT<br>Other values: <i>Qualified object name</i></td>
|
||
|
<td valign="top" rowspan="3">Optional</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top">Qualifier 1: Outgoing EBCDIC/ASCII table</td>
|
||
|
<td valign="top"><i>Name</i></td>
|
||
|
</tr><tr>
|
||
|
<td valign="top">Qualifier 2: Library</td>
|
||
|
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
|
||
|
</tr><tr>
|
||
|
<td valign="top" rowspan="3"><a href="#STRTCPFTP.TBLFTPIN"><b>TBLFTPIN</b></a></td>
|
||
|
<td valign="top">Incoming ASCII/EBCDIC table</td>
|
||
|
<td valign="top">Single values: <b><u>*CCSID</u></b>, *DFT<br>Other values: <i>Qualified object name</i></td>
|
||
|
<td valign="top" rowspan="3">Optional</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td valign="top">Qualifier 1: Incoming ASCII/EBCDIC table</td>
|
||
|
<td valign="top"><i>Name</i></td>
|
||
|
</tr><tr>
|
||
|
<td valign="top">Qualifier 2: Library</td>
|
||
|
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
|
||
|
</tr></table>
|
||
|
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
</div>
|
||
|
<div> <a name="STRTCPFTP.RMTSYS"></a>
|
||
|
<h3>Remote system (RMTSYS)</h3>
|
||
|
<p>Specifies the remote system name to which or from which the files are transferred. To be successful, the remote system name must be valid, and the system must be able to communicate with the local system. The user can assign names to an internet address with the Work with TCP/IP host table entries option on the Configure TCP/IP menu (CFGTCP command). Also, a remote name server can be used to map remote system names to internet addresses. You can use the Change remote name server option on the CFGTCP menu to specify a remote name server.
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b>*INTNETADR</b></dt>
|
||
|
<dd>The INTNETADR parameter is prompted.
|
||
|
</dd>
|
||
|
<dt><b><i>character-value</i></b></dt>
|
||
|
<dd>Specify the remote system name to which or from which the file transfer takes place.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<div> <a name="STRTCPFTP.INTNETADR"></a>
|
||
|
<h3>Internet address (INTNETADR)</h3>
|
||
|
<p>Specifies the internet address of the remote system to which or from which the file transfer takes place. The internet address is specified in the form, <i>nnn.nnn.nnn.nnn</i>, where <i>nnn</i> is a decimal number ranging from 0 through 255. An internet address is not valid if it has a value of all binary ones or all binary zeros for the network identifier (ID) portion or the host ID portion of the address. If the internet address is entered from a command line, the address must be enclosed in apostrophes.
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><i>character-value</i></b></dt>
|
||
|
<dd>Specify the internet address of the remote system.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<div> <a name="STRTCPFTP.CCSID"></a>
|
||
|
<h3>Coded character set identifier (CCSID)</h3>
|
||
|
<p>Specifies the ASCII coded character set identifier (CCSID) that is used for single-byte character set (SBCS) ASCII file transfers when the FTP TYPE mode is set to ASCII. ASCII file transfers are also assumed when no TYPE subcommand has been issued. The CCSID value chosen is the default used by the FTP client for ASCII-to-EBCDIC and EBCDIC-to-ASCII mapping. Mapping is determined using the specified ASCII CCSID and the EBCDIC CCSID of the job.
|
||
|
</p>
|
||
|
<p>Outgoing and incoming mapping can be done optionally with mapping tables defined in the TBLFTPOUT and TBLFTPIN parameters. Normally the TBLFTPOUT and TBLFTPIN parameters are set to the default of *CCSID or *DFT. Both parameters indicate that the value used in the CCSID parameter is used for mapping. If a mapping table is to be used for outgoing mapping, a table object can be specified in the TBLFTPOUT parameter. The table object specified in the TBLFTPOUT parameter is used instead of the CCSID value.
|
||
|
</p>
|
||
|
<p>Incoming mapping can be changed to use a mapping table by specifying a table object in the TBLFTPIN parameter. This mapping table overrides the specified CCSID value and is used for incoming mapping.
|
||
|
</p>
|
||
|
<p>Double-byte character set (DBCS) CCSID values are not permitted for this parameter. DBCS values can be specified using the TYPE subcommand.
|
||
|
</p>
|
||
|
<p>
|
||
|
<b>Note: </b>IBM includes mapping support in FTP to ensure compatibility with releases prior to V3R1. Use of mapping tables for incoming TYPE A file transfers results in the loss of CCSID tagging if the target file must be created. IBM strongly recommends that you use CCSID support for normal operations.
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*DFT</u></b></dt>
|
||
|
<dd>The CCSID value 00819 (ISO 8859-1 8-bit ASCII) is used.
|
||
|
</dd>
|
||
|
<dt><b><i>1-65533</i></b></dt>
|
||
|
<dd>Specify the CCSID value to be used. This value is validated to ensure a valid SBCS CCSID was requested.
|
||
|
<p>The TBLFTPOUT and TBLFTPIN parameters are used to specify user-defined incoming and outgoing mapping tables. The user-defined mapping tables replace the mapping done by the FTP client when the CCSID parameter is specified.
|
||
|
</p>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<div> <a name="STRTCPFTP.PORT"></a>
|
||
|
<h3>Port (PORT)</h3>
|
||
|
<p>Specifies the port number to be used for connecting to the FTP server.
|
||
|
</p>
|
||
|
<p>Normally the "well-known" port value of 21 is used to connect to the FTP server. Under some circumstances, the FTP server may be contacted at a port other than port 21. In those situations, the port parameter may be used to specify the server port to connect to.
|
||
|
</p>
|
||
|
<p>
|
||
|
<b>Note: </b>The FTP client subcommands OPEN and SECOPEN each have an optional 'port' parameter which may be used to specify a port other than port 21.
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*DFT</u></b></dt>
|
||
|
<dd>The value 00021 is used.
|
||
|
</dd>
|
||
|
<dt><b>*SECURE</b></dt>
|
||
|
<dd>The value 00990 is used. Port 990 is reserved for secure FTP servers which immediately use Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols to encrypt data.
|
||
|
</dd>
|
||
|
<dt><b><i>1-65535</i></b></dt>
|
||
|
<dd>The requested port value is used. This value is validated to ensure it is in the proper range.
|
||
|
<p>
|
||
|
<b>Note: </b>If 990 is specified, the FTP client will perform the same functions as if *SECURE were specified.
|
||
|
</p>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<div> <a name="STRTCPFTP.SECCNN"></a>
|
||
|
<h3>Secure connection (SECCNN)</h3>
|
||
|
<p>Specifies the type of security mechanism to be used for protecting information transferred on the FTP control connection (which includes the password used to authenticate the session with the FTP server). Transport Layer Security (TLS) and Secure Sockets Layer (SSL) are compatible protocols which use encryption to protect data from being viewed during transmission and verify that data loss or corruption does not occur.
|
||
|
</p>
|
||
|
<p>
|
||
|
<b>Note: </b>The FTP client subcommand SECOPEN can be used to open a protected FTP connection during an FTP client session.
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*DFT</u></b></dt>
|
||
|
<dd>If the PORT parameter specifies *SECURE or 990, *IMPLICIT is used; otherwise, *NONE is used.
|
||
|
</dd>
|
||
|
<dt><b>*IMPLICIT</b></dt>
|
||
|
<dd>The FTP client immediately attempts to use TLS/SSL when connecting to the specified FTP server (without sending an AUTH subcommand to the server). If the server does not support implicit TLS/SSL on the specified port, or the TLS/SSL negotiation fails for any reason, the connection is closed.
|
||
|
</dd>
|
||
|
<dt><b>*SSL</b></dt>
|
||
|
<dd>After connecting to the specified FTP server, the FTP client sends an AUTH (authorization) subcommand requesting a TLS/SSL protected session. If the server supports TLS/SSL, a TLS/SSL negotiation performed. If the server does not support TLS/SSL or the TLS/SSL negotiation fails, the connection is closed.
|
||
|
</dd>
|
||
|
<dt><b>*NONE</b></dt>
|
||
|
<dd>The FTP client does not use encryption when connecting to the specified FTP server.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<div> <a name="STRTCPFTP.DTAPROT"></a>
|
||
|
<h3>Data protection (DTAPROT)</h3>
|
||
|
<p>Specifies the type of data protection to be used for information transferred on the FTP data connection. This connection is used to transfer file data and directory listings. The FTP protocol does not allow protection of the data connection if the control connection is not protected.
|
||
|
</p>
|
||
|
<p>
|
||
|
<b>Note: </b>The DTAPROT parameter controls the use of the PROT (protection) FTP server subcommand. The FTP client subcommand SECDATA can be used to change protection for specific FTP data connections during an FTP client session.
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*DFT</u></b></dt>
|
||
|
<dd>If the SECCNN parameter specifies a protected control connection, *PRIVATE is used; otherwise, *CLEAR is used.
|
||
|
</dd>
|
||
|
<dt><b>*PRIVATE</b></dt>
|
||
|
<dd>Information sent on the FTP data connection is encrypted.
|
||
|
<p>
|
||
|
<b>Note: </b>If the SECCNN parameter specifies that the FTP control connection is not encrypted, *PRIVATE cannot be specified.
|
||
|
</p>
|
||
|
</dd>
|
||
|
<dt><b>*CLEAR</b></dt>
|
||
|
<dd>Information sent on the FTP data connection is not encrypted.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<div> <a name="STRTCPFTP.TBLFTPOUT"></a>
|
||
|
<h3>Outgoing ASCII/EBCDIC table (TBLFTPOUT)</h3>
|
||
|
<p>Specifies the table object that is to be used to map all outgoing data in the FTP client. Outgoing data is mapped from EBCDIC to ASCII.
|
||
|
</p>
|
||
|
<p>If a table object is specified for TBLFTPOUT, the table object is used for outgoing mapping. Otherwise, the CCSID parameter is used to determine outgoing mapping.
|
||
|
</p>
|
||
|
<p><b>Single values</b>
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*CCSID</u></b></dt>
|
||
|
<dd>The CCSID parameter is used to determine outgoing mapping.
|
||
|
</dd>
|
||
|
<dt><b>*DFT</b></dt>
|
||
|
<dd>The CCSID parameter is used to determine outgoing mapping.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<p><b>Qualifier 1: Outgoing EBCDIC/ASCII table</b>
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><i>name</i></b></dt>
|
||
|
<dd>Specify the name of the table object to be used by the FTP client for mapping outgoing data.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<p><b>Qualifier 2: Library</b>
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*LIBL</u></b></dt>
|
||
|
<dd>All libraries in the user and system portions of the job's library list are searched until the first match is found.
|
||
|
</dd>
|
||
|
<dt><b>*CURLIB</b></dt>
|
||
|
<dd>The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.
|
||
|
</dd>
|
||
|
<dt><b><i>name</i></b></dt>
|
||
|
<dd>Specify the name of the library to be searched.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<div> <a name="STRTCPFTP.TBLFTPIN"></a>
|
||
|
<h3>Incoming ASCII/EBCDIC table (TBLFTPIN)</h3>
|
||
|
<p>Specifies the table object that is to be used to map all incoming data in the FTP client. Incoming data is mapped from ASCII to EBCDIC.
|
||
|
</p>
|
||
|
<p>If a table object is specified for TBLFTPIN, the table object is used for incoming mapping. Otherwise, the CCSID parameter is used to determine incoming mapping
|
||
|
</p>
|
||
|
<p><b>Single values</b>
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*CCSID</u></b></dt>
|
||
|
<dd>The CCSID parameter is used to determine incoming mapping.
|
||
|
</dd>
|
||
|
<dt><b>*DFT</b></dt>
|
||
|
<dd>The CCSID parameter is used to determine incoming mapping.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<p><b>Qualifier 1: Incoming ASCII/EBCDIC table</b>
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><i>name</i></b></dt>
|
||
|
<dd>Specify the name of the table object to be used by the FTP client for mapping incoming data.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<p><b>Qualifier 2: Library</b>
|
||
|
</p>
|
||
|
<dl>
|
||
|
<dt><b><u>*LIBL</u></b></dt>
|
||
|
<dd>All libraries in the user and system portions of the job's library list are searched until the first match is found.
|
||
|
</dd>
|
||
|
<dt><b>*CURLIB</b></dt>
|
||
|
<dd>The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.
|
||
|
</dd>
|
||
|
<dt><b><i>name</i></b></dt>
|
||
|
<dd>Specify the name of the library to be searched.
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<hr size="2" width="100%">
|
||
|
<div>
|
||
|
<h3><a name="FTP.COMMAND.EXAMPLES">Examples</a></h3>None
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
<hr size="2" width="100%">
|
||
|
<div><h3><a name="STRTCPFTP.ERROR.MESSAGES">Error messages</a> </h3>
|
||
|
<p>None
|
||
|
</p>
|
||
|
</div>
|
||
|
<table width="100%">
|
||
|
<tr><td align="right"><a href="#FTP.Top_Of_Page">Top</a></td></tr>
|
||
|
</table>
|
||
|
</body>
|
||
|
</html>
|