NAME

rpc_server_use_protseq_ep - Tells the RPC runtime to use the specified protocol sequence combined with the specified endpoint for receiving remote procedure calls

Used by server applications. 

SYNOPSIS

#include <dce/rpc.h>
void rpc_server_use_protseq_ep(

unsigned_char_t ∗protseq ,
unsigned32 max_call_requests ,
unsigned_char_t ∗endpoint ,
unsigned32 ∗status );

PARAMETERS

Input

protseqSpecifies a string identifier for the protocol sequence to register with the RPC runtime. See the table of valid protocol sequences in the rpc_intro(3) reference page for a list of string identifiers.  The location of the table is in the description of a protocol sequence. 

max_call_requestsSpecifies the maximum number of concurrent remote procedure call requests that the server can accept.  The RPC runtime guarantees that the server can accept at least this number of concurrent call requests.  The actual number of these requests can be greater than the value of max_call_requests and can vary for each protocol sequence.  Use the value rpc_c_protseq_max_reqs_default to specify the default argument value.  Also, routine rpc_server_listen limits (according to its max_calls_exec argument) the amount of concurrent remote procedure call execution.  See the description section of reference page rpc_server_listen(3) for more information. 

endpointSpecifies address information for an endpoint. This information is used in creating a binding handle for the protocol sequence specified in the protseq argument. 

Output

statusReturns the status code from this routine.  This status code indicates whether the routine completed successfully or, if not, why not.  The possible status codes and their meanings are as follows:

rpc_s_okSuccess. 

rpc_s_calls_too_large_for_wk_ep
Maximum concurrent calls too large.

rpc_s_cant_bind_socketCannot bind to socket. 

rpc_s_cant_create_socketCannot create socket. 

rpc_s_invalid_endpoint_format
Invalid endpoint format.

rpc_s_invalid_rpc_protseqInvalid protocol sequence. 

rpc_s_max_descs_exceededExceeded maximum number of network descriptors. 

rpc_s_protseq_not_supported
Protocol sequence not supported on this host.

DESCRIPTION

The rpc_server_use_protseq_ep routine registers a protocol sequence and its specified endpoint address information with the RPC runtime. A server must register at least one protocol sequence with the RPC runtime to receive remote procedure call requests.  A server can call this routine multiple times to register additional protocol sequences and endpoints. 

For each protocol sequence registered by a server, the RPC runtime creates one or more binding handles.  Each binding handle contains the well-known endpoint specified in argument endpoint. 

The max_call_requests argument allows you to specify the maximum number of concurrent remote procedure call requests the server handles. 

The explanation of the rpc_server_use_all_protseqs routine contains a list of the routines a server typically calls after calling this routine.  For an explanation of how a server can establish a client-server relationship without using the local endpoint map or the name service database, see the explanation of a string binding in the rpc_intro(3) reference page. 

RETURN VALUES

None. 

RELATED INFORMATION

Functions: rpc_binding_vector_free(3), rpc_ep_register(3), rpc_ep_register_no_replace(3), rpc_ns_binding_export(3), rpc_server_inq_bindings(3), rpc_server_listen(3), rpc_server_register_if(3), rpc_server_use_all_protseqs(3), rpc_server_use_all_protseqs_if(3), rpc_server_use_protseq(3), rpc_server_use_protseq_ep(3)