| 201 SPECIFIED NUCLEUS IDENTIFIER ALREADY IS IN USE |
Explanation: GPCNC was invoked with a nucleus identifier for which a nucleus connection already exists.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCNC that caused the error. Select a unique nucleus identifier. Check that a unique nucleus identifier is supplied for each nucleus connection requested.
Error Number: 201
| 202 SPECIFIED NUCLEUS DOES NOT EXIST |
Explanation: A subroutine has been invoked with an invalid nucleus identifier.
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. Ensure that a valid nucleus identifier is specified.
Error Number: 202
| 203 SPECIFIED CONNECTION METHOD IS NOT SUPPORTED |
Explanation: GPCNC was invoked with an invalid communication method.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCNC that caused the error. Correct the communication method parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See also The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQCMM to obtain a list of valid communication methods.
Error Number: 203
| 204 NUCLEUS CONNECTION FAILED |
Explanation: GPCNC has failed to establish a connection to the specified nucleus.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCNC that caused the error. Ensure that the target nucleus specification is correct, that the nucleus is active and ready for operation, and that any required communication facilities are operational.
Error Number: 204
| 205 SHELL DEFERRAL MODE IS INVALID |
Explanation: GPSHDF was invoked with an invalid deferral mode.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPSHDF that caused the error. Correct the deferral mode parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See also The graPHIGS Programming Interface: Understanding Concepts, for an explanation of shell deferral mode, or use the inquiry function GPQSHD to obtain a list of available shell deferral modes.
Error Number: 205
| 206 SYNCHRONIZATION MODE IS INVALID |
Explanation: GPSYNC was invoked with an invalid synchronization mode.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPSYNC that caused the error. Correct the synchronization mode parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of synchronization mode.
Error Number: 206
| 207 SPECIFIED APPLICATION IDENTIFIER DOES NOT EXIST |
Explanation: GPSPMS was invoked with an invalid target application identifier.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPSPMS that caused the error. Correct the target application identifier parameter. Ensure that the target environment is active and ready to accept messages.
Error Number: 207
| 208 CONNECTION NOT CURRENTLY PERMITTED FROM THIS HOST |
Explanation: A connection to a remote graPHIGS API nucleus was attempted explicitly through the GPCNC subroutine or implicitly through the GPOPPH subroutine during nucleus connection processing. The host attempting the connection does not have permission to access the specified nucleus.
System Action: The subroutine call in error is ignored.
Programmer Response: Before connecting to a remote nucleus, you must indicate to the nucleus which hosts are permitted access. You allow host permission by issuing the gPhost command or by creating a default host access file. See The graPHIGS Programming Interface: Technical Reference for a discussion on remote nuclei.
Error Number: 208
| 209 UPDATE NOTIFICATION MODE IS INVALID |
Explanation: GPSHDF was invoked with an invalid update notification mode.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPSHDF that caused the error. Correct the update notification mode parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of update notification mode, or use the inquiry function GPQSHD to determine the valid update notification mode.
Error Number: 209
| 210 RESOURCE CREATION DETECTED AN INVALID USERID/PASSWORD |
Explanation: GPEXAP was invoked, and one of the following conditions exists:
A remote nucleus can perform userid/password checking only under the following conditions:
and
or
System Action: The subroutine call in error is ignored.
Programmer Response: Correct the problem in one of the following ways:
Error Number: 210
| 211 RESOURCE TYPE IS INVALID |
Explanation: A subroutine was invoked with an invalid resource type.
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 resource type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resource types.
Error Number: 211
| 212 SPECIFIED RESOURCE IDENTIFIER DOES NOT EXIST |
Explanation: GPATR was invoked with an invalid nucleus resource identifier.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPATR that caused the error. Correct the resource identifier parameter.
Error Number: 212
| 213 SPECIFIED PASSWORD IS INCORRECT |
Explanation: GPATR or GPSPMS was invoked with an invalid password.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPATR or GPSPMS that caused the error. Correct the password parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of message and resource passwords.
Error Number: 213
| 214 PASSWORD CANNOT BE CHANGED FROM THIS APPLICATION |
Explanation: GPPW was invoked for a resource that was not created by the application.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPPW that caused the error. Correct the call. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources and passwords.
Error Number: 214
| 215 SPECIFIED RESOURCES DO NOT EXIST ON THE SAME NUCLEUS |
Explanation: A subroutine was invoked with resource identifiers that do not exist on the same target nucleus.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct one of the resource identifier parameters. See The graPHIGS Programming Interface: Subroutine Reference for parameter descriptions. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources and the nucleus.
Error Number: 215
| 216 ONE OR MORE RESOURCES IS NOT ATTACHED |
Explanation: GPQICH was invoked to return a list of image board identifiers, some of which are not attached to the application. The graPHIGS API will not return the list of image board identifiers, when one or more resources is not attached to the application.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPQICH 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. Either correct the workstation identifier, the image index, or attach the image board. See The graPHIGS Programming Interface: Subroutine Reference for parameter descriptions. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources and image boards.
Error Number: 216
| 217 RESOURCE CREATION REQUEST EXCEEDS NUCLEUS TABLE CAPACITY |
Explanation: A subroutine was invoked with the maximum number of the resource type currently created.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Either detach a resource using GPDTR, or change the program to avoid creating too many resources. See The graPHIGS Programming Interface: Subroutine Reference for parameter descriptions. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources.
Error Number: 217
| 218 ARCHIVE FILES ARE NOT SUPPORTED ON SPECIFIED NUCLEUS |
Explanation: GPOPAR was invoked and a nucleus was specified that does not support archive files.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPOPAR that caused the error. Correct the ncid parameter if that nucleus does not support archive files. (Not all graPHIGS API nuclei support archive files. For example, older versions of the nucleus and the nucleus in the 6090 do not support archive files.)
Error Number: 218
| 219 SPECIFIED ARCHIVE FILE IDENTIFIER ALEADY IN USE |
Explanation: GPOPAR or GPATR was invoked with a specified archive file identifier that is already in use.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPOPAR or GPATR that caused the error. Correct the arid parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 219
| 220 sPECIFIED ARCHIVE FILE DOES NOT EXIST |
Explanation: A subroutine was invoked with an archive file identifier that does not exist in the list of all opened archive files.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the arid parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 220
| 221 SPECIFIED STRUCTURE STORE IDENTIFIER ALREADY IS IN USE |
Explanation: GPATR or GPCRSS was invoked with a structure store identifier that is already in use.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Use another structure store identifier parameter, or detach the specified structure store. See The graPHIGS Programming Interface: Subroutine Reference for a parameter description. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources.
Error Number: 221
| 222 SPECIFIED STRUCTURE STORE DOES NOT EXIST |
Explanation: A subroutine was invoked with a structure store identifier for which a structure store has not been created.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log or error indicator parameter, as appropriate, to determine the function that caused the error. Use another structure store identifier parameter, or create the specified structure store prior to invoking the function. See The graPHIGS Programming Interface: Subroutine Reference for a parameter description. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources.
Error Number: 222
| 223 SPECIFIED STRUCTURE STORE TYPE IS NOT SUPPORTED |
Explanation: GPCRSS was invoked with a structure store type that is not supported. Ensure that you use structure store types that are valid for your level of the graPHIGS API
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCRSS that caused the error. Correct the structure store type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of structure store types.
Error Number: 223
| 224 SPECIFIED VIEW DOES NOT HAVE ASSOCIATED STRUCTURE STORE |
Explanation: GPARV was invoked before the specified workstation was associated to a structure store.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPARV that caused the error. Correct the workstation identifier to one that is associated to a structure store, or use GPASSW to associate the workstation to a structure store.
Error Number: 224
| 225 STRUCTURE STORE THRESHOLD SIZE < ZERO |
Explanation: GPSSTH was invoked with a structure store threshold value less than zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPSSTH that caused the error. Correct the threshold value to be an integer greater than zero.
Error Number: 225
| 226 MAXIMUM NUMBER OF SIMULTANEOUS ASSOCIATED WORKSTATIONS EXCEEDED |
Explanation: GPASSW was invoked directly (or indirectly) by GPOPWS to associate a structure store to all views of a workstation and the maximum number of workstations have already been associated to the structure store.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPASSW that caused the error. Correct the number of workstations that are associated to the structure store. The workstation cannot be associated to a structure store until one of the current associated workstations is disassociated from the structure store (by invoking the close workstation subroutine). At this time, the application should invoke GPASSW to associate the desired workstation to the structure store.
Error Number: 226
| 227 STRUCTURE STORE IS NOT SELECTED |
Explanation: GPQAR or GPQVR was invoked with no structure store selected.
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. Ensure that your application has created and selected a structure store prior to invoking the subroutine call. These functions may be done automatically for your application, unless overridden using the DEFNUC default in either the Application Defaults Interface Block (ADIB), or External Defaults File (EDF); ensure that the DEFNUC value is correct. See The graPHIGS Programming Interface: Technical Reference to determine the values supported by the DEFNUC default.
Error Number: 227
| 231 SPECIFIED IMAGE BOARD IDENTIFIER ALREADY IS IN USE |
Explanation: GPCRIB or GPATR was invoked with an image board identifier that was already in use.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the image board identifier to some value that has not already been used.
Error Number: 231
| 232 SPECIFIED IMAGE BOARD DOES NOT EXIST |
Explanation: A subroutine was invoked with an image board identifier which does not exist.
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 image board identifier to be one that exists.
Error Number: 232
| 233 SPECIFIED IMAGE BOARD BIT DEPTH IS NOT SUPPORTED |
Explanation: GPCRIB was invoked with a bit depth value that is not supported by the specified nucleus.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCRIB that caused the error. Correct the bit depth value to one that is supported by the specified nucleus. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function, GPQIBF, to determine what bit depth values are supported on the desired
Error Number: 233
| 234 SPECIFIED IMAGE BOARD SIZE IS INVALID |
Explanation: GPCRIB was invoked with a horizontal or vertical size that is not in the range supported by the specified nucleus.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCRIB that caused the error. Correct the horizontal or vertical size parameters. Use the inquiry function, GPQIBF, to determine the maximum vertical and horizontal sizes.
Error Number: 234
| 235 SPECIFIED IMAGE BOARD TYPE IS NOT SUPPORTED |
Explanation: GPCRIB was invoked with a image board type that is not supported by the specified nucleus.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCRIB that caused the error. Correct the image board type to one that is supported by the specified nucleus. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 235
| 236 RECTANGLE DEFINITION IS INVALID |
Explanation: A subroutine was invoked with a rectangle definition that is invalid. This error occurs if the source rectangle origin values are less than zero, the rectangle size values are less than one, or the rectangle exceeds the source image boundaries.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the rectangle definition (origin and size).
Error Number: 236
| 237 SPECIFIED APPLICATION IMAGE FORMAT IS NOT SUPPORTED |
Explanation: GPWRCT, GPRDFB, or GPRRCT was invoked with an invalid application image format 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 application image format parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing.
Error Number: 237
| 238 SPECIFIED TWO OPERAND OPERATION IS NOT SUPPORTED |
Explanation: GPTWPO was invoked with an invalid operation type parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPTWPO that caused the error. Correct the operation type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 238
| 239 SPECIFIED THREE OPERAND OPERATION IS NOT SUPPORTED |
Explanation: GPTHPO was invoked with an invalid operation type parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPTHPO that caused the error. Correct the operation type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 239
| 240 APPLICATION IMAGE DESCRIPTION IS INVALID |
Explanation: GPWRCT, GPRDFB, or GPRRCT was invoked with invalid data in the format-dependent 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 format-dependent parameter. Be sure that you use the correct parameters for the type of format that you have selected using the format parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing.
Error Number: 240
| 241 SPECIFIED FONT DIRECTORY IDENTIFIER ALREADY IS IN USE |
Explanation: GPATR or GPCRFD was invoked with a font identifier that is already in use.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Use another font directory identifier parameter, or detach the specified font directory. See The graPHIGS Programming Interface: Subroutine Reference for a parameter description. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources.
Error Number: 241
| 242 SPECIFIED FONT DIRECTORY DOES NOT EXIST |
Explanation: A subroutine was invoked with a font directory identifier that has not been created.
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. Use another font directory identifier parameter, or create the specified font directory prior to invoking the function. See The graPHIGS Programming Interface: Subroutine Reference for a parameter description and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of resources.
Error Number: 242
| 243 SPECIFIED FONT DIRECTORY TYPE IS NOT SUPPORTED |
Explanation: GPCRFD was invoked with a font directory type that is not supported. The font directory type parameter allows future extensions of the graPHIGS API Be sure that you use font directory types that are valid for your level of the graPHIGS API
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCRFD that caused the error. Correct the font directory type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of font directory types.
Error Number: 243
| 245 FONT OPTION IS INVALID |
Explanation: GPLDFO was invoked with an invalid font option that is not supported.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPLDFO that caused the error. Correct the font option. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 245
| 250 HLHSR IDENTIFIER IS INVALID |
Explanation: GPHID was invoked with a HLHSR identifier that was not valid.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPHID that caused the error. Correct the HLHSR identifier parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 250
| 251 SPECIFIED HLHSR MODE IS NOT SUPPORTED |
Explanation: GPXVR was invoked with a HLHSR mode that is not supported by the specified workstation identifier.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPXVR that caused the error. Correct the HLHSR mode with a mode that the workstation supports. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQHMO to determine what HLHSR modes are valid for a given workstation type.
Error Number: 251
| 252 ANTIALIASING IDENTIFIER IS INVALID |
Explanation: GPAID was invoked with an antialiasing identifier that was not valid.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPAID that caused the error. Correct the antialiasing identifier parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 252
| 253 SPECIFIED ANTIALIASING MODE IS NOT SUPPORTED |
Explanation: GPXVR was invoked with an antialiasing mode that is not supported by the specified workstation identifier.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPXVR that caused the error. Correct the antialiasing mode with a mode that the workstation supports. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQAMO to determine what antialiasing modes are valid for a given workstation type.
Error Number: 253
| 254 LIGHT SOURCE INDEX < ONE |
Explanation: GPLSR, GPLSS, or GPQLSR was invoked with an invalid light source index parameter. The light source index value must be greater than or equal to one.
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 light source index value parameter.
Error Number: 254
| 255 LIGHT SOURCE INDEX EXCEEDS THE WORKSTATION TABLE CAPACITY |
Explanation: GPLSR or GPQLSR was invoked with a light source index that was greater than the capacity of the light source table of the specified workstation.
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 light source index to be within the range allowed for the specified workstation. See The graPHIGS Programming Interface: Understanding Concepts, or use the inquiry function, GPQLSF, to determine the available information on light source facilities of the workstation.
Error Number: 255
| 256 ACTIVATE LIST AND DEACTIVATE LIST ARE NOT DISJOINT |
Explanation: GPLSS was invoked with an activation list and a deactivation list that had one or more entries that were the same.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPLSS that caused the error. Correct the values in the activation list (and/or the deactivation list), so that no entries in the activation list match any entry in the deactivation list.
Error Number: 256
| 257 LIGHTING CALCULATION MODE IS INVALID |
Explanation: GPLMO was invoked with an invalid lighting calculation mode parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPLMO that caused the error. Correct the lighting calculation mode parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid lighting calculation modes.
Error Number: 257
| 258 SPECIFIED LIGHT SOURCE TYPE IS NOT SUPPORTED |
Explanation: GPLSR was invoked with an invalid light source type parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPLSR that caused the error. Correct the light source type parameter. See The graPHIGS Programming Interface: Subroutine Reference for allowable light source types.
Error Number: 258
| 259 ONE OF LIGHT SOURCE PARAMETERS IS INVALID |
Explanation: GPLSR was invoked with an invalid value specified as part of a light source parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPLSR that caused the error. Correct the light source parameter. The light source parameter format depends on the light source type. Be sure the parameter matches the type. See The graPHIGS Programming Interface: Subroutine Reference for valid light source parameters.
Error Number: 259
| 260 SPECIFIED TRANSPARENT PROCESSING MODE IS NOT SUPPORTED |
Explanation: GPXVR was invoked with an invalid value for the transparent processing mode. A value specified for the transparent processing mode was invalid, or the specified mode is not available on the specified workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the invocation for GPXVR that caused the error. Correct the transparent processing mode. See The graPHIGS Programming Interface: Subroutine Reference for allowable transparent processing modes.
Error Number: 260
| 261 DEPTH CUE INDEX < ZERO |
Explanation: GPDCI, GPDCR, or GPQDCR was invoked with an invalid value for the depth cue index parameter. The value assigned was less than zero. The depth cue 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 determine which function caused the error. Correct the value of the depth cue index parameter.
Error Number: 261
| 262 DEPTH CUE INDEX EXCEEDS THE WORKSTATION TABLE CAPACITY |
Explanation: GPDCR or GPQDCR was invoked with an invalid depth cue index value that exceeds the workstation table capacity.
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. Use the appropriate inquiry function to determine the size of depth cue table for your workstation.
Error Number: 262
| 263 DEPTH CUE REFERENCE PLANE IS INVALID |
Explanation: GPDCR was invoked with invalid far and near depth cue reference plane distances. The far distance must be less than the near distance.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDCR that caused the error. Correct the far and near distance values.
Error Number: 263
| 264 DEPTH CUE SCALE FACTOR IS INVALID |
Explanation: GPDCR was invoked with invalid depth cue scale factors.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDCR that caused the error. Correct the scale factor parameter.
Error Number: 264
| 265 COLOR PROCESSING INDEX < ZERO |
Explanation: GPCPI, GPCPR, GPQCPR, or GPXVR was invoked with a color processing index less than zero. The index 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 color processing index parameter.
Error Number: 265
| 266 COLOR PROCESSING INDEX EXCEEDS THE WORKSTATION TABLE CAPACITY |
Explanation: GPCPR, GPQCPR, or GPXVR was invoked with a color processing index which was too large for the specified workstation. The color processing index must be less than or equal to the maximum index supported on the workstation.
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 color processing index parameter. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQCPF to determine the supported color processing indexes.
Error Number: 266
| 267 SPECIFIED RENDERING COLOR MODEL IS NOT SUPPORTED |
Explanation: GPCPR was invoked with a color model value which is not supported on the specified workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCPR that caused the error. Correct the color processing index parameter. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQRCM to determine the supported rendering color models.
Error Number: 267
| 268 SPECIFIED QUANTIZATION METHOD IS NOT SUPPORTED |
Explanation: GPCPR was invoked with a color quantization method that is not supported on the specified workstation.
System Action: The function is ignored.
Programmer Response: Locate the specific invocation of GPCPR that caused the error. Correct the color quantization method parameter. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQCQM to determine the supported color quantization methods.
Error Number: 268
| 269 ONE OF QUANTIZATION PARAMETERS IS INVALID |
Explanation: GPCPR was invoked with an invalid color quantization parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCPR that caused the error. Correct the color quantization parameter.
Error Number: 269
| 272 GROUP IDENTIFIER IS INVALID |
Explanation: A subroutine was invoked with an invalid group identifier parameter.
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 group identifier parameter. See The graPHIGS Programming Interface: Subroutine Reference for a list of allowable group identifiers.
Error Number: 272
| 273 NUMBER OF GROUP IDENTIFIERS < ONE |
Explanation: A subroutine was invoked with an invalid number of group identifiers. The number of group identifiers must be greater than or equal to one.
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. Correct the number of group identifiers, so that it is greater than or equal to one (this number must match the number of group identifiers in the list to be passed to the function).
Error Number: 273
| 274 THIS FUNCTION IS NOT SUPPORTED BY THE WORKSTATION |
Explanation: A subroutine was invoked that is not supported on the specified workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the workstation identifier if it is not correct. See The graPHIGS Programming Interface: Technical Reference or use the appropriate inquiry function, either GPQLTF, GPQMTF or GPQHF, to determine whether the workstation supports the desired function.
Error Number: 274
| 275 SPECIFIED ENTRY CANNOT BE CHANGED |
Explanation: A subroutine was invoked that attempted to change an entry in a table that is not allowed to be changed.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Determine that the index into the table is correct. See The graPHIGS Programming Interface: Subroutine Reference to check which entry is restricted for the failing function.
Error Number: 275
| 276 DEFINITION DATA FORMAT IS NOT SUPPORTED |
Explanation: GPHR or GPMTR was invoked with a data format that is not supported by the specified workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the data format if it is invalid. See The graPHIGS Programming Interface: Technical Reference or use the appropriate inquiry function, either GPQHF or GPQMTF, to determine the allowed data format for the specified workstation.
Error Number: 276
| 277 DEFINITION DATA EXCEEDS THE WORKSTATION TABLE CAPACITY |
Explanation: GPLTR, GPMTR or GPHR was invoked with definition data that is larger than the size of the table for the specified workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Determine that the definition data is correct. See The graPHIGS Programming Interface: Technical Reference or use the appropriate inquiry function GPQLTF, GPQMTF, or GPQHF, to determine the size of the definition data for the specified workstation.
Error Number: 277
| 278 CULL SIZE INDEX < ONE |
Explanation: GPCSR, GPQCSR, GPTEX2, or GPTEX3 was invoked with an invalid cull size index. The cull size index must be greater than or equal to one.
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 cull size index so that it is greater than or equal to one.
Error Number: 278
| 279 CULL SIZE INDEX EXCEEDS THE WORKSTATION TABLE CAPACITY |
Explanation: GPCSR or GPQCSR was invoked with an invalid cull size index. The index exceeds the size of the cull size table in the specified workstation.
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 cull size index. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQCSF to determine the size of the cull table for the specified workstation.
Error Number: 279
| 280 CULL SIZE < ZERO |
Explanation: GPCSR was invoked with an invalid cull size. The cull size must be greater than or equal to zero.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCSR that caused the error. Correct the cull size so that it is greater than or equal to zero.
Error Number: 280
| 281 DEPTH CUE MODE IS INVALID |
Explanation: GPDCR was invoked with a depth cue mode parameter which is incorrectly specified.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDCR that caused the error. Correct the depth queue mode parameter. See The graPHIGS Programming Interface: Subroutine Reference or use the inquiry function GPQDCF for a list of allowable depth cue modes.
Error Number: 281
| 282 COLOR TABLE IDENTIFIER < ONE |
Explanation: GPCRC or GPDLC was invoked with an invalid color table identifier. The color table identifier must be greater than 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 color table identifier.
Error Number: 282
| 283 COLOR TABLE IDENTIFIER ALREADY IS IN USE |
Explanation: GPCRC was invoked with a color table identifier that was previously used.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the color table identifier.
Error Number: 283
| 284 COLOR TABLE IDENTIFIER DOES NOT EXIST |
Explanation: A subroutine was invoked with an invalid color table identifier. The color table identifier does not exist on the workstation.
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 color table identifier parameter. Use the inquiry function GPQCID to obtain a list of color table identifiers that exist on the workstation.
Error Number: 284
| 285 SPECIFIED COLOR MODEL IS NOT SUPPORTED |
Explanation: GPCRC was invoked to create a color table with a color model that is not supported.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the color model parameter.
Error Number: 285
| 286 COLOR TABLE SIZE EXCEEDS THE WORKSTATION MAXIMUM |
Explanation: GPCRC was invoked to create a color table with a color table length greater than the specified workstation maximum table size.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCRC that caused the error. Specify a color table length within the workstation's limitation. Use the inquiry function GPQCCH to determine the maximum table size supported by the workstation.
Error Number: 286
| 287 COLOR TABLE SIZE < ONE |
Explanation: GPCRC was invoked to create a color table with an invalid color table length parameter. The color table length parameter must be specified in log2.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the color table length parameter.
Error Number: 287
| 288 IMAGE INDEX NOT WITHIN WORKSTATION TABLE RANGE |
Explanation: A subroutine was invoked with an invalid image index.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the image index parameter. Use the inquiry function GPQIDF to determine the maximum image index supported by the workstation. Ensure that the image index is not less than one.
Error Number: 288
| 289 SPECIFIED COLOR TABLE CANNOT BE MODIFIED |
Explanation: GPXCR was invoked with a color table identifier for a color table that does not exist on the workstation, or cannot be modified.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPXCR that caused the error. Correct the color table identifier parameter, and determine if the color table can be modified. See The graPHIGS Programming Interface: Technical Reference See also The graPHIGS Programming Interface: Understanding Concepts, or use the inquiry function GPQXCF to determine the characteristics of the specified color table on your workstation.
Error Number: 289
| 290 SPECIFIED IMAGE INDEX IS NOT DEFINED |
Explanation: A subroutine was invoked with an invalid image index parameter.
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 image index parameter, or create the image using GPDFI See The graPHIGS Programming Interface: Subroutine Reference for a parameter description and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing.
Error Number: 290
| 291 SPECIFIED IMAGE CONNECTION TYPE IS NOT SUPPORTED |
Explanation: GPDFI was invoked with an invalid connection type parameter or a connection type parameter that is not supported by the workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDFI that caused the error. Correct the connection type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing. See The graPHIGS Programming Interface: Technical Reference to determine the image connection types supported by the workstation, or use the GPQIDF inquiry function.
Error Number: 291
| 292 NUMBER OF IMAGE BOARDS DOES NOT MATCH THE CONNECTION TYPE |
Explanation: GPDFI was invoked with an invalid number of image boards for the specified connection type parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDFI that caused the error. Either correct the number of image boards parameter for the connection type specified in the connection type parameter, or correct the connection type parameter, if incorrect. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing.
Error Number: 292
| 293 CHARACTERISTICS OF THE SPECIFIED IMAGE BOARDS DO NOT MATCH |
Explanation: GPDFI was invoked specifying image boards that were not created with the same horizontal and vertical size.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDFI that caused the error. Correct the specified list of image boards. The image boards used to define the image must be created with the same horizontal and vertical size. Image boards are created using the GPCRIB subroutine call.
Error Number: 293
| 294 SPECIFIED IMAGE MAPPING METHOD IS NOT SUPPORTED |
Explanation: GPCIM2, GPCIM3, or GPDRI2 was invoked with an invalid image mapping method parameter, or an image mapping method that is not supported by the workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the image mapping parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing. See also The graPHIGS Programming Interface: Technical Reference to determine the image mapping methods supported by the workstation, or use the GPQIMF inquiry function.
Error Number: 294
| 295 PIXEL OPERATION TYPE IS INVALID |
Explanation: GPQPO was invoked with an invalid pixel operation type parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPQPO that caused the error. Correct the pixel operation type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing.
Error Number: 295
| 296 SPECIFIED IMAGE MAPPING DOES NOT EXIST |
Explanation: GPQIMC was invoked with an invalid image mapping identifier.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPQIMC 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. Either correct the image mapping identifier parameter, or create the image mapping using GPCIM2 or GPCIM3 See The graPHIGS Programming Interface: Subroutine Reference for a parameter description and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of image processing.
Error Number: 296
| 297 LINE RENDERING STYLE IS INVALID |
Explanation: GPLNR was invoked with an invalid line rendering style.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocaton of GPLNR that caused the error. Correct the line rendering style. See The graPHIGS Programming Interface: Subroutine Reference for valid rendering styles, or use the inquiry function GPQLNR to determine the line rendering styles supported by the workstation.
Error Number: 297
| 299 FACE LIGHTING METHOD IS INVALID |
Explanation: GPFLM was invoked with an invalid face lighting 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 face lighting method parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values.
Error Number: 299