Users of ESRO services (invoker and performer) need to agree on a well defined set of parameters which are enumerated below.
The invoker and the performer can specify these parameters using a variety of mechanisms. The notation specified in this section is one such mechanism. It is not the only machanism and ESRO protocol can be used independent of this notation.
The Remote Operations and Operation Errors are specified in this section. The notation is defined by means of the macro facility defined in [3].
The macros enabling the specification of operations and errors are listed in Figure 7.
Note that this notation is very similar to the abstract operation defined in [1]. The value form of ES-OPERATION is always an integer.
An operation is mapped onto the ESRO Services.
The invocation of an operation is mapped on the ESRO-INVOKE service.
The value assigned to the operation is mapped on the Operation-value parameter of that service. The value of the Named-Type in the ARGUMENT clause of the OPERATION Macro is mapped on the Argument parameter of that service.
If an operation was successfully performed, the reply is mapped on the ESRO-RESULT service.
The value of the Named-Type in the RESULT clause of the OPERATION macro is mapped on the Result parameter of that service.
If an operation was not successfully performed, the reply is mapped on the ESRO-ERROR service.
In this case one of the errors in the Identifier List of Error Names in the ERROR clause of the OPERATION macro may be applied. The value assigned to the applied error is mapped onto the Error parameter of that service. The value of the Named-Type in the PARAMETER clause of the ERROR macro of the applied error is mapped on the Error- parameter of that service.
