58 lines
3.8 KiB
HTML
58 lines
3.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="task" />
|
||
|
|
<meta name="DC.Title" content="Use the rpcbind daemon" />
|
||
|
|
<meta name="abstract" content="When a client wants to connect to a remote procedure call (RPC) service, it contacts the RPCBIND daemon and requests the address of the service. In this way, addresses can be dynamic and the client does not need to know which port the service is waiting on." />
|
||
|
|
<meta name="description" content="When a client wants to connect to a remote procedure call (RPC) service, it contacts the RPCBIND daemon and requests the address of the service. In this way, addresses can be dynamic and the client does not need to know which port the service is waiting on." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahprpcover.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahpensbind.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahpstartbind.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="rzahpusebind" />
|
||
|
|
<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>Use the rpcbind daemon</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahpusebind"><a name="rzahpusebind"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use the rpcbind daemon</h1>
|
||
|
|
<div><p>When a client wants to connect to a remote procedure call (RPC)
|
||
|
|
service, it contacts the RPCBIND daemon and requests the address of the service.
|
||
|
|
In this way, addresses can be dynamic and the client does not
|
||
|
|
need to know which port the service is waiting on.</p>
|
||
|
|
<div class="section"> <p>Services need to be registered with the rpcbind daemon in order
|
||
|
|
to be useful. If the rpcbind daemon is inactive, the services are unable to
|
||
|
|
start, and the clients are not able to find any of the services.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahpensbind.htm">Ensure that the rpcbind daemon is running on i5/OS</a></strong><br />
|
||
|
|
To use the transport independent remote procedure call (TI-RPC)
|
||
|
|
application programming interfaces (APIs), you need to ensure that the rpcbind
|
||
|
|
daemon job (QNFSRPCD) is running on i5/OS™.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahpstartbind.htm">Start and end the rpcbind daemon on i5/OS</a></strong><br />
|
||
|
|
Start the rpcbind daemon on i5/OS™ if it is not already running. The
|
||
|
|
rpcbind daemon (RPCBIND) command starts the rpcbind daemon job (QNFSRPCD).</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahprpcover.htm" title="Remote procedure call (RPC) provides a high-level paradigm, which allows distributed applications to communicate with one another.">Using Sun TI-RPC to develop distributed applications</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|