Next: ERR_CLEAR - Return the error table to the default context and flush its contents
Up: Using EMS within ADAM system software
Previous: Synchronising message output
Routines specific
to the ADAM fixed part
There are three ERR routines which start up, clear and stop the Error Reporting
System within the ADAM fixed part to ensure that the delivery of any
reported error messages is deferred and that any messages pending output are
delivered to the user when the application has finished.
These subroutines are ERR_START, ERR_CLEAR and
ERR_STOP - they are
discussed in this document because they are purely for system programming and
will affect the use of EMS as well as ERR within ADAM.
ERR_START has the effect of marking a new EMS context and thus
deferring the delivery of any reported error messages to the user.
The new context is known as the default context.
ERR_CLEAR has the effect of returning the current error context to
the `default' level set by ERR_START and flushing any reported error
messages to the user.
Thus, the effect of any mismatched `mark' and `release' calls within an
application is annulled.
ERR_STOP clears the error message table by calling
ERR_CLEAR and then returns
the error reporting context to the initial context level, i.e. the
level prior to the call to ERR_START.
The use of these three routines is entirely reserved for starting up,
clearing and
stopping error reporting within the environment, e.g. the ADAM fixed
part, and must not be used for any other purpose.
These routines exist only in the ADAM version of the ERR library and are linked
using the procedure given in
SUN/104.
Next: ERR_CLEAR - Return the error table to the default context and flush its contents
Up: Using EMS within ADAM system software
Previous: Synchronising message output
EMS Error Message Service
Starlink System Note 4
P C T Rees
A J Chipperfield
28 September 2001
E-mail:ussc@star.rl.ac.uk
Copyright © 2001 Council for the Central Laboratory of the Research
Councils