Specifications

Interfaces Page 33
Output-buffer
- the looped back data received, whether correct or
not. Present
only if the buffer was furnished
on the Loop call.
Function:
Used to abort a Loop-direct or Loop-assisted, for example if the
user decides that the reply has taken too long.
Inputs:
Receipt-number
- the request identification assigned to this
request by the Loop-direct or Loop-assisted function.
Outputs: none.
3.2.3 Remote Console Functions
There is an aspect of the Console Server operational model that
affects the user interface in a way that must be explained here. This
is the relationship between data access functions and control
functions.
. Data access -- these functions involve parameters (for example
Read-identity). The model assumes that the Console Server has
necessary access abilities without higher level involvement.
. Control -- these functions involve changing the flow of
execution of a processor (for example, Boot). The model
assumes that the Console Server cannot do this directly. The
higher level must therefore poll the Console Server for this
type of request and the information needed to honor
it.
Most of the remote console functions are calls to the Console
Requester. Console Requester operations are of two types, those that
require exclusive access to the remote console and those that do not.
Unless otherwise noted, the following functions are calls to the
Console Requester.
Function:
Checks to see
if
certain remote requests have been made. These
are requests
that directly modify local system processor