| 100 NUMBER OF POINTS < ZERO |
Explanation: A subroutine was called with the number of points value less than zero. The number of points value must be greater than or equal to zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to d etermine which function caused the error. Correct the number of points parameter.
Error Number: 100
| 101 NUMBER OF SPHERES < ZERO |
Explanation: GPSPH was invoked with the number of spheres less than zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPSPH that caused the error. Correct the number of spheres.
Error Number: 101
| 102 PARAMETRIC SURFACE CHARACTERISTICS TYPE IS INVALID |
Explanation: GPPSC was invoked with an invalid parametric surface characteristic type.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPPSC that caused the error. Correct the parametric surface characteristic type parameter.
Error Number: 102
| 103 PARAMETRIC SURFACE CHARACTERISTICS DATA IS INVALID |
Explanation: GPPSC was invoked with an invalid parametric surface characteristic data.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPPSC that caused the error. Correct the parametric surface characteristic data parameter.
Error Number: 103
| 105 GEOMETRIC TEXT CULLING DISPLAY METHOD IS INVALID |
Explanation: GPGTXC was invoked with an invalid geometric text culling display method.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPGTXC that caused the error. Correct the geometric text culling display method.
Error Number: 105
| 106 GEOMETRIC TEXT CULLING HEIGHT < ZERO |
Explanation: GPGTXC was invoked with an invalid geometric text culling height of less than zero. The geometric text culling height must be greater than or equal to zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPGTXC that caused the error. Correct the geometric text culling height.
Error Number: 106
| 107 REFERENCE VECTORS ARE COLINEAR |
Explanation: A subroutine was invoked with the two reference vectors parallel. These two vectors are used to define a local text plane for drawing the primitive and, therefore, must not be parallel.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the reference vector parameters. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of text primitives.
Error Number: 107
| 108 NUMBER OF CHARACTERS IN TEXT STRING < ZERO |
Explanation: A subroutine was invoked with the character string length less than zero. The number of characters in the text string must be greater than or equal to zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log or error indicator parameter, as appropriate, to determine which function caused the error. Correct the string length parameter.
Error Number: 108
| 110 REFLECTANCE MODEL IS INVALID |
Explanation: GPBRMO or GPRMO was invoked with an invalid reflectance model value parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the reflectance model parameter.
Error Number: 110
| 111 AMBIENT COEFFICIENT IS INVALID |
Explanation: GPBSPR or GPSPR was invoked with an invalid ambient coefficient value parameter. The ambient coefficient must be 0.0 <= value <= 1.0.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the ambient coefficient value parameter.
Error Number: 111
| 112 DIFFUSE COEFFICIENT IS INVALID |
Explanation: GPBSPR or GPSPR was invoked with an invalid diffuse coefficient value parameter. The diffuse coefficient must be 0.0 <= value <= 1.0.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the diffuse coefficient value parameter.
Error Number: 112
| 113 SPECULAR COEFFICIENT IS INVALID |
Explanation: GPBSPR or GPSPR was invoked with an invalid specular coefficient value parameter. The specular coefficient must be 0.0 <= value <= 1.0.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the specular coefficient value parameter.
Error Number: 113
| 114 SPECULAR EXPONENT IS INVALID |
Explanation: GPBSPR or GPSPR was invoked with an invalid specular exponent. The specular exponent must be greater than or equal to zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the specular exponent value parameter.
Error Number: 114
| 115 TRANSPARENT COEFFICIENT IS INVALID |
Explanation: A subroutine was invoked with an invalid transparent coefficient value. The transparent coefficient must be 0.0 <= value <= 1.0.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the transparent coefficient parameter.
Error Number: 115
| 116 NUMBER OF LIGHT SOURCE INDEXES < ZERO |
Explanation: GPLSS was invoked with an invalid number of light source indexes parameter. The number of light source indexes must be greater than or equal to zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPLSS that caused the error. Correct the number of light source indexes parameter.
Error Number: 116
| 118 FRAME BUFFER COMPARISON IS INVALID |
Explanation: GPFBC was invoked with an invalid frame buffer comparison parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPFBC that caused the error. Correct the frame buffer comparison. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of frame buffer functions.
Error Number: 118
| 119 FRAME BUFFER COMPONENT NUMBER IS INVALID |
Explanation: GPRDFB was invoked with an invalid frame buffer component number parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPRDFB that caused the error. Correct the frame buffer component number parameter.
Error Number: 119
| 120 WARNING, ONE OR MORE STRUCTURES DO NOT EXIST |
Explanation: A subroutine was invoked that specified one or more structures that do not exist in the source resource. (The source resource can be either a structure store or an archive file, depending on which subroutine was used.)
System Action: One of the following actions is taken, depending on the condition:
Programmer Response: Check the error log to determine which function issued the warning. If the message is unexpected, verify the existence of the structure identifiers in the parameter list by using either GPQSTI, GPQSTS (for a structure store) or GPRSTI (for an archive file). Correct the structure identifier list.
Error Number: 120
| 121 EDIT MODE IS INVALID |
Explanation: GPEDMO was invoked with an invalid edit mode.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPEDMO that caused the error. Correct the edit mode parameter.
Error Number: 121
| 122 STRUCTURE IDENTIFIER DOES NOT EXIST |
Explanation: A structure store inquiry or GPQVR was invoked to derive information about a structure that does not exist.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of the function that caused the error. This error can be returned only on an inquiry function. Therefore, it can be detected only by checking the error indicator parameter after invoking the inquiry function. The programmer can correct the parameter with an existing structure identifier, or ignore the results returned. Use the inquiry function GPQSTI to inquire the structures currently defined. Use GPQSTS to determine if an individual structure exists.
Error Number: 122
| 123 CONDITION CRITERIA IS INVALID |
Explanation: GPCEXS or GPCRET was invoked with an invalid condition criteria value.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the value of the criteria parameter.
Error Number: 123
| 124 EXECUTE MODE IS INVALID |
Explanation: GPCEXS was invoked with an invalid invocation mode value.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCEXS that caused the error. Correct the value of the invocation mode.
Error Number: 124
| 125 ATTEMPTING TO EXECUTE THE OPEN STRUCTURE |
Explanation: GPCEXS, GPCPER, GPCPST, or GPEXST was invoked with a structure identifier equal to the current open structure. Self-referencing structures are not allowed.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the structure identifier parameter, so that it does not reference the current open structure.
Error Number: 125
| 126 PRIORITY VALUE IS INVALID |
Explanation: GPARV, GPCIM2, or GPCIM3 was invoked with an invalid priority value. Priorities must be in the range (0.0 <= priority <=1.0).
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the priority parameter.
Error Number: 126
| 127 CONFLICT RESOLUTION FLAG IS INVALID |
Explanation: GPCNRS, GPTAST, or GPTST was invoked with an invalid value for the conflict resolution flag.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCNRS, GPTAST, or GPTST that caused the error. Correct the conflict resolution flag parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 127
| 128 STRUCTURE CONFLICT OCCURS WHEN RESOLUTION FLAG IS ABANDON |
Explanation: A subroutine was invoked with the conflict resolution flag set to 2=ABANDON , and a conflict was found.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. If the message is unexpected, then verify which structures in the source structure store or archive file conflict with the structures in the destination structure store or archive file, using the appropriate inquiry subroutine -- such as GPQACA or GPQACS Depending on the desired result, the application could:
Error Number: 128
| 129 ATTEMPTING TO HAVE THE RESULTING STRUCTURE EXECUTE ITSELF |
Explanation: GPCSI, GPCSRS, or GPCSIR was invoked with an original structure identifier and a resulting structure identifier such that either the original structure references the resulting structure (GPCSI or GPCSRS) or the resulting structure references the original structure (GPCSRS). This would cause the resulting structure to have an execute structure-type element that referenced itself when the subroutine was completed.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Change the structure identifier in error.
Error Number: 129
| 130 LABEL IDENTIFIER CANNOT BE FOUND IN THE OPEN STRUCTURE |
Explanation: Either GPDELB, GPEPLB or GPEPLG (with label search flag set to WRAP) was invoked with a nonexistent label identifier, or GPDLEG or GPEPLG (with label search flag set to NOWRAP) was invoked with a label identifier that did not exist between the current element pointer to the end of the structure. When calling GPDELB or GPDLEG, both labels must exist.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the parameter or be sure that the specified labels exist.
Error Number: 130
| 132 ELEMENT CODE DOES NOT EXIST BEFORE END OF STRUCTURE |
Explanation: GPEPCD was invoked. An element with the desired element code was not found before the end of the open structure.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPEPCD that caused the error. Correct the element code, or be sure that an element with the specified code exists in the structure (from the current element to the end of the structure).
Error Number: 132
| 133 LABEL DELETE OPTION IS INVALID |
Explanation: GPDLEG was invoked with an invalid label deletion option value.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDLEG that caused the error. Correct the label deletion option value.
Error Number: 133
| 134 NUMBER OF ENTRIES IN LIST < ONE |
Explanation: A subroutine was invoked that specified a number less than one in the number of structures identifier parameter. The value for this parameter must be greater than one.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the number of structures identifier parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 134
| 135 VALUE OF SOURCE IS INVALID |
Explanation: GPQCNA or GPQCSN was invoked with an invalid value for the source parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPQCNA or GPQCSN that caused the error. Correct the source parameter.
Error Number: 135
| 136 VALUE OF SEARCH FLAG IS INVALID |
Explanation: GPEPLG or GPEPPG was invoked with an invalid search flag.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Change the search flag to one of the allowed search options.
Error Number: 136
| 137 VALUE OF CONDITIONAL EDIT FLAG IS INVALID |
Explanation: GPCEDT was invoked with an invalid edit flag.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCEDT that caused the error. Change the edit flag to one of the allowed edit options.
Error Number: 137
| 138 STARTING ELEMENT CANNOT BE FOUND |
Explanation: GPATS or GPTE was invoked with an invalid starting element.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the starting element parameter.
Error Number: 138
| 139 SEARCH METHOD IS INVALID |
Explanation: GPTE, GPATS, or GPNLER was invoked with an invalid search method.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the search method parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 139
| 140 DEVICE NUMBER < ONE OR DEVICE NOT AVAILABLE |
Explanation: A subroutine was invoked with one of the following conditions existing:
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log or the error indicator parameter, as appropriate, to determine which function caused the error. Correct the parameter in error. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQLI to determine the supported input devices.
Error Number: 140
| 141 INPUT DEVICE NOT IN CORRECT MODE |
Explanation: A subroutine was invoked without the device in the proper mode. All input device initialization and request functions require the device to be in REQUEST mode.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the application so that the input device is the proper mode when the function is called. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of input device modes.
Error Number: 141
| 142 VALUE OF ARCHIVE FLAG IS INVALID |
Explanation: GPOPAR was invoked with an invalid archive flag parameter value.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPOPAR that caused the error. Correct the archive flag parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 142
| 143 OPTION VALUE IS INVALID |
Explanation: GPNLER was invoked with an invalid option.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPNLER that caused the error. Correct the option. See The graPHIGS Programming Interface: Subroutine Reference for valid parameters.
Error Number: 143
| 144 PROMPT/ECHO TYPE NOT AVAILABLE ON WORKSTATION |
Explanation: An input device initialization subroutine was called, and the specified prompt/echo type is unavailable on the workstation.
System Action: Type one is used.
Programmer Response: Check the error log to determine which function caused the error. Correct the prompt/echo type parameter. See The graPHIGS Programming Interface: Technical Reference or use one of the inquiry functions, GPQDxx, to determine the supported prompt/echo types.
Error Number: 144
| 145 ECHO AREA BOUNDARY VALUE IN ERROR |
Explanation: An input device initialization subroutine was called with an invalid echo area boundary. All echo area boundary values must be within the device coordinate range. Also, minimum values must always be less than the corresponding maximum values.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the echo area parameter.
Error Number: 145
| 146 FIELD IN INPUT DEVICE DATA RECORD IN ERROR |
Explanation: An input device initialization subroutine was called with an invalid data record. The error may be one of the following conditions:
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. See The graPHIGS Programming Interface: Subroutine Reference for valid data record formats. Then, either correct the data record, or change the prompt/echo type to match the specified data record.
Error Number: 146
| 147 EVENT QUEUE HAS OVERFLOWED |
Explanation: The event queue overflow occurs asynchronous to application processing and is reported on the next invocation of a subroutine, which forces an update of the event queue.
System Action: No other event report will be accepted until the event queue is cleared.
Programmer Response: Check the error log to determine which function caused the error. The application may use GPQIQO to inquire the workstation and the device which caused the overflow. The event queue can be cleared using AWAIT and/or FLUSH subroutines.
Error Number: 147
| 148 EVENT QUEUE HAS NOT OVERFLOWED |
Explanation: GPQIQO has been called and the queue has not overflowed.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPQIQO that caused the error. This error can be returned only on an inquiry function. Therefore, it can be detected only by checking the error indicator parameter after invoking the inquiry function. This is probably not an error and requires no response if the application intends to poll the event queue overflow status. GPQIQO will be used most often, within an application defined error handler, in response to event queue overflow.
Error Number: 148
| 150 GET FUNCTION DOES NOT MATCH CURRENT EVENT CLASS |
Explanation: A GPGTxx subroutine was invoked for a device class that does not match the class in the current event report (CER).
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log for the function causing the error. Be sure the device class returned on the previous GPAWEV is used to select the correct GPGTxx subroutine. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of input queue handling.
Error Number: 150
| 151 TIMEOUT VALUE < ZERO |
Explanation: GPAWEV was invoked with a timeout value less than zero. The timeout value must be greater than or equal to zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPAWEV that caused the error. Correct the timeout parameter. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of GPAWEV timeout.
Error Number: 151
| 152 INITIAL CHOICE VALUE < ZERO OR IS INVALID |
Explanation: GPINCH was invoked with an invalid initial choice value. The choice value was less than zero, or not a valid choice alternative supported by the device.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPINCH that caused the error. Correct the initial choice parameter. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQIT to determine the valid choice alternatives on this device.
Error Number: 152
| 155 VIEW PRIORITY REFERENCE NUMBER IS INVALID |
Explanation: GPVIP, GPVOP, or GPVP was invoked with an invalid view priority reference number. The view priority reference number must be a valid view index (greater than or equal to zero and less than or equal to the maximum number of view table entries that the workstation supports).
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the view priority reference parameter. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQNV to determine the valid range for a specific workstation.
Error Number: 155
| 156 |
Explanation: GPINPK was invoked with an invalid pick path order.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPINPK that caused the error. Correct the pick path order parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 156
| 158 INVALID ELEMENTS IN THE INITIAL PICK PATH |
Explanation: GPINPK was invoked with invalid pick path elements. The following conditions must exist for a valid pick path:
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPINPK that caused the error. Correct the pick path parameter. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of the pick path.
Error Number: 158
| 160 PHYSICAL INPUT DEVICE CATEGORY IS INVALID |
Explanation: GPEPD, GPPDMO, or GPQPDC was invoked with an invalid physical device category.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log or error indicator parameter, as appropriate, to determine which function caused the error. Correct the physical device category parameter. See The graPHIGS Programming Interface: Subroutine Reference for the valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of physical device categories.
Error Number: 160
| 161 PHYSICAL INPUT VALUE IS INVALID |
Explanation: GPEPD was invoked with an invalid physical input value.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPEPD that caused the error. Correct the physical input value. See The graPHIGS Programming Interface: Subroutine Reference for the valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of physical input values.
Error Number: 161
| 162 PHYSICAL INPUT DEVICE HAS NOT BEEN DISABLED |
Explanation: GPEPD was invoked for a physical input device that has not been disabled.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPEPD that caused the error. Ensure that the physical input device is in disabled mode. A GPPDMO call may have been omitted or failed.
Error Number: 162
| 163 PHYSICAL DEVICE MODE IS INVALID |
Explanation: GPPDMO was invoked with an invalid physical device mode.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPPDMO that caused the error. Correct the physical device mode parameter.
Error Number: 163
| 164 PICK DEVICE DOES NOT PROVIDE EXTENDED INFORMATION |
Explanation: GPRQXP or GPSMXP was invoked for a pick device that does not provide extended pick information.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. For pick devices that do not provide extended pick information, use the function GPRQPK or GPSMPK
Error Number: 164
| 166 INITIAL PICK CORRELATION STATE IS INVALID |
Explanation: GPIPKC was invoked with an invalid initial pick correlation state.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPIPKC that caused the error. Correct the initial pick correlation state parameter.
Error Number: 166
| 167 PICK SELECTION CRITERIA IS INVALID |
Explanation: GPPKSC was invoked with an invalid pick selection criteria parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPPKSC that caused the error. Correct the pick selection criteria parameter.
Error Number: 167
| 168 INPUT DEVICE IS CURRENTLY OWNED BY ANOTHER CONNECTION |
Explanation: A set mode routine was invoked for a logical device that was in use by another application process. Some other application process has activated the device for input, and no other application process may activate the device for input until the device becomes inactive.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Cooperating application processes need to be aware of each other's operations. When a device is activated for input by an application process, no other application process may receive input from the device until the device is deactivated explicitly by the owning application process, or implicitly by the graPHIGS API
Error Number: 168
| 169 PHYSICAL INPUT DEVICE CANNOT BE DISABLED |
Explanation: GPPDMO was invoked for a physical device that cannot be disabled.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See also The graPHIGS Programming Interface: Technical Reference r use the inquiry function GPQPDC to determine if a physical device may be disabled.
Error Number: 169
| 177 ORIGIN PARAMETER IS INVALID |
Explanation: GPCVD was invoked with an invalid origin parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCVD that caused the error. Correct the origin parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid origin values.
Error Number: 177
| 178 DATATYPE PARAMETER IS INVALID |
Explanation: GPCVD was invoked with an invalid datatype parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCVD that caused the error. Correct the datatype parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid datatype parameter values.
Error Number: 178
| 179 ENVIRONMENT DESCRIPTOR IS INVALID |
Explanation: GPCVD was invoked with an invalid environment descriptor.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCVD that caused the error. Correct the environment descriptor. See The graPHIGS Programming Interface: Subroutine Reference for valid environment descriptor values.
Error Number: 179
| 180 CURSOR SHAPE TYPE IS NOT SUPPORTED |
Explanation: GPCUS was invoked for a fixed cursor shape type which is not supported on the workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCUS that caused the error. Correct the fixed cursor shape type to one that is supported by your workstation. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See also The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQCUF to determine available fixed cursor types.
Error Number: 180
| 181 CURSOR PIXEL ARRAY SIZE IS INVALID |
Explanation: GPCUR was invoked with an invalid cursor pixel array size.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCUR that caused the error. Correct the pixel array sizes.
Error Number: 181
| 182 CURSOR SHAPE TABLE INDEX NOT WITHIN WORKSTATION TABLE RANGE |
Explanation: GPCUR or GPCUS was invoked using a cursor shape table index that is not within the valid range of indexes for the cursor shape table. The index supplied was either less than one or greater than the maximum entry.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See also The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQCUF to determine the maximum number of cursor shape table entries.
Error Number: 182
| 183 SPECIFIED CURSOR FORMAT IS NOT SUPPORTED |
Explanation: GPCUR was invoked with a cursor definition format that is not supported on the specified workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCUR that caused the error. Correct the cursor definition format to one that your workstation supports. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See also The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQCUF to obtain a list of available cursor definition formats.
Error Number: 183
| 197 MESSAGE STRING LENGTH < ZERO |
Explanation: GPMSG, GPSBMS, and GPSPMS was invoked with a message string that has less than zero characters. A message must have zero or more characters.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the message length parameter.
Error Number: 197
| 198 NUMBER OF SUBAREAS < ZERO |
Explanation: GPPGD2, GPPGD3, GPPG2 or GPPG3 was called with a number of polygon subareas less than zero. A polygon must have zero or more subareas.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the polygon subareas parameter.
Error Number: 198
| 199 POLYGON SUBAREA HAS < ZERO POINTS |
Explanation: GPPGD2, GPPGD3, GPPG2 or GPPG3 was called with one of the entries in the number of points per subarea parameter less than zero. A subarea must have zero or more points.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the polygon subarea parameter.
Error Number: 199