ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/rpc1.htm

99 lines
3.8 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>Remote Procedure Call (RPC) APIs</title>
<!-- Begin Header Records ========================================= -->
<!-- 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. -->
<!-- NETMG2 SCRIPT A converted by B2H R4.1 (346) (CMS) by HOLTJM at -->
<!-- RCHVMW2 on 29 Jan 1999 at 10:01:37 -->
<!-- File restructured for V5R2 -->
<!-- End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<a name="Top_Of_Page"></a>
<!-- Java sync-link -->
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript">
</script>
<h2>Remote Procedure Call (RPC) APIs</h2>
<p>The Remote Procedure Call (RPC) APIs include:</p>
<ul>
<li><a href="rpc2.htm">Authentication APIs</a></li>
<li><a href="rpc3.htm">Name-to-Address Translation APIs</a></li>
<li><a href="rpc4.htm">Network Selection APIs</a></li>
<li><a href="rpc5.htm">Transport-Independent Remote Procedure Call (TI-RPC)
APIs</a></li>
<li><a href="rpc6.htm">External Data Representation (XDR) APIs</a></li>
</ul>
<p>These APIs are intended for programmers who develop distributed
applications. They enable distributed applications to communicate with each
other. Open Networking Computers (ONC) RPC was developed by Sun Microsystems
and is used to easily separate and distribute a client application from a
server by using the SUN RPC protocol. RPC includes a method of abstracting
data, called eXternal Data Representation, or XDR, to allow communications to
be abstracted at the API level.</p>
<p>Transport-Independent RPC (TI-RPC), or ONC+ RPC, is the latest incantation
of RPC. It provides a method of abstracting the underlying protocol used at the
network layer, providing a more seamless transition from one protocol to
another.</p>
<p><strong>Note:</strong> These functions use header (include) files from the
library QSYSINC, which is optionally installable. Make sure QSYSINC is
installed on your system before using any of the functions. See
<a href="rpc7.htm">Header Files for Remote Procedure Call APIs</a> for the
file and member name of each header file.</p>
<p>The following terms relate to the RPC applications:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><strong>RPCBind</strong></td>
<td align="left" valign="top">A daemon program that allows client programs to
obtain the aress of a service that is registered with the RPCBind daemon.</td>
</tr>
<tr>
<td align="left" valign="top"><strong>RPCGen</strong></td>
<td align="left" valign="top">A compiler that accepts a remote-program
interface definition written in the RPC language (RPCL), which is similar to
the C programming language. From this definition, RPCGen produces C-language
output for client stub functions, a server skeleton, XDR filter routines, and a
header file.</td>
</tr>
</table>
<p>For more information on RPCBind and RPCGen, see the
<a href="../rbam6/rbam6clmain.htm">Control Language</a> topic.</p>
<p>For more information about these APIs, see
<a href="../rzahp/rzahprpcover.htm">Sun TI-RPC distributed applications</a>
in the Information Center.</p>
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center">
<a href="#Top_Of_Page">Top</a> |
<a href="aplist.htm">APIs by category</a></td>
</tr>
</table>
</center>
</body>
</html>