Chapter 2E. Device-Independent Messages (501-599)

The data length value parameter is less than zero or less than the minimum length required. For example, if the data must contain at least four real values, then the minimum record data length would be 28 bytes (3 fullword integers for the header, followed by 4 reals).

The specified length of the area that the data record is returned to is smaller than the data record size. This condition is returned only in the error indicator parameter of the inquiry call.

The data length parameter is less than zero, or less than the minimum length required.

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. Identify the function causing the error and correct the parameter. Be sure the data-length parameter is greater than or equal to the length defined by the data-record header or zero if no data is required. For input device inquiry, increase the length parameter value and size of the area in which the record is to be returned. If the data record is not required by the application, this error may be ignored.

Error Number: 509

Explanation: GPINVL was invoked with the minimum value of the range greater than the maximum value of the range.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPINVL that caused the error. Correct the valuator range parameters.

Error Number: 511

Explanation: A subroutine was invoked with an invalid method parameter 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 method parameter.

Error Number: 512

Explanation: GPINSK, GPINPK, or GPINST was invoked with the number of the initial values greater than the maximum 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 parameter. See The graPHIGS Programming Interface: Technical Reference or use the inquiry functions, GPQDSK or GPQDST, to determine the maximum number of initial values that are supported.

Error Number: 513

Explanation: GPCRWS or GPOPWS was invoked with an inconsistent workstation type and connection identifier.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the connection identifier and/or the workstation type in one of these places:

• On a GPOPWS or GPCRWS call
• In a nickname definition in the External Defaults File (EDF) or Application Defaults Interface Block.

See The graPHIGS Programming Interface: Technical Reference and The graPHIGS Programming Interface: Writing Applications for information on connection identifiers, workstation types and nicknames.

Error Number: 514

Explanation: GPINVL was invoked with the initial valuator value not between the minimum and maximum values of the valuator range.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPINVL that caused the error. Correct the initial value and/or valuator range.

Error Number: 515

Explanation: GPDCMM was invoked with an invalid scale factor 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 scale factor value.

Error Number: 516

Explanation: GPCR or GPXCR was invoked with the number of indexes less 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 indexes parameter.

Error Number: 517

Explanation: A subroutine was invoked with an invalid request for changes to view zero. View zero is statically defined and unchangeable.

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 index or remove the function call.

Error Number: 518

Explanation: A subroutine was invoked when the current event report was empty.

System Action: The subroutine call in error is ignored.

Programmer Response: GPAWEV must be issued to move an event from the event queue into the current event report. GPGTxx functions empty the current event report.

Error Number: 519

Explanation: A subroutine was invoked that caused more errors than the error queue can hold.

System Action: All errors are lost until room exists on the queue. As errors are reported to the error handler, space becomes available on the error queue to hold additional errors.

Programmer Response: Locate the specific invocation of the subroutine that caused the error. Contact your systems support to assist you in problem determination at this point.

Error Number: 520

Explanation: GPELOG or GPQEMS was invoked with the graPHIGS API not in error state.

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. The application should be modified to use these functions only within the first-level error handler.

Error Number: 521

Explanation: GPVMT2, GPVMT3, or GPXVR was invoked with a matrix that cannot be inverted.

System Action: The matrix is accepted and used normally for output. Since there is no inverse matrix for transforming stroke/locator input from device coordinates to world coordinates, default actions will be taken. The coordinates (0,0,0), will be returned for locator input, and zero points will be returned for stroke input from the corresponding view.

Programmer Response: Check the error log to determine which function caused the error. Verify the usage of a non-invertible matrix. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of view matrix and stroke/locator input.

Error Number: 522

Explanation: GPASF was invoked with the number of attribute source flags (ASF) parameters less than zero.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPASF that caused the error. Correct the parameter.

Error Number: 523

Explanation: GPQEDA or GPQEHA was invoked with a starting element position that is larger than the number of elements in the structure.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Check that the number of elements in the specified structure is larger than the specified starting element position (GPQSTS can be used for this). Change the starting element position so that it is less than the last element in the structure.

Error Number: 524

Explanation: Only inquiry and error handling functions are valid while in error state.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of the function that caused the error. Correct the error by eliminating the call. Within the first-level error handler, eliminate all calls to graPHIGS API subroutines which are not error handling or inquiry functions

Error Number: 525

Explanation: A subroutine was invoked and data was found that cannot be translated to fit the format expected by these functions. The values returned in the output parameters are unpredictable.

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. These inquiries are part of the compatibility subroutines that allow existing programs to continue to run unaltered. Applications that have been changed to make use of the new graPHIGS API functionality should use the GPQED, GPQEMS, GPQCVR, or GPQRVR subroutines (respectively) in order to make use of the information created.

Error Number: 526

Explanation: GPCCV, GPES, GPQMDS, or GPRDFB was invoked and the target workstation does not support the specified escape.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of the function that caused the error. Use the inquiry function GPQES to determine the supported escapes for a specified workstation.

Error Number: 527

Explanation: GPELS was invoked with an invalid search direction.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPELS that caused the error. Correct the search direction parameter.

Error Number: 528

Explanation: GPELS was invoked with a negative inclusion or exclusion list length.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPELS that caused the error. Check and correct the list length parameters of the GPELS element search structure function.

Error Number: 529

Explanation: GPADCN or GPRCN was invoked with the number of class names less than 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 number of class names parameter.

Error Number: 530

Explanation: GPHLF, GPIVF, or GPPKF, was invoked with an invalid filter list length parameter. The value of the filter list length must be equal to or greater than 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 filter list length parameter.

Error Number: 531

Explanation: GPAWEV was called with the timeout value greater than the maximum supported, which is approximately 15 hours.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Decrease the timeout interval, so that it is less than the maximum timeout value.

Error Number: 532

Explanation: A subroutine inquiry function has been invoked, and the amount of information to be returned exceeds the length of the output area provided by the application. This error is only returned as an error indicator from an inquiry function. It is never placed on the error queue. This may not be considered an error if the information is from an unknown length list.

System Action: The information is truncated to the size of the output area.

Programmer Response: 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 error can be corrected by:

• Increasing the output area size
• Requesting the rest of the information through additional inquiry calls with different start locations.

Error Number: 533

Explanation: A subroutine function was invoked with an invalid type parameter.

System Action: The subroutine call in error is ignored.

Programmer Response: Determine which function caused the error. Correct the type value. See The graPHIGS Programming Interface: Subroutine Reference for valid values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of the type parameter.

Error Number: 534

Explanation: GPQE, GPQED, or GPQEHD was invoked with the element pointer at zero There is no structure element at this location.

System Action: No element content information is returned.

Programmer Response: Set the element pointer at a valid structure element before invoking the failing function. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of the element pointer.

Error Number: 535

Explanation: GPQNS, GPQRCT, or GPQWTO was invoked and the amount of information to be returned exceeds the length of the output area provided by the application. This error is only returned as an error indicator from an inquiry function.

System Action: The length of the output parameter area that is required is returned, but the information is not returned.

Programmer Response: This error can be returned only on an inquiry function. Therefore, it can only be detected by checking the error indicator parameter after invoking the inquiry function. The inquiry may be reissued with an output area large enough to contain the required information.

Error Number: 536

Explanation: GPPAR, GPPXL2, or GPPXL3 was invoked with a subarray that exceeds the input array dimensions.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the array or subarray specification to conform to input array dimensions.

Error Number: 537

Explanation: A subroutine inquiry function was invoked that returns a subset of a list of values. The first location to be returned within the list was specified as less than zero.

System Action: The subroutine call in error is ignored.

Programmer Response: This error can be returned only on an inquiry function. Therefore, it can only be detected by checking the error indicator parameter after invoking the inquiry function. Correct the start value to be greater than or equal to one.

Error Number: 538

Explanation: A subroutine inquiry function was invoked that returns a subset of a list of values. The number of values from the list to be returned was specified as less than zero.

System Action: The subroutine call in error is ignored.

Programmer Response: 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 requested number to a value that is greater than or equal to zero.

Error Number: 539

Explanation: GPQEHD, GPQEHA, GPQEDA or GPQED inquiry function was invoked, but the number of items requested is less than one. The number of items must be greater than or equal to one.

System Action: The subroutine call in error is ignored.

Programmer Response: 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 entries or number of elements parameter.

Error Number: 540

Explanation: A subroutine was invoked with a character set identifier less than zero or greater than 255, or it is an identifier reserved for IBM.

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 character set identifier parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid values.

Error Number: 542

Explanation: A subroutine was invoked with an invalid list length. The first location to be returned within the list is specified as greater than the number of values in the list.

System Action: The list length output parameter is returned and is valid, but no members of the list are returned.

Programmer Response: This error can be detected only by checking the error indicator parameter after calling the inquiry function. Either decrease the start parameter, or ignore this error if the list is not required. The list length may be used to adjust the start parameter for the future calls.

Error Number: 543

Explanation: GPQCR, or GPQXCR was invoked with the start value less than zero. Color tables begin at entry zero.

System Action: The subroutine call in error is ignored.

Programmer Response: 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. Check the start value parameter and correct if necessary.

Error Number: 544

Explanation: GPVCH, GPXVCH, or GPXVR was invoked with an invalid view border.

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 border indicator parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of view borders.

Error Number: 547

Explanation: A subroutine was invoked for a workstation description table that is either unavailable on the system, or the system service failed when it tried to access the table.

System Action: The subroutine call in error is ignored.

Programmer Response: 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. Be sure the specified workstation type is supported. Check with the system programmer to be sure that the specified workstation type has been installed.

Error Number: 548

Explanation: GPPXL2 or GPPXL3 was invoked with an invalid pixel pack factor.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the pixel pack factor. See The graPHIGS Programming Interface: Subroutine Reference for valid parameters values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of pixel pack factor.

Error Number: 549

Explanation: GPICS was invoked with a character set identifier not supported by the workstation.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPICS that caused the error. Correct the parameter in error. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQAIS to determine the actual input character sets that are supported.

Error Number: 550

Explanation: GPQCR or GPQXCR was invoked with the start value parameter exceeding the size of the color table.

System Action: The subroutine call in error is ignored.

Programmer Response: 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 start parameter. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQLW to determine the actual size of the color table.

Error Number: 551

Explanation: GPRAS, GPRDS, GPQPDS, or GPQPAS was invoked with an invalid path order.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Check and correct the path order parameter of the associated structure inquiry function.

Error Number: 552

Explanation: GPDAFO was invoked with a character set identifier of the primary character set. The primary character set cannot be deactivated.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPDAFO that caused the error. Eliminate all invocations to GPDAFO with a primary character set identifier. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQPCS to determine the primary character set.

Error Number: 553

Explanation: GPPKAP was invoked with the pick aperture size less than zero.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPPKAP that caused the error. Correct the pick aperture size. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of pick aperture.

Error Number: 554

Explanation: GPDPL2 or GPDPL3 was invoked with an invalid move/draw indicator in the move/draw array.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the move/draw indicator. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts, for an explanation of the disjoint polyline.

Error Number: 555

Explanation: A subroutine was invoked, creating a structure element that exceeded the maximum size allowed. Total element size exceeds the maximum allowed by the graPHIGS API The maximum size structure element that may be defined is 64k bytes.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of the subroutine that caused the error. Correct the structure element size. See The graPHIGS Programming Interface: Technical Reference for an explanation of the format and size of each structure element.

Error Number: 556

Explanation: A subroutine was invoked that has a point list parameter. The width of the point list parameter is less than the minimum allowed. The width parameter must be greater than or equal to 2 for 2D functions and greater than or equal to 3 for 3D functions.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of the function that caused the error. Correct the parameter in error. See The graPHIGS Programming Interface: Understanding Concepts, for an explanation of point lists.

Error Number: 557

Explanation: GPRAS, GPRDS, GPQPDS, or GPQPAS was invoked with a negative path depth.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Check and correct the path depth parameter of the associated structure inquiry function.

Error Number: 558

Explanation: GPACFO was invoked after the maximum number of fonts had already been activated.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPACFO that caused the error. Deactivate other fonts to make room in the font pool preceding this invocation. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQFP to determine the supported font pool size.

Error Number: 559

Explanation: GPQFAR or GPQFCH was invoked, and the system could not find the requested character set/font combination.

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. Specify an available character set/font combination.

Error Number: 560

Explanation: GPQGFC was invoked with character set and font identifiers that do not map to a currently active font.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPQGFC 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 character set and font identifier parameters.

Error Number: 561

Explanation: GPQAFC or GPQXAF inquiry function was invoked with character set and font identifiers which do not map to an available annotation font.

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 character set and font identifier parameters. See The graPHIGS Programming Interface: Subroutine Reference for a list of available annotation fonts.

Error Number: 562

Explanation: GPACFO or GPQGFC was invoked with character set and font identifiers which do not map to an available geometric font.

System Action: The function is ignored.

Programmer Response: Check the error log or error indicator parameter, as appropriate, to determine which function caused the error. Correct the character set and font identifier parameters. See The graPHIGS Programming Interface: Subroutine Reference for a list of available geometric fonts.

Error Number: 563

Explanation: GPQFAR was invoked, and the text string contains a character code that is undefined in the given character set.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPQFAR 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 may not be an error in all cases. For example, this function can be used to determine the set of supported character codes by invoking it once for each value in the range 0 to 255. Before invoking this function for codes 0 to 255, be sure to activate the character set/font.

Error Number: 564

Explanation: GPIT was issued with a trigger qualifier that does not exist for the corresponding input device.

A potential error is being tolerated. In early releases of AIX X-Windows, it was not possible to determine the number of mouse buttons available. The trigger ranges were for the maximum possible range of buttons. In later releases, it became possible to determine the number of mouse buttons available, so calls to GPIT that specify invalid trigger values (based on the new information) are tolerated for compatibility.

System Action: The invalid trigger qualifier is ignored. Any valid trigger qualifiers specified by GPIT are used in setting the specified input device trigger.

Programmer Response: Check the error log to determine which GPIT function caused the error. Correct the parameter and use GPQIT to determine which trigger qualifiers are present.

Error Number: 565

Explanation: Either GPEPPK or GPEPPG (with pick identifier search flag set to WRAP) was invoked with a nonexistent pick identifier, or GPEPPG (with pick identifier search flag set to NOWRAP) was invoked with a pick identifier that did not exist between the current element pointer and the end of the structure.

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 the specified pick identifier exists.

Error Number: 566

Explanation: GPIT or GPBKAC was called with a trigger type value that either does not exist, or is not supported by the corresponding input device for GPIT, or workstation for GPBKAC

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 and use the appropriate inquiry, GPQAIT or GPQABK, to determine which trigger types are present.

Error Number: 567

Explanation: GPBKAC or GPIT was called with a trigger qualifier that either does not exist, or is not supported by the corresponding input device for GPIT, or workstation for GPBKAC

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 and use the appropriate inquiry, GPQAIT, to determine which trigger qualifiers are present.

Error Number: 568

Explanation: GPIT, GPQAIT, or GPQIT was invoked for an input device that does not support programmable triggers.

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. For GPIT, correct the input device parameters. Use GPQIT to determine which input devices support programmable triggers on a given workstation.

Error Number: 569

Explanation: GPIT, or GPQDIT was called with a trigger list identifier that does not exist.

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 GPQNST to determine the number of secondary triggers for the specified device.

Error Number: 570

Explanation: A subroutine was called for a workstation that either does not support this function, or does not possess distributed storage, or GPQAFC or GPQXAF were called for a workstation type of 'GDF' or 'CGM' Since the 'GDF' or 'CGM' plot file support cannot determine, at file creation time, the characteristics of the plotter to be used, this information cannot be returned.

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.

Error Number: 571

Explanation: GPBKAC, GPQABK, or GPQBK was called for a workstation that does not allow the break action to be modified.

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 GPQBK to determine if the break action is programmable for the given workstation.

Error Number: 572

Explanation: A trigger descriptor that was passed to GPIT had an invalid range of trigger qualifiers.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPIT that caused the error. Correct the parameter list passed, so that all high-trigger qualifiers are greater than or equal to the corresponding low-trigger qualifiers.

Error Number: 574

Explanation: GPIT was invoked with an invalid specified number of entries in the trigger list. The number of entries in the trigger list must be equal to or greater than zero.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPIT that caused the error. Correct the parameters on the call, or refer to The graPHIGS Programming Interface: Understanding Concepts, for more information.

Error Number: 575

Explanation: GPIT was called for the primary trigger list, which must have at least one entry.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPIT that caused the error. Correct the parameters on the call, or refer to The graPHIGS Programming Interface: Understanding Concepts, for more information on primary trigger lists.

Error Number: 576

Explanation: A subroutine was invoked with an invalid buffer-length parameter. The buffer-length parameter must be equal to or greater than 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 parameter.

Error Number: 577

Explanation: GPINST or GPINSK was invoked with the string input buffer size value greater than the maximum buffer size for the device.

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. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQDST to determine the maximum string buffer length.

Error Number: 578

Explanation: GPINST or GPINSK was invoked with an invalid initial position parameter. The initial position parameter must be equal to or 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 initial position parameter.

Error Number: 579

Explanation: GPINST or GPINSK was invoked with the initial position value greater than the buffer size for the device.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the initial position parameter.

Error Number: 580

Explanation: GPCRWS or GPOPWS was invoked with an invalid number of View Table entries. The PROCOPT option VWTBLSZ specified an invalid number of View Table entries for this workstation. Either the VWTBLSZ option was too large or less than two. All workstations must have at least one definable View Table entry. Therefore, VWTBLSZ must be greater than or equal to two (view 0 plus one definable entry).

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the VWTBLSZ option as set in the External Defaults File (EDF), Application Defaults Interface Block, or GPCRWS call, so that it specifies a valid number of view table entries. The limits for the view table size are device-dependent. See The graPHIGS Programming Interface: Technical Reference for the limits for the view table size.

Error Number: 581

Explanation: GPCR2, GPCRA2, or GPSPH was invoked with an invalid specified radius value. The specified radius value must be equal to or greater than 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 radius parameter.

Error Number: 582

Explanation: GPCRWS or GPOPWS was invoked with an invalid number of locator or string devices. The PROCOPT option LOCDEVS or STRDEVS specified an invalid number of locator or string devices for this 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 option for the incorrect entry as set in the External Defaults File (EDF), Application Defaults Interface Block, or GPCRWS call, so that it specifies a valid number of input devices. The number of input devices is device-dependent. See The graPHIGS Programming Interface: Technical Reference

Error Number: 583

Explanation: GPPLET was invoked with an invalid polyline end type value. The polyline end type value must be equal to or greater than one.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPPLET that caused the error. Correct the end type parameter value. See The graPHIGS Programming Interface: Technical Reference to determine valid end type values.

Error Number: 584

Explanation: GPCRWS or GPOPWS was invoked with an invalid KEYBOARD PROCOPT value. The KEYBOARD PROCOPT contains a value that is not supported on the given 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 KEYBOARD option as set in the External Defaults File (EDF), Application Defaults Interface Block, or GPCRWS call, to specify a value that is supported by your workstation. See The graPHIGS Programming Interface: Technical Reference for lists of supported KEYBOARDS.

Error Number: 585

Explanation: GPCRWS or GPOPWS was invoked with an invalid display model value. The DISPLMOD PROCOPT contains an invalid 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 DISPLMOD option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, to specify a value that is supported by your workstation. See The graPHIGS Programming Interface: Technical Reference for lists of DISPLMODs.

Error Number: 586

Explanation: GPCRWS or GPOPWS was invoked with an invalid echo method. The ECHOMETH PROCOPT contains an invalid 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 ECHOMETH option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, to specify a value that is supported in the given workstation. See The graPHIGS Programming Interface: Technical Reference for list of supported ECHOMETHs.

Error Number: 587

Explanation: GPCRWS or GPOPWS was invoked with an invalid value for the frame buffer control (FBUFFER) PROCOPT.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the frame buffer control option. See The graPHIGS Programming Interface: Technical Reference for information on the FBUFFER PROCOPT.

Error Number: 588

Explanation: GPXVCH was invoked with an invalid specified number of characteristic identifiers value. The specified number of characteristics must be equal to or greater than one.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPXVCH that caused the error. Correct the parameter value.

Error Number: 591

Explanation: GPXVCH was invoked with an invalid view characteristics identifier parameter value. A characteristic identifier is not one of the valid identifiers.

System Action: The subroutine call in error is ignored.

Programmer Response: Locate the specific invocation of GPXCVH that caused the error. Correct the parameter value.

Error Number: 592

Explanation: An error has been detected by an internal graPHIGS API communication routine. If the major code is five or seven, then an I/O error has occurred and may indicate a hardware problem. Use the following table for a more detailed explanation and appropriate programmer response for errors with a major code of five or seven.

System Action: None.

Programmer Response: If the major code is five or seven, see the above table. If the major code is other than five or seven, inform a service representative of the error number, major code, minor code and the conditions surrounding the error's occurrence.

Error Number: 593

Explanation: An API subroutine was called with more data than can be fit into the shell/nucleus connection buffer.

System Action: The function is ignored.

Programmer Response: Reduce the amount of data supplied to the API function in error, or increase the connection buffer size, using the defaults file or PROCOPT data.

Error Number: 594

Explanation: GPIT was invoked to set a secondary trigger to type -1.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Either eliminate the -1 type, or else change the trigger list id to primary (0). See The graPHIGS Programming Interface: Subroutine Reference for valid values.

Error Number: 595

Explanation: GPCRWS or GPOPWS was invoked with an invalid PLBTES option. The PLBTES PROCOPT specifies an invalid number of polylin bundle type entries.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the PLBTES option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, so that it specifies a valid number of bundle table entries. The limits for the valid number of bundle table entries are device-dependent. See The graPHIGS Programming Interface: Understanding Concepts, for details about these limits.

Error Number: 596

Explanation: GPCRWS or GPOPWS was invoked with an invalid PMBTES option. The PMBTES PROCOPT specifies an invalid number of polymarker bundle type entries.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the PMBTES option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, so that it specifies a valid number of bundle table entries. The limits for the valid number of bundle table entries are device-dependent. See The graPHIGS Programming Interface: Understanding Concepts, for details about these limits.

Error Number: 597

Explanation: GPCRWS or GPOPWS was invoked with an invalid TXBTES option. The TXBTES PROCOPT specifies an invalid number of text bundle type entries.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the TXBTES option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, so that it specifies a valid number of bundle table entries. The limits for the valid number of bundle table entries are device-dependent. See The graPHIGS Programming Interface: Understanding Concepts, for details about these limits.

Error Number: 598

Explanation: GPCRWS or GPOPWS was invoked with an invalid EBTES option. The EBTES PROCOPT specifies an invalid number of edge bundle type entries.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the error log to determine which function caused the error. Correct the EBTES option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, so that it specifies a valid number of bundle table entries. The limits for the valid number of bundle table entries are device-dependent. See The graPHIGS Programming Interface: Understanding Concepts, for details about these limits.

Error Number: 599