rrpc_inq_stats(3ncs) [ultrix man page]
rrpc_inq_stats(3ncs) rrpc_inq_stats(3ncs) Name rrpc_inq_stats - obtain statistics about a server Syntax #include <idl/c/rrpc.h> void rrpc_$inq_stats(handle, max_stats, stats, l_stat, status) handle_t handle; unsigned long max_stats; rrpc_$stat_vec_t stats; unsigned long *l_stat; status_$t *status; Arguments handle A remote procedure call (RPC) handle . max_stats The maximum number of elements in the array of statistics. stats An array of 32-bit integers representing statistics about the server. A set of rrpc_$sv constants defines indices for the ele- ments in this array. The following list describes the statistic indexed by each rrpc_$sv constant: rrpc_$sv_calls_in The number of calls processed by the server. rrpc_$sv_rcvd The number of packets received by the server. rrpc_$sv_sent The number of packets sent by the server. rrpc_$sv_calls_out The number of calls made by the server. rrpc_$sv_frag_resends The number of fragments sent by the server that duplicated previous sends. rrpc_$sv_dup_frags_rcvd The number of duplicate fragments received by the server. l_stat The index of the last element in the returned array. status The completion status. If the completion status returned in is equal to status_$ok , then the routine that supplied it was suc- cessful. Description The routine returns an array of integer statistics about a server. Restrictions On the client side, because of the way the calls are defined and implemented in the run-time library you must explicitly call into the entry point vector table for the interface to send an request across the network. The following is an example of a call that works as desired: (*rrpc_$client_epv.rrpc_$inq_stats)(handle, (unsigned long) max_stats, stats, &l_stat ,&status); The server sidestub routine calls the entry oint on behalf of the client. The results of the call are then passed back to the client. Files See Also intro(3ncs) rrpc_inq_stats(3ncs)
Check Out this Related 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)