117 lines
7.3 KiB
HTML
117 lines
7.3 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="Exit points for controlling REXEC server" />
|
|
<meta name="abstract" content="This topic includes information about exit points that can be used for controlling REXEC server." />
|
|
<meta name="description" content="This topic includes information about exit points that can be used for controlling REXEC server." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzal7overview.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzal7rxcs0100.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaii/rzaiimst31.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaiq/rzaiqpsvrep.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaiq/rzaiql0100.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaiq/rzaiql0300.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="exitpt" />
|
|
<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 REXEC server</title>
|
|
</head>
|
|
<body id="exitpt"><a name="exitpt"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Exit points for controlling REXEC server</h1>
|
|
<div><p>This topic includes information about exit points that can be used
|
|
for controlling REXEC server.</p>
|
|
<div class="section"><p>With the use of exit programs, the experienced programmer can
|
|
create customized processing during an application. If the REXEC 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>
|
|
</div>
|
|
<div class="section"><p>An exit point is a specific point in the REXEC program where control
|
|
can pass to an exit program. An exit program is a program to which the exit
|
|
point passes control.</p>
|
|
</div>
|
|
<div class="section"><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 REXEC 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 REXEC application
|
|
and the customer-written exit program.</p>
|
|
</div>
|
|
<div class="section"><p>Different exit points can share the same exit point interface.
|
|
When this is the case, multiple exit points can call a single exit program.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Exit point performance</h4><p>The following
|
|
table lists exit points that give you additional control over the REXEC server.</p>
|
|
|
|
<div class="tablenoborder"><img src="./delta.gif" alt="Start of change" /><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 1. TCP/IP exit points </caption><thead align="left"><tr valign="bottom"><th valign="bottom" width="25.44642857142857%" id="d0e41">TCP/IP exit points </th>
|
|
<th valign="bottom" width="37.5%" id="d0e43">Brief description</th>
|
|
<th valign="bottom" width="37.05357142857143%" id="d0e45">Exit points formats used</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="25.44642857142857%" headers="d0e41 ">QIBM_QTMX_SERVER_REQ</td>
|
|
<td valign="top" width="37.5%" headers="d0e43 ">The TCP/IP request validation exit point provides additional
|
|
control for restricting an operation.</td>
|
|
<td valign="top" width="37.05357142857143%" headers="d0e45 ">VLRQ0100</td>
|
|
</tr>
|
|
<tr><td valign="top" width="25.44642857142857%" headers="d0e41 ">QIBM_QTMX_SVR_LOGON<sup>1</sup></td>
|
|
<td valign="top" width="37.5%" headers="d0e43 ">The TCP/IP server logon exit point provides additional
|
|
control over authenticating a user and setting up the user's environment for
|
|
the REXEC server. </td>
|
|
<td valign="top" width="37.05357142857143%" headers="d0e45 ">TCPL0100<p></p>
|
|
TCPL0300</td>
|
|
</tr>
|
|
<tr><td valign="top" width="25.44642857142857%" headers="d0e41 ">QIBM_QTMX_SVR_SELECT</td>
|
|
<td valign="top" width="37.5%" headers="d0e43 ">The REXEC server command processing selection exit point
|
|
allows you to specify which command processor the REXEC server uses for interpreting
|
|
and running your commands. </td>
|
|
<td valign="top" width="37.05357142857143%" headers="d0e45 "><a href="rzal7rxcs0100.htm#rxcs0100">RXCS0100</a></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
|
<p><sup>1</sup>An exit point might 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, and then choose the one most appropriate for
|
|
your system. </p>
|
|
<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 REXEC 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>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzal7rxcs0100.htm">RXCS0100</a></strong><br />
|
|
The REXEC server command processing selection (RXCS0100) exit point allows you to specify which command processor the REXEC server uses for interpreting and running your commands.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzal7overview.htm" title="The Remote Execution (REXEC) server is a Transmission Control Protocol/Internet Protocol (TCP/IP) application that allows a client user to submit system commands to a remote server system. The Remote Execution Protocol (REXEC) allows processing of these commands or programs on any host in the network. The local host then receives the results of the command processing.">REXEC</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../rzaii/rzaiimst31.htm">Use server exit programs</a></div>
|
|
<div><a href="../rzaiq/rzaiqpsvrep.htm">VLRQ0100</a></div>
|
|
<div><a href="../rzaiq/rzaiql0100.htm">TCPL0100</a></div>
|
|
<div><a href="../rzaiq/rzaiql0300.htm">TCPL0300</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |