rpc_listen(3ncs) [ultrix man page]

rpc_listen(3ncs)														  rpc_listen(3ncs)

Name
       rpc_listen - listen for and handle remote procedure call (RPC) packets (server only)

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

       void rpc_$listen(max_calls, status)
       unsigned long max_calls;
       status_$t *status;

Arguments
       max_calls      This  value  indicates  the  maximum number of calls that the server is allowed to process concurrently.	On ULTRIX systems,
		      this value should be 1; any other value is ignored and defaulted to one.

       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  dispatches  incoming  remote procedure call requests to manager procedures and returns the responses to the client.  You must
       issue or before you use This routine normally does not return.  A return from this routine indicates either an irrecoverable error, or that
       an call has been issued.  If is equal to status_$ok , the assumption is that has occurred.

Examples
       Listen for incoming remote procedure call requests.
       rpc_$listen (1, &status);

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

       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_$bad_pkt	   The server or client has received an ill-formed packet.

Files
See Also
       intro(3ncs), rpc_shutdown(3ncs)

																  rpc_listen(3ncs)

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)