147 lines
9.5 KiB
HTML
147 lines
9.5 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="File Transfer Protocol exit programs" />
|
|
<meta name="abstract" content="You can use File Transfer Protocol (FTP) exit programs to secure FTP. The FTP server communicates with each exit program through a specific exit point. This topic includes parameter descriptions and code examples." />
|
|
<meta name="description" content="You can use File Transfer Protocol (FTP) exit programs to secure FTP. The FTP server communicates with each exit program through a specific exit point. This topic includes parameter descriptions and code examples." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqreference.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqsvreqep.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqlepi.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqremep.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqextprog.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqseccontrolaccess.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqftpscon.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqinstep.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="rzaiqreferenceexit" />
|
|
<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>File Transfer Protocol exit programs</title>
|
|
</head>
|
|
<body id="rzaiqreferenceexit"><a name="rzaiqreferenceexit"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">File Transfer Protocol exit programs</h1>
|
|
<div><p>You can use File Transfer Protocol (FTP) exit programs
|
|
to secure FTP. The FTP server communicates with each exit program through
|
|
a specific exit point. This topic includes parameter descriptions and code
|
|
examples.</p>
|
|
<div class="section"><p>The FTP client and the FTP server communicate with each exit program
|
|
through a specific exit point. Parameters are passed between the server and
|
|
the exit program. The format of the exchanged information is specified by
|
|
an exit point format.</p>
|
|
<p>FTP uses the following exit points. Refer to these
|
|
topics for more information, including parameter descriptions and code examples:</p>
|
|
<ul><li>Request validation exit point: client and server</li>
|
|
<li>Server logon exit point</li>
|
|
</ul>
|
|
<p>To allow the exit programs to work properly, you must install and
|
|
register your exit point programs. If your programs are no longer needed,
|
|
you must properly remove the exit point programs to prevent their future functioning.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">TCP/IP exit points and exit point formats</h4><p>The following
|
|
table provides information about exit points for various TCP/IP applications
|
|
and their related exit point formats.</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="37.5%" id="d0e54">TCP/IP Exit Points</th>
|
|
<th valign="top" width="12.5%" id="d0e56">Application</th>
|
|
<th valign="top" width="12.5%" id="d0e58"><a href="rzaiqpsvrep.htm">VLRQ0100</a></th>
|
|
<th valign="top" width="12.5%" id="d0e61"><a href="rzaiql0100.htm">TCPL0100</a></th>
|
|
<th valign="top" width="12.5%" id="d0e64"><a href="rzaiql0200.htm">TCPL0200</a></th>
|
|
<th valign="top" width="12.5%" id="d0e67"><a href="rzaiql0300.htm">TCPL0300</a></th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="37.5%" headers="d0e54 "><a href="rzaiqsvreqep.htm">QIBM_QTMF_CLIENT_REQ</a></td>
|
|
<td valign="top" width="12.5%" headers="d0e56 ">FTP</td>
|
|
<td valign="top" width="12.5%" headers="d0e58 ">X</td>
|
|
<td valign="top" width="12.5%" headers="d0e61 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e64 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e67 "> </td>
|
|
</tr>
|
|
<tr><td valign="top" width="37.5%" headers="d0e54 "><a href="rzaiqsvreqep.htm">QIBM_QTMF_SERVER_REQ</a></td>
|
|
<td valign="top" width="12.5%" headers="d0e56 ">FTP</td>
|
|
<td valign="top" width="12.5%" headers="d0e58 ">X</td>
|
|
<td valign="top" width="12.5%" headers="d0e61 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e64 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e67 "> </td>
|
|
</tr>
|
|
<tr><td valign="top" width="37.5%" headers="d0e54 "><a href="rzaiqlepi.htm">QIBM_QTMF_SVR_LOGON</a> <sup>1</sup></td>
|
|
<td valign="top" width="12.5%" headers="d0e56 ">FTP</td>
|
|
<td valign="top" width="12.5%" headers="d0e58 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e61 ">X</td>
|
|
<td valign="top" width="12.5%" headers="d0e64 ">X</td>
|
|
<td valign="top" width="12.5%" headers="d0e67 ">X <sup>2</sup></td>
|
|
</tr>
|
|
<tr><td valign="top" width="37.5%" headers="d0e54 ">QIBM_QTMX_SERVER_REQ</td>
|
|
<td valign="top" width="12.5%" headers="d0e56 ">REXEC</td>
|
|
<td valign="top" width="12.5%" headers="d0e58 ">X</td>
|
|
<td valign="top" width="12.5%" headers="d0e61 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e64 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e67 "> </td>
|
|
</tr>
|
|
<tr><td valign="top" width="37.5%" headers="d0e54 ">QIBM_QTMX_SVR_LOGON <sup>1</sup></td>
|
|
<td valign="top" width="12.5%" headers="d0e56 ">REXEC</td>
|
|
<td valign="top" width="12.5%" headers="d0e58 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e61 ">X</td>
|
|
<td valign="top" width="12.5%" headers="d0e64 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e67 ">X <sup>2</sup></td>
|
|
</tr>
|
|
<tr><td valign="top" width="37.5%" headers="d0e54 ">QIBM_QTOD_SERVER_REQ</td>
|
|
<td valign="top" width="12.5%" headers="d0e56 ">TFTP</td>
|
|
<td valign="top" width="12.5%" headers="d0e58 ">X</td>
|
|
<td valign="top" width="12.5%" headers="d0e61 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e64 "> </td>
|
|
<td valign="top" width="12.5%" headers="d0e67 "> </td>
|
|
</tr>
|
|
<tr><td colspan="6" valign="top" headers="d0e54 d0e56 d0e58 d0e61 d0e64 d0e67 "><p><strong><sup>1</sup></strong> - An exit point
|
|
can have more than one format, but an exit program can only be registered
|
|
for one of the exit point formats. Examine each of these formats, then choose
|
|
the one most appropriate for your system.</p>
|
|
<p><strong><sup>2</sup></strong> - This
|
|
format is available starting with V5R1.</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaiqsvreqep.htm">Request validation exit point: Client and server</a></strong><br />
|
|
The Request Validation exit points can be used to restrict operations which can be performed by FTP users. Request validation exit points are provided by both the FTP client and server; to restrict both FTP client and FTP server access, exit programs must be added to both exit points.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaiqlepi.htm">Server logon exit point</a></strong><br />
|
|
You can control the authentication of users to a TCP/IP application server with the TCP/IP Application Server Logon exit point.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaiqremep.htm">Remove exit programs</a></strong><br />
|
|
You can remove an installed exit program.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqreference.htm" title="You can find information about server and client subcommands, File Transfer Protocol (FTP) exit programs, data transfer methods, and more.">File Transfer Protocol reference information</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaiqseccontrolaccess.htm" title="If you are using File Transfer Protocol (FTP), you need to control users to protect your data and network. This topic offers tips and security considerations.">Control File Transfer Protocol access</a></div>
|
|
<div><a href="rzaiqftpscon.htm" title="You can use File Transfer Protocol (FTP) exit points to protect the iSeries from this topic.">Manage access using File Transfer Protocol exit programs</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzaiqinstep.htm" title="You can create a library to contain your exit programs and their log files, compile the programs, and register them for use by the File Transfer Protocol (FTP) server.">Install and register exit programs</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzaiqextprog.htm" title="To use anonymous File Transfer Protocol (FTP), you need to write two exit programs: FTP Server Logon exit program and FTP Server Request Validation exit program.">Write exit programs for anonymous File Transfer Protocol</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |