OSF DCE Application Development Guide--Core Components

Developing a Simple RPC Application
The server program can be terminated at any time by a signal, which on many systems
can be generated by <Ctrl-c>.
When applications such as greet execute, many errors can occur that have nothing to do
with your own code. In general, errors that occur when a remote procedure call executes
are reported as exceptions. For example, exceptions that the client side of greet_client
could raise if the server suddenly and unexpectedly halts include (but are not limited to)
rpc_x_comm_failure and rpc_x_call_timeout. Other ways to respond to these errors
are available through the comm_status and fault_status attributes in an interface
definition or attribute configuration file. Explanations of these attributes appear in
Chapter 18. Also, see Chapter 16, which explains the guidelines for error handling.
In addition, Part 2 of this guide contains information about the macros (such as those
specified by TRY, CATCH, and ENDTRY statements) for exception handling. If an
exception occurs that the client application does not handle, it causes the client to
terminate with an error message. The client’s termination could include a core dump or
other system-dependent error-reporting method. Detailed explanations of RPC status
codes and RPC exceptions are in the
124245 Tandem Computers Incorporated 11− 25