Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rpc_clear_server_binding(3ncs) [ultrix man page]

rpc_clear_server_binding(3ncs)											    rpc_clear_server_binding(3ncs)

Name
       rpc_clear_server_binding - unset the binding of an RPC handle to a server (client only)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$clear_server_binding(handle, status)
       handle_t handle;
       status_$t *status;

Arguments
       handle		   The RPC handle whose binding is being cleared.

       status		   The completion status.  If the completion status returned in is equal to status_$ok , then the routine that supplied it
			   was successful.

Description
       The routine removes the association between an RPC handle and a particular server (that is, a particular port number), but does not  remove
       the associations with an object and with a host (that is, a network address).  This call replaces a fully bound handle with a bound-to-host
       handle.	A bound-to-host handle identifies an object located on a particular host but does not identify a server exporting an interface	to
       the object.

       If  a  client  uses  a bound-to-host handle to make a remote procedure call, the call is sent to the Local Location Broker (LLB) forwarding
       port at the host identified by the handle.  If the call's interface and the object identified by the handle are both  registered  with  the
       host's  LLB, the LLB forwards the request to the registering server.  When the client RPC runtime library receives a response, it binds the
       handle to the server.  Subsequent remote procedure calls that use this handle are then sent directly to the bound server's port.

       The routine is useful for client error recovery when a server dies.  The port that a server uses when it restarts is  not  necessarily  the
       same port that it used previously; therefore, the binding that the client was using may not be correct.	This routine enables the client to
       unbind from the dead server while retaining the binding to the host.  When the client sends a request, the binding is automatically set	to
       the server's new port.

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$not_in_call    An internal error.

       rpc_$proto_error    An internal protocol error.

Files
See Also
       intro(3ncs), rpc_bind(3ncs), rpc_clear_binding(3ncs), rpc_set_binding(3ncs)

														    rpc_clear_server_binding(3ncs)

Check Out this Related Man Page

rpc_inq_object(3ncs)													      rpc_inq_object(3ncs)

Name
       rpc_inq_object - return the object UUID represented by an RPC handle (client or server)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$inq_object(handle, object, status)
       handle_t handle;
       uuid_$t *object;
       status_$t *status;

Arguments
       handle		   An RPC handle.

       object		   The UUID of the object identified by handle.

       status		   The completion status.  If the completion status returned in is equal to status_$ok , then the routine that supplied it
			   was successful.

Description
       The routine enables a client or server to determine the particular object that a handle represents.

       If a server exports an interface through which clients can access several objects, it can use to determine the object requested in a  call.
       This routine requires an RPC handle as input, so the server can make the call only if the interface uses explicit handles (that is, if each
       operation in the interface has a handle parameter).  If the interface uses an implicit handle, the handle identifier is not passed  to  the
       server.

Examples
       A  database server that manages multiple databases must determine the particular database to be accessed whenever it receives a remote pro-
       cedure call.  Each manager routine makes the following call; the routine then uses the  returned  UUID  to  identify  the  database  to	be
       accessed:
       rpc_$inq_object (handle, &db_uuid, &status);

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$unk_if	   The	requested interface is not known.  It is not registered in the server, the version number of the registered inter-
			   face is different from the version number specified in the request, or the UUID in the request does not match the  UUID
			   of the registered interface.

       rpc_$not_in_call    An internal error.

       rpc_$proto_error    An internal protocol error.

Files
See Also
       intro(3ncs)

															      rpc_inq_object(3ncs)
Man Page