| 2001 CHARACTER SET HAS UNSUPPORTED CHARACTER CODES WHICH ARE IGNORED |
Explanation: The requested character set specifies character codes that are not in the range X'40' to X'FE' for EBCDIC characters, or in the range X'20' to X'FF' for ASCII characters.
System Action: All characters within this range are used. Any characters outside this range are ignored.
Programmer Response: None. The system will use only the supported characters.
Error Number: 900
| 2002 NUMBER OF STRUCTURE ELEMENTS EXCEEDS 5080 CAPACITY |
Explanation: An update to a structure cannot be displayed by the 5080 because the total number ofd structure elements exceeds the 5080 limit.
System Action: The display does not change.
Programmer Response: Edit the structure and delete elements until the structure element count is within the 5080 capability.
Error Number: 930
| 2003 THE REQUESTED CHARACTER SET IS INVALID FOR THE 5080 |
Explanation: A request was made to activate a character set which is not in the list of valid character sets for the 5080. At Open Workstation time, the graPHIGS API constructs a list of the valid Character Set/Font Identifiers from the known graPHIGS API-defined character sets and those listed in the FONTLIST PROCOPT for this 5080 Workstation.
System Action: The character set is not activated.
Programmer Response: Check that the desired character set is being activated. If it is not a graPHIGS API-defined character set, be sure that the character set is specified in the FONTLIST for this workstation. See The graPHIGS Programming Interface: Technical Reference for a list of valid character sets.
Error Number: 920
| 2004 5085 STORAGE NOT AVAILABLE FOR THE REQUESTED CHARACTER SET |
Explanation: This message is caused by either of the following conditions:
Note: A ward is a section of a double-byte character set where the first byte of all the codes belonging to it are the same. See the glossary in The graPHIGS Programming Interface: Understanding Concepts for a more detailed explanation.
Both of these conditions indicate a problem with specifying user-defined character sets for the 5080. User-defined character sets for the 5080 must be specified via the FONTLIST PROCOPT in order for the graPHIGS API to accuratel predict how much storage to allocate for character sets. The PROCOPT FONTPSIZ specifies the total number of simultaneously active character sets.
System Action: The character set is not activated.
Programmer Response: Check that the PROCOPT FONTLIST specifies the desired user-defined character sets for the 5080, and that the PROCOPT FONTPSIZ specifies a large enough Font Pool Size for the needed number of simultaneously active Character Sets. See The graPHIGS Programming Interface: Technical Reference for more details on user defined character sets. Also, see IBM 5080 Graphics System: Principles of Operation for information on how the 5080 handles character sets.
Error Number: 920
| 2005 A REQUESTED CHARACTER SET SIZE EXCEEDS THE 5080 MAXIMUM |
Explanation: At Open Workstation time, the graPHIGS API found that a character set listed in the PROCOPT FONTLIST fits one of the following conditions:
Note: A ward is a section of a double-byte character set where the first byte of all the codes belonging to it are the same. See the glossary in The graPHIGS Programming Interface: Understanding Concepts for a more detailed explanation.
All sizes are the sizes of the character sets after conversion to the 5080 Programmable Character Set (PCS) format. These restrictions are imposed by the 5080. No PCS is allowed to exceed one 5080 page (65536 bytes), and the maximum number of PCSs allowed in the 5080 is 48.
System Action: The size of the character set in error is not used in allocating storage for the PCSs in the 5080, although the character set and font identifier are still listed as valid. Thus, activation of the character set will cause further errors.
Programmer Response: Either the user-defined character set in error cannot be used for the 5080, or it must be re-defined to fit the limitations of the 5080. See The graPHIGS Programming Interface: Technical Reference for more details on user-defined character sets. Also, see IBM 5080 Graphics System: Principles of Operation for information on how the 5080 handles character sets.
Error Number: 910
| 2006 THE 5080 CHARACTER SET TABLE SIZE HAS BEEN EXCEEDED |
Explanation: An error occurred in writing a character set to the 5080 that indicates that the maximum number of 5080 Programmable Character Sets (PCS) has been exceeded. The maximum number is 48. One PCS is used for each single-byte character set and each ward of a double-byte character set.
Note: A ward is a section of a double-byte character set where the first byte of all the codes belonging to it are the same. See the glossary in The graPHIGS Programming Interface: Understanding Concepts for a more detailed explanation.
System Action: The character set is not activated.
Programmer Response: If you need to activate additional character sets, close this workstation and re-open it. See The graPHIGS Programming Interface: Technical Reference for more details on how the graPHIGS API handles character sets. Also, see IBM 5080 Graphics System: Principles of Operation, for information on how the 5080 handles character sets.
Error Number: 920
| 2007 THE PRIMARY CHARACTER SET FILE COULD NOT BE FOUND |
Explanation: While attempting to activate the primary character set, the file for that character set could not be loaded.
System Action: The workstation is not opened.
Programmer Response: Be sure that you have access to the character set/font definition files. See The graPHIGS Programming Interface: Writing Applications for information on how to access these files, or contact your system programmer.
Error Number: 940
| 2008 AN ELEMENT EXCEEDS THE MAXIMUM ELEMENT SIZE |
Explanation: When a structure element was processed, it exceeded the maximum size for a single element.
System Action: The element is truncated and processing continues.
Programmer Response: Locate the element and redefine it as more than one element of a smaller size.
Error Number: 910
| 2009 INSUFFICIENT CONTIGUOUS DLB STORAGE, ELEMENT TRUNCATED |
Explanation: Inadequate contiguous DLB storage was encountered during connection of a structure to a workstation. This indicates that DLB storage is exhausted or fragmented.
System Action: The element is truncated and processing continues.
Programmer Response: Delete any unnecessary elements, or disassociate any unnecessary structures. Use GPQWSU to determine current storage utilization. Try to disassociate and reassociate structures to clean up and reduce fragmentation.
Error Number: 910
| 2010 AN INITIAL STROKE OR LOCATOR POINT IS OUTSIDE OF THE VIEW |
Explanation: One of the initial points was found outside the initial view.
System Action: The number of initial points is set to zero for a stroke device, and the center of a workstation window is used for a locator device.
Programmer Response: Examine the initial values for the stroke and locator devices. Adjust the values for the initial points so that they lie within the clip boundaries of the initial view.
Error Number: 910
| 2011 THE 4TH COLUMN OF THE MATRIX IS ASSUMED TO BE (0,0,0,1) |
Explanation: A viewing or modeling transformation matrix was found in which the fourth column was not (0,0,0,1). The workstation requires that these values be in the fourth column.
System Action: (0,0,0,1) is used as the fourth column.
Programmer Response: Check the error log to determine the error causing function. To avoid this message, change the fourth column of the matrix.
Error Number: 910
| 2012 PRP IS BETWEEN NEAR/FAR CLIP PLANES, VIEW = a1 DEFAULTS TO PARALLEL |
Explanation: The Projection Reference Point (PRP) is between the near and far clip planes. Under this condition, it is impossible for the workstation to project a perspective view.
System Action: The projection type defaults to parallel.
Programmer Response: Move the projection reference point outside both clip planes.
Error Number: 910
| 2013 THE 5080 IS MISSING THE TRANSFORMATION AND CLIPPING FEATURE |
Explanation: The configuration data returned indicates that the 5080 does not have the required transformation and clipping feature.
System Action: The workstation is not opened.
Programmer Response: Be sure that the feature is installed on your device. Contact a service representative.
Error Number: 940
| 2014 THE 5080 CONTAINS A DISKETTE WITH UNSUPPORTED MICROCODE |
Explanation: The configuration data returned indicates that the 5080 does not have the required microcode level.
System Action: The workstation is not opened.
Programmer Response: Go into Setup mode and check the microcode level number. See The GDDM/graPHIGS Programming Interface: Installation and Problem Diagnosis or The AIX PS/2 Personal graPHIGS Programming Interface: Installation and Problem Diagnosis for the minimum level of microcode required. If the microcode level is less than the required minimum, obtain a diskette with a correct microcode level and do an initial program load in the device again. Then, rerun the application. You should obtain and use the latest level of microcode for your 5080 workstation. This will ensure that you have fixes for microcode problems and possible performance enhancements. Ask the person responsible for installing the graPHIGS API on your system to see the Program Directory supplied with the latest release for information about the latest microcode level.
Error Number: 940
| 2015 THE ATTACHED DEVICE IS NOT A 5085 |
Explanation: The configuration data returned indicates that the attached unit is not a 5085 graphics processor.
System Action: The workstation is not opened.
Programmer Response: Be sure you are connected to a working 5085. Contact your system programmer.
Error Number: 940
| 2016 THE 5085 IS NOT CONNECTED TO A 5088 |
Explanation: The configuration data returned indicates that the control unit is not a 5088 channel control unit.
System Action: The workstation is not opened.
Programmer Response: Be sure your 5085 is connected to a working 5088 control unit. Contact your system support.
Error Number: 940
| 2017 THE 5085 IS NOT DEFINED AS A HIGH FUNCTION GRAPHICS DEVICE |
Explanation: The configuration data returned indicates that the attached 5085 is not defined to the system as a high function graphics device (HFGD).
System Action: The workstation is not opened.
Programmer Response: Be sure you are connected to a working 5085 device. Contact your system programmer.
Error Number: 940
| 2018 THE 5085 DOES NOT HAVE A PICK DEVICE ATTACHED |
Explanation: The configuration data returned indicates that the 5085 does not have a pick device attached.
System Action: The workstation is not opened.
Programmer Response: Be sure a tablet is attached to the 5085.
Error Number: 940
| 2019 THE 5085 DOES NOT HAVE A KEYBOARD ATTACHED |
Explanation: The configuration data returned indicates that the 5085 does not have a keyboard attached.
System Action: The workstation is not opened.
Programmer Response: Be sure a keyboard is attached to the 5085.
Error Number: 940
| 2020 The 5085 DOES NOT HAVE A TABLET ATTACHED |
Explanation: The configuration data returned indicates that the 5085 does not have a tablet attached.
System Action: The workstation is not opened.
Programmer Response: Be sure a tablet is attached to the 5085.
Error Number: 940
| 2022 THE 5085 DOES NOT HAVE THE REQUIRED MEMORY EXPANSION |
Explanation: The configuration data returned indicates that the 5085 does not have the required memory increment.
System Action: The workstation is not opened.
Programmer Response: Be sure that at least one memory expansion is installed in your 5085. Contact a service representative.
Error Number: 940
| 2023 THE 5080 CONTAINS AN UNSUPPORTED EPROM LEVEL |
Explanation: The configuration data returned indicates that the 5080 does not have the required EPROM level. On open, this will be detected if the structured field buffer in the 5080 is less than 6,144 bytes, since the EPROM level is too low to redefine it.
System Action: The workstation is not opened.
Programmer Response: Contact your system programmer to either restore the original (6K) structured field buffer, or, if the serial number of the 5085 is below 12,000, install the 5085 Specify Feature #9401 (MSA). This will allow applications to define their own structured field buffer.
Error Number: 940
| 2024 GSEVWT RETURNED ERROR CODE = xxxx |
Explanation: An attempt to parse the AIX ring buffer failed.
System Action: None.
Programmer Response: This failure is usually caused by the SIGMSG signal running at a high rate. Devices such as valuators and tablets generate large numbers of SIGMSG signals. Unless this occurs frequently or is linked to some application failure, it can be ignored. A discussion of signals, including SIGMSG, can be found in the AIX Operating System: Technical Reference
Error Number: 900
| 2025 AN UNEXPECTED ERROR WAS ENCOUNTERED DURING CLOSE WORKSTATION |
Explanation: While the device support was attempting to close the workstation, a component failed to successfully complete.
System Action: The workstation continues to close, performing as much of the close function as possible.
Programmer Response: Rerun the application with the graPHIGS API trace turned on to determine which component of the close process resulted in the error. If you cannot determine the cause of the error, contact a service representative.
Error Number: 910
| 2026 THE DISPLAY LIST BUFFER IS FULL |
Explanation: A request for 5080 display list storage could not be fulfilled.
System Action: Processing continues. However, the state of the 5080 workstation at this point is indeterminate. Structure contents on the workstation may not be consistent with the graPHIGS API structure contents. Thus, the results of any further structure editing on the workstation are unpredictable.
Programmer Response: In order to reconcile the 5080 workstation's structured contents with the graPHIGS API structure contents, you must disassociate all roots from the workstation and re-associate them. Delete any unnecessary structures and elements in order to make room on the workstation. If this error happened on a GPOPWS (Open Workstation) call, contact a service representative.
Error Number: 930
| 2027 ASYNCHRONOUS 5080 ERROR, SENSE = xxxxxxxx xxxxxxxx xxxxxxxx xxxx |
Explanation: An unexpected asynchronous error was received from the 5080. The first 14 bytes of the sense data, as returned from Graphics Access Method (GAM), are inserted in the message. This is shown by x's in the message description.
System Action: The operation continues. However, more errors may be generated depending on the cause of the error.
Programmer Response: Examine the sense data and consult the IBM 5080 Graphics System: Principles of Operation to determine the cause of the error. The section "Status and Sense" goes through a bit-by-bit explanation of the sense words and their meaning. This is probably not an application error. Contact your service representative.
Error Number: 930
| 2028 5080 I/O ERROR: R: xx, C: xx S: xxxxxxxx xxxxxxxx xxxxxxxx xxxx |
Explanation: An I/O operation, initiated by the 5080 device support, resulted in an abnormal completion code. The X's in the message description represent the following I/O error information:
In the RT PC environment, in addition to an error being logged, a trace of the CCW program causing the error is dumped to 'stderr'
System Action: The operation continues. However, more errors may be generated depending on the cause of the error.
Programmer Response: Check to be sure that the 5081 or 5085 is powered on. Examine the sense data and consult the IBM 5080 Graphics System: Principles of Operation, to determine the cause of the error. The section "Status and Sense" goes through a bit-by-bit explanation of the sense words and their meaning. This is probably not an application error. Contact your service representative.
Error Number: 930
| 2029 THE 5085 LINK HAS BEEN SWITCHED AWAY |
Explanation: After the 5085 workstation was opened, a Link Switch Notification was received indicating that the 5085 link was switched away from the current environment. This message is only logged if Link Switch Notification is not enabled via the GPES call. See The graPHIGS Programming Interface: Subroutine Reference for more details.
System Action: Workstation processing continues but may result in I/O errors under certain circumstances. No further I/O will be performed to the workstation, and no updates will be seen.
Programmer Response: An application should utilize the Link Switch Notification Escape Function to handle this situation. If you wish to continue using the workstation, it should be closed and reopened after receiving Event Type 101 (Link Switch back to the application). See The graPHIGS Programming Interface: Subroutine Reference, for information on the GPES function and The graPHIGS Programming Interface: Technical Reference for information on the 5085 workstation.
Error Number: 930
| 2030 GAM HAS RETURNED AN ERROR ON SPECIFYING AN ATTENTION ROUTINE |
Explanation: The device support received a non-zero return code in response to a Graphics Access Method (GAM) SPAR Macro. See Graphics Access Method/System Product: Application Programming Guide
System Action: The workstation is not opened.
Programmer Response: Contact a service representative.
Error Number: 940
| 2031 UNABLE TO GET THE CONFIGURATION DATA FROM THE 5080 |
Explanation: The device support received a non-zero code in response to a Graphics Access Method (GAM) GRAFINQ Macro. See Graphics Access Method/System Product: Application Programming Guide
System Action: The workstation is not opened.
Programmer Response: Be sure the device is powered on and does not have any hardware problems. Contact a service representative.
Error Number: 940
| 2032 THE NUMBER OF BIT PLANES IN THE CONFIGURATION DATA IS INVALID |
Explanation: The configuration data returned indicates that the 5080 does not have 2, 4, 6, or 8-bit planes.
System Action: The workstation is not opened.
Programmer Response: Be sure there are no 5080 hardware problems.
Error Number: 940
| 2033 UNABLE TO OPEN GDDM |
Explanation: GDDM has returned an error on trying to open the workstation.
System Action: The workstation is not opened.
Programmer Response: Check the error file for the error messages that GDDM has produced. See Graphical Data Display Manager: Messages, for an explanation.
Error Number: 940
| 2034 TABLE EXTENTS ARE TOO LARGE FOR INITIALIZATION |
Explanation: There is not enough storage available in the 5080 to perform table initialization.
System Action: The workstation is not opened.
Programmer Response: Reduce the values specified for definable options (view table entries, string devices, etc.) to allow initialization. If the error still occurs, you must upgrade the 5080 memory to make additional memory available.
Error Number: 940
| 2036 ERROR 0001 - CONTACT SERVICE PERSONNEL |
Explanation: This is a 5080 device support internal error.
System Action: None.
Programmer Response: If possible, reproduce the error with the graPHIGS API trace turned on. Contact and inform a service representative of the error number and conditions surrounding its occurrence.
Error Number: 940
| 2037 ERROR 0002 - CONTACT SERVICE PERSONNEL |
Explanation: This is a 5080 device support internal error.
System Action: The function is ignored.
Programmer Response: If possible, reproduce the error with the graPHIGS API trace turned on. Contact and inform a service representative of the error number and conditions surrounding its occurrence.
Error Number: 900
| 2038 ERROR 0003 - CONTACT SERVICE PERSONNEL |
Explanation: This is a 5080 device support internal error.
System Action: The workstation is not opened.
Programmer Response: If possible, reproduce the error with the graPHIGS API trace turned on. Contact and inform a service representative of the error number and conditions surrounding its occurrence.
Error Number: 940
| 2039 ERROR 0004 - CONTACT SERVICE PERSONNEL |
Explanation: This is a 5080 device support internal error.
System Action: The workstation is not opened.
Programmer Response: If possible, reproduce the error with the graPHIGS API trace turned on. Contact and inform a service representative of the error number and conditions surrounding its occurrence.
Error Number: 940
| 2040 ERROR 0008 - CONTACT SERVICE PERSONNEL |
Explanation: This is a GDDM device support internal message.
System Action: None.
Programmer Response: If possible, reproduce the error with the graPHIGS API trace turned on. Contact and inform a service representative of the error number and conditions surrounding its occurrence.
Error Number: 900
| 2041 ADMxxxx {MESSAGE TEXT} |
Explanation: GDDM has encountered a warning type error.
System Action: None.
Programmer Response: See Graphical Data Display Manager: Messages
Error Number: 910
| 2042 ADMxxxx {MESSAGE TEXT} |
Explanation: GDDM has encountered an error.
System Action: None.
Programmer Response: See Graphical Data Display Manager: Messages
Error Number: 920
| 2043 ADMxxxx {MESSAGE TEXT} |
Explanation: GDDM has encountered a severe error.
System Action: None.
Programmer Response: See Graphical Data Display Manager: Messages
Error Number: 930
| 2044 ADMxxxx {MESSAGE TEXT} |
Explanation: GDDM has encountered a terminating error.
System Action: None.
Programmer Response: See Graphical Data Display Manager: Messages
Error Number: 940
| 2045 CONNECTION TO X SERVER LOST |
Explanation: The X workstation is no longer able to communicate with the X server. This condition may be caused by either the termination of the X server process or an interruption in the network connection between the nucleus and the server.
System Action: The graphics device is now in an indeterminate state.
Programmer Response: The application should detect this error in its error handler and when notified of this error, the application should issue either the Disconnect Nucleus (GPDNC) or Close graPHIGS (GPCLPH) subroutine call. If this is not done, a wait condition may occur. Restart the failing X server or correct the network connection problem.
Error Number: 930
| 2046 X PROTOCOL ERROR, message text, REQCDE = request code, RESID = resource id |
Explanation: A graPHIGS API error has occurred or an X server resource shortage has caused the failure of a resource allocation request. The message text, request code, and resource id come directly from X. See The AIX X-Windows Programmer's Reference for an explanation of these fields.
System Action: The graphics device is now in an indeterminate state. Operation may continue, but results may be unpredictable.
Programmer Response: If the message text suggests a resource shortage, the user should take steps to reduce usage on the X server, possibly by removing other executing applications. Otherwise, inform a service representative of the error number and the conditions surrounding its occurrence.
Error Number: 930
| 2047 XOPENDISPLAY FAILED - CHECK THE graPHIGS CONNID |
Explanation: The X workstation is not able to connect to the X server that was specified by the connection identifier connid parameter on the GPCRWS or GPOPWS subroutine calls, or by a nickname in the External Defaults File (EDF) or Application Default Interface Block (ADIB).
System Action: The workstation is not opened.
Programmer Response: Verify that the connection identifier connid is correct and that all remote devices, and the paths to them, are operational. Also, verify that the host name has been enabled for access to the X server. For information on the xhost command, see The AIX X-Windows Programmer's Reference
Error Number: 930
| 2048 USER-SUPPLIED WINDOW ID INVALID, WINDOW ID = window id |
Explanation: The X window identifier that was passed in by the application using the XWINDID PROCOPT in the Application Default Interface Block (ADIB) is invalid.
System Action: The workstation is not opened.
Programmer Response: Correct the value of the window identifier passed to the graPHIGS API in the ADIB.
Error Number: 930
| 2049 UNSUPPORTED X VISUAL |
Explanation: An X window identifier was passed in by the application using the XWINDID PROCOPT in the Application Default Interface Block (ADIB). The window was created using the DirectColor or TrueColor visuals. The graPHIGS API X workstation does not support the DirectColor or TrueColor visuals.
System Action: The workstation is not opened.
Programmer Response: A server with DirectColor or TrueColor may also support the other visuals. Create a window using a supported visual and pass the window id to the graPHIGS API.
Error Number: 930
| 2050 INSUFFICIENT DATA LEN n1 FOR CGM WDO |
Explanation: An application attempted to generate workstation-dependent output (WDO), and GPWDO or GPES with a function identifier (funcid) of 1014 was invoked with an invalid length parameter. One of the following conditions exists:
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPWDO or GPES that caused the error. Correct the length parameter. See The graPHIGS Programming Interface: Technical Reference for more information on CGM binary encoded elements.
Error Number: 920
| 2051 DATA LEN n1 > 32771 FOR CGM WDO |
Explanation: An application attempted to generate workstation-dependent output (WDO), and GPWDO or GPES with a function identifier (funcid) of 1014 was invoked with an invalid length parameter. Data must not exceed a single partition. The maximum length of data that fits in a single partition is 32771 bytes, which includes 4 bytes from the long form header.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPWDO or GPES that caused the error. Correct the length parameter. See The graPHIGS Programming Interface: Technical Reference for more information on CGM binary encoded elements.
Error Number: 921
| 2052 DATA LEN n1 <> ENCODED LEN n2 + HDRSZ n3 IN CGM WDO - USING ENCODED LEN |
Explanation: An application attempted to generate workstation-dependent output (WDO), and GPWDO or GPES a function identifier (funcid) of 1014 was invoked with a value for the length parameter that does not match the encoded length.
System Action: One of the following actions was taken:
Programmer Response: Locate the specific invocation of GPWDO or GPES that caused the error. Correct the value for the length parameter. See The graPHIGS Programming Interface: Technical Reference for more information on CGM binary encoded elements.
Error Number: 910