man7/errcodes
Table of Contents
errcodes - AccelNET error codes
This manual page
lists error codes which are used by AccelNET. Not all situations use all
of the error codes.
I/O error - ie. socket no good, broken pipe or timeout on a socket.
all ok, there is no error
data outside valid range.
This error may be returned when a parameter value
is outside the PhyMin and PhyMax limits.
unimplemented DataType.
This error is returned when data conversion or update
is attempted on a parameter for which the data type is unimplemented.
Write lock present.
An update was attempted and denied on a parameter that
another job holds a write lock on.
no Write permission.
The job attempting the update did not have write permission.
bad pointers.
Usually this error is seen when an invalid parameter tagname
is used for an update.
general failure
A catchall for failures not covered by other error codes.
null working pointer
This error code is used internally in places where
it is desired to indicate that a working pointer is null. One could ask
why ERRbadp isn’t used instead. Generally the user will not see this error.
I/O error
An I/O subsystem can’t communicate with the hardware.
When a datapoint
is in this state it is displayed in purple by Xcrt.
Many times this error
is seen on ion source parameters because the isolation transformer is turned
off and the data acquistion system on the source deck is unpowered.
Errors in this group pertain to AccelNET
table management. Usually they are not directly seen by the user.
out of records or out of memory.
entry already in table.
list is empty.
invalid parent record (parent doesn’t exist).
record doesn’t exist.
invalid LABEL record.
invalid RefName record.
invalid DESC record.
invalid DATA record.
invalid PAGE record.
Error codes in this section are
used internally. Usually they are not seen by the user.
invalid Qown field in DATA record.
Error codes in this
section are sent in response to a write lock request. Most of the time they
are not directly seen by the user.
lock already present and owned by calling task.
lock already present and owned by another task.
The error codes are contained in ErrorCodes.h. Not all error codes
are used by all programs.
$Id: errcodes.7,v 1.0 2004/12/08
14:24:44 kitchen Exp $
Table of Contents
NARA 5SDH-2
