The specific errors detected by the graPHIGS API subroutines are listed
with the appropriate subroutine syntax.
Device driver warning and errors.
The timing of notification of the error is controlled by several
factors, such as deferral mode or availability of system resources.
Although errors are listed with each subroutine,
the error may actually be reported by the
processing of another subroutine.
For example:
Errors detected within the nucleus may be reported
to the application on later, unrelated subroutines.
Errors in view specifications
(such as error
522 when a view
matrix specified on the Set View Mapping 3
[GPVMP3]
[page
GPVMP3 - Set View Mapping 3]
subroutine
is singular) may not be detected and
reported to the application until the incorrect data is used by
the Update Workstation
(GPUPWS)
[page
GPUPWS - Update Workstation]
subroutine.
I/O errors may be reported on subroutines that do not appear
to perform I/O, or may perform
I/O that is unrelated to the reported I/O error.
Since deferral mode affects the timing of workstation updates,
error conditions in some subroutines may not be detected until later
subroutines force an update.
This can cause errors from the former subroutines
to be reported to the application on the later, unrelated subroutines.
In addition, there are certain errors that, although possible
on any graPHIGS API subroutine, are not listed with each subroutine.
These errors are:
- 2
- FUNCTION REQUIRES STATE PHOP
- 300
- STORAGE REQUEST FAILED
- 520
- ERROR QUEUE HAS OVERFLOWED
- 525
- FUNCTION CANNOT BE CALLED IN ERROR STATE
- 556
- ELEMENT EXCEEDS MAXIMUM ALLOWED SIZE
- 594
- DATA EXCEEDS CONNECTION BUFFER SIZE
- 603
- INTERNAL COMMUNICATIONS PROTOCOL ERROR
- 607
- NUCLEUS IS DOWN LEVEL. VERSION @A1, RELEASE @A2.@A3 IS REQUIRED
For a complete description of these error messages,
see The graPHIGS Programming Interface: Messages and Codes
In addition, messages from the workstation service routines
(Messages 2000-2999) and/or
system services (Messages 1000-1299) are possible on
many subroutines.
For additional information on errors and error processing states,
see The graPHIGS Programming Interface: Messages and Codes
and The graPHIGS Programming Interface: Understanding Concepts