rpc_set_fault_mode(3ncs) [ultrix man page]

rpc_set_fault_mode(3ncs)												  rpc_set_fault_mode(3ncs)

Name
       rpc_set_fault_mode - set the fault-handling mode for a server (server only)

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

       unsigned long rpc_$set_fault_mode(state)
       unsigned long state;

Arguments
       state  If `true' (not zero), the server exits when a fault occurs.  If `false' (zero), the server reflects faults back to the client.

Description
       The function controls the handling of faults that occur in user server routines.

       In  the default mode, the server reflects faults back to the client and continues processing.  Calling with value other than zero for state
       sets the fault-handling mode so that the server sends an rpc_$comm_failure fault back to the client and exits.  Calling with state equal to
       zero resets the fault-handling mode to the default.

       This function returns the previous state of the fault-handling mode.

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

       rpc_$not_in_call    An internal error.

       rpc_$proto_error    An internal protocol error.

Files
See Also
       intro(3ncs)

															  rpc_set_fault_mode(3ncs)

rpc_inq_binding(3ncs)													     rpc_inq_binding(3ncs)

Name
       rpc_inq_binding - return the socket address represented by an RPC handle (client or server)

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

       void rpc_$inq_binding(handle, sockaddr, slength, status)
       handle_t handle;
       socket_$addr_t *sockaddr;
       unsigned long *slength;
       status_$t *status;

Arguments
       handle		   An RPC handle.

       sockaddr 	   The socket address represented by handle.

       slength		   The length, in bytes, of sockaddr.

       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 to determine the socket address, and therefore the server, identified by an RPC handle.  It is useful  when  a
       client uses an unbound handle in a remote procedure call and wishes to determine the particular server that responded to the call.

Examples
       The Location Broker administrative tool, uses the following statement to determine the GLB that last responded to a lookup request:
       rpc_$inq_binding(lb_$handle, &global_broker_addr,
			   &global_broker_addr_len, &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.

       rpc_$unbound_handle The handle is not bound and does not represent a particular host address.  Returned by

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

															     rpc_inq_binding(3ncs)