75 lines
4.8 KiB
HTML
75 lines
4.8 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 programs" />
|
|
<meta name="abstract" content="Exit programs are called and given control by an application program or system program. They can be used to customize particular functions to your needs. An exit program is a program to which control is passed from a calling program." />
|
|
<meta name="description" content="Exit programs are called and given control by an application program or system program. They can be used to customize particular functions to your needs. An exit program is a program to which control is passed from a calling program." />
|
|
<meta name="DC.Relation" scheme="URI" content="concept.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/wrkreginf.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="conExitProg" />
|
|
<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 programs</title>
|
|
</head>
|
|
<body id="conExitProg"><a name="conExitProg"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Exit programs</h1>
|
|
<div><p>Exit programs are called and given control by an application program
|
|
or system program. They can be used to customize particular functions to your
|
|
needs. An <em>exit program</em> is a program to which control is passed from
|
|
a calling program.</p>
|
|
<p>Exit programs are usually user-written programs; however, a few are system-supplied
|
|
(such as a few of the Operational Assistant exit programs).</p>
|
|
<p>To transfer control to an exit program, you do an external call as you
|
|
would to any other program.</p>
|
|
<p>There are no general requirements for using exit programs. For any specific
|
|
requirements, see the documentation for the specific exit program.</p>
|
|
<div class="section"><h4 class="sectiontitle">Exit points</h4><p>An <em>exit point</em> signifies the point
|
|
in a system function or program where control is turned over to one or more
|
|
exit programs to perform a function.</p>
|
|
<p>Prior to Version 3 Release 1, the
|
|
exit program might have been represented as network attributes, system values,
|
|
CL command parameters, or attributes of system objects. Also, in previous
|
|
releases, all exit point providers had to supply their own means of registering
|
|
and deregistering exit programs.</p>
|
|
<p>The <em>registration facility</em> provides
|
|
a central point to store and retrieve information about <span class="keyword">i5/OS™</span> and
|
|
non-<span class="keyword">i5/OS</span> exit
|
|
points and their associated exit programs. This information is stored in the
|
|
registration facility repository and can be retrieved to determine which exit
|
|
points and exit programs already exist.</p>
|
|
<p>You can use the registration
|
|
facility APIs to register and deregister exit points, to add and remove exit
|
|
programs, and to retrieve information about exit points and exit programs.
|
|
You can also perform some of these functions by using the Work with Registration
|
|
Information (WRKREGINF) command.</p>
|
|
<p>The <em>exit point provider</em> is responsible
|
|
for defining the exit point information, defining the format in which the
|
|
exit program receives data, and calling the exit program.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="concept.htm" title="Describes the underlying concepts that you need to understand to work effectively with APIs. Among the concepts covered are basic concepts, programming considerations, and terminology.">API concepts</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="../cl/wrkreginf.htm">Work with Registration Information (WRKREGINF)</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |