rpc_dup_handle(3ncs) [ultrix man page]

rpc_dup_handle(3ncs)													      rpc_dup_handle(3ncs)

Name
       rpc_dup_handle - make a copy of an RPC handle (client only)

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

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

Arguments
       handle The RPC handle to be copied.

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

Description
       The routine returns a copy of an existing RPC handle.  Both handles can then be used in the client program for concurrent multiple accesses
       to  a binding.  Because all duplicates of a handle reference the same data, an or routine made on any one duplicate affects all duplicates.
       However, an RPC handle is not freed until is called on all copies of the handle.

Files
See Also
       intro(3ncs), rpc_alloc_handle(3ncs), rpc_free_handle(3ncs)

															      rpc_dup_handle(3ncs)

rpc_clear_binding(3ncs) 												   rpc_clear_binding(3ncs)

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

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

       void rpc_$clear_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 success-
	      ful.

Description
       The routine removes any association between an RPC handle and a particular server and host, but it does not remove the association  between
       the  handle and an object.  This routine saves the RPC handle so that it can be reused to access the same object, either by broadcasting or
       after resetting the binding to another server.

       A remote procedure call made using an unbound handle is broadcast to all Local Location Brokers (LLBs) on the local network.  If the call's
       interface  and  the  object  identified	by  the  handle are both registered with any LLB, that LLB forwards the request to the registering
       server.	The client RPC runtime library returns the first response that it  receives  and  binds  the  handle  to  the  first  server  that
       responded.

       The routine is the inverse of the routine.

Examples
       Clear the binding represented in handle:
       rpc_$clear_binding (handle, &status);

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_server_binding(3ncs), rpc_set_binding(3ncs)

															   rpc_clear_binding(3ncs)