<?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="Format of application-specific information parameter" /> <meta name="DC.Relation" scheme="URI" content="../apis/unix9.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="rzaiqfaps" /> <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>Format of application-specific information parameter</title> </head> <body id="rzaiqfaps"><a name="rzaiqfaps"><!-- --></a> <!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script> <h1 class="topictitle1">Format of application-specific information parameter</h1> <div><div class="section"><p>When the application identifier indicates the FTP server program, the application-specific information parameter has these field.</p> <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e21">Offset Dec</th> <th valign="top" id="d0e23">Offset Hex</th> <th valign="top" id="d0e25">Type</th> <th valign="top" id="d0e27">Field</th> </tr> </thead> <tbody><tr><td valign="top" headers="d0e21 ">0</td> <td valign="top" headers="d0e23 ">0</td> <td valign="top" headers="d0e25 ">BINARY(4)</td> <td valign="top" headers="d0e27 ">Initial name format</td> </tr> <tr><td valign="top" headers="d0e21 ">4</td> <td valign="top" headers="d0e23 ">4</td> <td valign="top" headers="d0e25 ">BINARY(4)</td> <td valign="top" headers="d0e27 ">Initial current working directory</td> </tr> <tr><td valign="top" headers="d0e21 ">8</td> <td valign="top" headers="d0e23 ">8</td> <td valign="top" headers="d0e25 ">BINARY(4)</td> <td valign="top" headers="d0e27 ">Initial file listing format</td> </tr> <tr><td valign="top" headers="d0e21 ">12</td> <td valign="top" headers="d0e23 ">C</td> <td valign="top" headers="d0e25 ">BINARY(4)</td> <td valign="top" headers="d0e27 ">Control connection security mechanism</td> </tr> <tr><td valign="top" headers="d0e21 ">16</td> <td valign="top" headers="d0e23 ">10</td> <td valign="top" headers="d0e25 ">BINARY(4)</td> <td valign="top" headers="d0e27 ">Data connection encryption option</td> </tr> <tr><td valign="top" headers="d0e21 ">20</td> <td valign="top" headers="d0e23 ">14</td> <td valign="top" headers="d0e25 ">BINARY(2)</td> <td valign="top" headers="d0e27 ">Control connection ciphersuite</td> </tr> <tr><td valign="top" headers="d0e21 ">22</td> <td valign="top" headers="d0e23 ">16</td> <td valign="top" headers="d0e25 ">BINARY(2)</td> <td valign="top" headers="d0e27 ">Data connection cyphersuite</td> </tr> </tbody> </table> </div> </div> <div class="section"><h4 class="sectiontitle">Field descriptions</h4><dl><dt class="dlterm">Initial name format</dt> <dd> Identifies the initial setting of the file name format for this session. When the exit program is called, the value of this field is set to correspond to the FTP server configuration file value specified by the NAMEFMT parameter. Valid values are:<dl><dt class="dlterm">0</dt> <dd>Use the LIBRARY/FILE.MEMBER name format. This setting corresponds to the NAMEFMT(*LIB) option of the CHGFTPA command and is equivalent to specifying the SITE NAMEFMT 0 subcommand to the FTP server.</dd> <dt class="dlterm">1</dt> <dd>Use the path name format. This setting corresponds to the NAMEFMT(*PATH) option of the CHGFTPA command and is equivalent to specifying the SITE NAMEFMT 1 subcommand to the FTP server.</dd> </dl> </dd> <dt class="dlterm">Initial current working directory</dt> <dd>Identifies the initial setting of the FTP server current working directory, which is the default directory that is used for file and list operations. When the exit program is called, the value of this field is set to correspond to the FTP server configuration values specified by the CURDIR. Valid values are:<dl><dt class="dlterm">0</dt> <dd>Use the current library as the initial FTP server current working directory. This setting corresponds to the CURDIR(*CURLIB) option of the CHGFTPA command.</dd> <dt class="dlterm">1</dt> <dd>Use the home directory as the initial FTP server current working directory. This setting corresponds to the CURDIR(*HOMEDIR) option of the CHGFTPA command.<div class="note"><span class="notetitle">Note:</span> If you set this field to 1, you must also set the initial name format field to 1.</div> </dd> </dl> </dd> <dt class="dlterm">Initial file list format</dt> <dd>Identifies the initial setting of the file list format for this session. When the exit program is called, the value of this field is set to correspond to the FTP server configuration value that you specify with the LISTFMT parameter. Valid values are:<dl><dt class="dlterm">0</dt> <dd>Use iSeries™ server file list format. This setting corresponds to the LISTFMT(*DFT) option of the CHGFTPA command and is equivalent to specifying the SITE LISTFMT 0 subcommand to the FTP Server.</dd> <dt class="dlterm">1</dt> <dd>Use the UNIX<sup>®</sup> file list format. This setting corresponds to the LISTFMT(*UNIX) option of the CHGFTPA command and is equivalent to specifying the SITE LISTFMT 1 subcommand to the FTP server.</dd> </dl> </dd> <dt class="dlterm">Control connection security mechanism</dt> <dd>Identifies the security mechanism used on to control connection for this FTP session. Valid values are:<dl><dt class="dlterm">0</dt> <dd>The control connection is not secured.</dd> <dt class="dlterm">1</dt> <dd>The control connection is secured using Secure Sockets Layer (SSL); the mechanism specified by the FTP client on the AUTH subcommand is TLS-P or SSL.</dd> <dt class="dlterm">2</dt> <dd>The control connection is secured using SSL; the mechanism specified by the client on the AUTH subcommand is TLS-C or TLS.</dd> </dl> <div class="note"><span class="notetitle">Notes:</span> <ul><li>This field is input only to the exit program. Changes made by the exit program are ignored.</li> <li>For sessions connecting to the secure FTP port, the value is set to 1. Connections to the secure FTP port act as if an implicit AUTH SSL subcommand has been sent to the FTP server.</li> </ul> </div> </dd> <dt class="dlterm">Data connection encryption option</dt> <dd>Specifies whether FTP data connections for this FTP session are to be encrypted. Valid values are:<dl><dt class="dlterm">-1</dt> <dd>Encryption of FTP data connections is not allowed for this FTP session.</dd> <dt class="dlterm">0</dt> <dd>Encryption of FTP data connections is allowed (but not required) for this FTP session.</dd> <dt class="dlterm">1</dt> <dd>Encryption of FTP data connections is required for this FTP session.</dd> </dl> <div class="note"><span class="notetitle">Notes:</span> <ul><li>If the control connection security mechanism value is 1, setting the data connection encryption option to -1 will require additional FTP subcommands from the client to successfully transfer data. (The TLS-P or SSL security mechanism encrypts data connections by default.)</li> <li>If the control connection security mechanism value is 2, setting the data connection encryption option to 1 will require additional FTP subcommands from the client to successfully transfer data. (The TLS-C or TLS security mechanism does not encrypt data connections by default.)</li> </ul> </div> </dd> <dt class="dlterm">Control connection ciphersuite</dt> <dd> Identifies the SSL ciphersuite used to encrypt on the control connection for this FTP session. Ciphersuite values are defined in the Secure Sockets Layer (SSL) APIs. <div class="note"><span class="notetitle">Notes:</span> <ul><li>This field is input only to the exit program. Changes made by the exit program are ignored.</li> <li>This value is valid only when the control connection security mechanism value is 1 or 2.</li> </ul> </div> </dd> <dt class="dlterm">Data connection ciphersuite</dt> <dd>Identifies the SSL ciphersuite used to encrypt data on data connection for this FTP session. When the exit program is called, this value is set to 0, which means to allow the secure sockets layer support negotiate the ciphersuite to be used. If the exit program changes this field, a valid ciphersuite value must be specified. Ciphersuite values are defined in the Secure Sockets Layer (SSL) APIs. <div class="note"><span class="notetitle">Notes:</span> <ul><li>This field ignored if the control connection security mechanism is 0 or the data connection encryption option is -1.</li> <li>Setting this field to a value other than 0 or the value specified in the control connection ciphersuite field might result in failure to perform an SSL handshake between the FTP server and the FTP client, because the specified ciphersuite might not be supported by the FTP client.</li> </ul> </div> </dd> </dl> </div> </div> <div><div class="relref"><strong>Related reference</strong><br /> <div><a href="../apis/unix9.htm">Secure Sockets Layer (SSL) APIs</a></div> </div> </div> </body> </html>