88 lines
5.9 KiB
HTML
88 lines
5.9 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Exit points for controlling TFTP server" />
|
||
|
|
<meta name="abstract" content="With the use of exit programs, the experienced programmer can create customized processing when an application is running. If the TFTP server finds a program registered to one of the exit points for the server, it calls that program using parameters that are defined by the exit point." />
|
||
|
|
<meta name="description" content="With the use of exit programs, the experienced programmer can create customized processing when an application is running. If the TFTP server finds a program registered to one of the exit points for the server, it calls that program using parameters that are defined by the exit point." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzal5overview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaii/rzaiimst31.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzal5tftpexitpoint" />
|
||
|
|
<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>Exit points for controlling TFTP server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzal5tftpexitpoint"><a name="rzal5tftpexitpoint"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Exit points for controlling TFTP server</h1>
|
||
|
|
<div><p>With the use of exit programs, the experienced programmer can create
|
||
|
|
customized processing when an application is running. If the
|
||
|
|
TFTP server finds a program registered to one of the exit points for the server,
|
||
|
|
it calls that program using parameters that are defined by the exit point.</p>
|
||
|
|
<p>An exit point is a specific point in the TFTP program where control may
|
||
|
|
pass to an exit program. An exit program is a program to which the exit point
|
||
|
|
passes control.</p>
|
||
|
|
<p>For each exit point, there is an associated programming interface, called
|
||
|
|
an exit point interface. The exit point uses this interface to pass information
|
||
|
|
between the TFTP application and the exit program. Each exit point has a unique
|
||
|
|
name. Each exit point interface has an exit point format name that defines
|
||
|
|
how information is passed between the TFTP application and the customer-written
|
||
|
|
exit program.</p>
|
||
|
|
<p>Different exit points may share the same exit point interface. When this
|
||
|
|
is the case, multiple exit points can call a single exit program.</p>
|
||
|
|
<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.
|
||
|
|
For more information about using exit programs, see Using server exit programs.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Exit point performance</h4><p>The following table lists
|
||
|
|
exit points that give you additional control over the TFTP server.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. TFTP exit point and format</caption><thead align="left"><tr><th valign="top" width="34.66334164588529%" id="d0e38">TCP/IP exit point</th>
|
||
|
|
<th valign="top" width="18.952618453865338%" id="d0e40">Application</th>
|
||
|
|
<th valign="top" width="22.942643391521198%" id="d0e42">Exit point format</th>
|
||
|
|
<th valign="top" width="23.44139650872818%" id="d0e44">Brief description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="34.66334164588529%" headers="d0e38 ">QIBM_QTOD_SERVER_REQ</td>
|
||
|
|
<td valign="top" width="18.952618453865338%" headers="d0e40 ">TFTP</td>
|
||
|
|
<td valign="top" width="22.942643391521198%" headers="d0e42 "><a href="../rzaiq/rzaiqpsvrep.htm">VLRQ0100</a></td>
|
||
|
|
<td valign="top" width="23.44139650872818%" headers="d0e44 ">The TCP/IP request validation exit point provides
|
||
|
|
additional control for restricting an operation.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<div class="note"><span class="notetitle">Notes:</span> <ul><li>The same interface format is used for request validation for the FTP client,
|
||
|
|
FTP server, REXEC server, and TFTP server. This allows the use of one exit
|
||
|
|
program for request validation of any combination of these applications.</li>
|
||
|
|
<li>The same interface format is used for server log-on processing for the
|
||
|
|
FTP server and TFTP server applications. This allows the use of one exit program
|
||
|
|
to process log-on requests for both of these applications.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzal5overview.htm" title="Trivial File Transfer Protocol (TFTP) is a simple protocol that provides basic file transfer function with no user authentication.">Trivial File Transfer Protocol</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzaii/rzaiimst31.htm">Using server exit programs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|