rpc_register(3ncs) [ultrix man page]
rpc_register(3ncs) rpc_register(3ncs) Name rpc_register - register an interface (server only) Syntax #include <idl/c/rpc.h> void rpc_$register(ifspec, epv, status) rpc_$if_spec_t *ifspec; rpc_$epv_t epv; status_$t *status; Arguments ifspec The interface being registered. epv The entry point vector (EPV) for the operations in the interface. The EPV is always defined in the server stub that is generated by the NIDL compiler from an interface definition. 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 registers an interface with the RPC runtime library. After an interface is registered, the RPC runtime library will pass requests for that interface to the server. You can call several times with the same interface (for example, from various subroutines of the same server), but each call must specify the same EPV. Each registration increments a reference count for the registered interface; an equal number of routines are then required to unregister the interface. Examples The following statement registers the bank interface with the bank server host's RPC runtime library: rpc_$register (&bank_$if_spec, bank_$server_epv, &status); Diagnostics This section lists status codes for errors returned by this routine in rpc_$op_rng_error The requested operation does not correspond to a valid operation in the requested interface. rpc_$too_many_ifs The maximum number of interfaces is already registered with the RPC runtime library; the server must unregister some interface before it registers an additional interface. rpc_$not_in_call An internal error. rpc_$you_crashed This error can occur if a server has crashed and restarted. A client RPC runtime library sends the error to the server if the client makes a remote procedure call before the server crashes, then receives a response after the server restarts. rpc_$proto_error An internal protocol error. rpc_$illegal_register You are trying to register an interface that is already registered and you are using an EPV different from the one used when the interface was first registered. An interface can be multiply registered, but you must use the same EPV in each routine. rpc_$bad_pkt The server or client has received an ill-formed packet. Files See Also intro(3ncs), rpc_register_mgr(3ncs), rpc_register_object(3ncs), rpc_unregister(3ncs) rpc_register(3ncs)
Check Out this Related Man Page
rpc_use_family_wk(3ncs) rpc_use_family_wk(3ncs) Name rpc_use_family_wk - create a socket with a well-known port for a remote procedure call (RPC) server (server only) Syntax #include <idl/c/rpc.h> void rpc_$use_family_wk(family, ifspec, sockaddr, slength, status) unsigned long family; rpc_$if_spec_t *ifspec; socket_$addr_t *sockaddr; unsigned long *slength; status_$t *status; Arguments family The address family of the socket to be created. This value corresponds to the communications protocol used to access the socket and determines how the sockaddr is expressed. The value must be one of socket_$unspec or socket_$internet. ifspec The interface that will be registered by the server. Typically, this parameter is the interface if_spec generated by the NIDL compiler from the interface definition; the well-known port is specified as an interface attribute. sockaddr The socket address of the socket on which the server will listen. 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 creates a socket that uses the port specified through the if_spec parameter. Use this routine to create a socket only if a server must listen on a particular well-known port. Otherwise, use A server listens on one socket per address family, regardless of how many interfaces that it exports. Therefore, servers that use well- known ports should make this call once per supported address family. Examples The following statement creates the well-known socket identified by for an array processor server: rpc_$use_family_wk (socket_$internet, &matrix$if_spec, &sockaddr, &slen, &status); Diagnostics This section lists status codes for errors returned by this routine in rpc_$cant_create_sock The RPC runtime library was unable to create a socket. rpc_$not_in_call An internal error. rpc_$proto_error An internal protocol error. rpc_$too_many_sockets The server is trying to use more than the maximum number of sockets that is allowed; it has called or too many times. rpc_$bad_pkt The server or client has received an ill-formed packet. rpc_$addr_in_use The address and port specified in an routine are already in use. This is caused by multiple calls to with the same well-known port. Files See Also intro(3ncs), rpc_use_family(3ncs) rpc_use_family_wk(3ncs)