| ## dce_server_use_protseq(3dce) Tells DCE to use the specified protocol sequence for receiving remote procedure calls Used by server applications. Synopsis #include <dce/dced.h> void dce_server_use_protseq( dce_server_handle_t server_handle, unsigned char *protseq, error_status_t *status); Parameters Input server_handle An opaque handle. Use the value of NULL. protseq Specifies a string identifier for the protocol sequence to register with the RPC runtime. (For a list of string identifiers, see the table of valid protocol sequences in the intro(3rpc) reference page.) Output status Returns the status code from this routine. This status code indicates whether the routine completed successfully. The only status code is error_status_ok. Description The dce_server_use_protseq( ) routine registers an individual protocol sequence with DCE. Typical servers use all valid protocol sequences, the default behavior for the dce_server_register( ) call, and so most servers do not need to call this dce_server_use_protseq( ) routine. However, this routine may be called prior to dce_server_register( ), to restrict the protocol sequences used. 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. Errors The following describes a partial list of errors that might be returned. Refer to the OSF DCE Problem Determination Guide for complete descriptions of all error messages. Related Information Routines: rpc_intro(3rpc) dce_server_register(3dce) rpc_server_use_protseq(3rpc) Book: OSF DCE Application Development Guide - Core Components ##