| 600 PROCOPT SPECIFIES INVALID NUMBER OF DEPTH CUE TABLE ENTRIES |
Explanation: GPCRWS or GPOPWS was invoked with an invalid DCTES option. The DCTES PROCOPT specifies an invalid number of depth cue table 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 DCTES 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 depth cue table entries. The limits for the valid number of depth cue table entries are device-dependent. See The graPHIGS Programming Interface: Understanding Concepts, for details about these limits.
Error Number: 600
| 601 PROCOPT SPECIFIES INVALID NUMBER OF LIGHT SOURCE TABLE ENTRIES |
Explanation: GPCRWS or GPOPWS was invoked with an invalid LSTES option. The LSTES PROCOPT specifies an invalid number of light source table 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 LSTES 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 light source table entries. The limits for the valid number of light source table entries are device-dependent. See The graPHIGS Programming Interface: Understanding Concepts, for details about these limits.
Error Number: 601
| 602 PROCOPT SPECIFIES INVALID NUMBER OF INTERIOR TABLE ENTRIES |
Explanation: GPCRWS or GPOPWS was invoked with an invalid IBTES option. The IBTES PROCOPT specifies an invalid number of interior bundle table 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 IBTES 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 interior 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: 602
| 603 INTERNAL COMMUNICATIONS PROTOCOL ERROR |
Explanation: An error has occurred involving a communication protocol internal to the graPHIGS API
System Action: The subroutine call in error is ignored.
Programmer Response: This error can be returned only on an inquiry subroutine in the error indicator parameter. This is probably not an application problem. Document the series of instructions that caused the message to be issued and report the problem to IBM.
Error Number: 603
| 604 NUCLEUS n1 NOT STARTED OR NOT RESPONDING |
Explanation: One of the following conditions exists:
System Action: The command is ignored.
Programmer Response: Make sure that you have a remote nucleus started with the specified identifier. See The graPHIGS Programming Interface: Technical Reference for a complete explanation of the gPhost, gPq, gPinit and gPterm commands, and the graPHIGS API gateway daemon.
Error Number: 604
| 605 gP IS UNABLE TO START A REMOTE NUCLEUS |
Explanation: A remote nucleus was started either explicitly or via gPinit The nucleus was unable to initialize. This error occurs because the system found another nucleus that already exists with the same identifier as the one being used to start this nucleus.
System Action: The command is ignored.
Programmer Response: Either start this nucleus with a different nucleus identifier or terminate the nucleus that already exists and reissue the command. See The graPHIGS Programming Interface: Technical Reference for a complete explanation of remote nuclei.
Error Number: 605
| 606 ILLEGAL COMBINATION OF ISO PHIGS AND GPXXX CALLS |
Explanation: Either a GPxxx function was invoked to inquire information which is only defined by ISO PHIGS, or else an ISO PHIGS function was invoked to inquire information only defined in a GPxxx call.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Change the function to either an ISO PHIGS function or a GPxxx function as appropriate.
Error Number: 606
| 607 NUCLEUS IS DOWN LEVEL. VERSION @A1, RELEASE @A2.@A3 IS REQUIRED |
Explanation: A function has been invoked which requires a matching level of nucleus code.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Install the required level of nucleus code or remove the function.
Error Number: 607
| 608 FRONT PLANE DISTANCE = BACK PLANE DISTANCE WHEN Z-EXTENT NON-ZERO |
Explanation: The front plane distance is equal to the back plane distance, but the viewport z-extent is not zero. The front plane distance may equal the back plane distance only when the viewport z-extent is zero.
System Action: If the error is generated by GPEVM3, the subroutine call in error is ignored. If the error is generated during traversal, the view mapping matrix defaults to the identity matrix.
Programmer Response: Either set the viewport z-extent to zero, or set the back (far) plane distance less than the front (near) plane distance.
Error Number: 608
| 609 ERROR LOGGING PARAMETERS DO NOT MATCH CURRENT ERROR REPORT |
Explanation: PERLOG was invoked with either the function identifier parameter or the error number parameter not matching that of the current error report.
System Action: The subroutine call in error is ignored.
Programmer Response: Invoke PERLOG from within a user-supplied Error Handling function, passing the same parameters as received by the Error Handling function.
Error Number: 609
| 610 PROJECTION REFERENCE POINT BETWEEN NEAR AND FAR PLANES |
Explanation: GPEVM3 was invoked with the projection reference point between the near and far clipping planes.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPEVM3 that caused the error. Correct the projection reference point and/or the near and far plane distances.
Error Number: 610
| 612 TSL STACK OVERFLOW HAS OCCURRED |
Explanation: GPPSTS was invoked and there is no more room to save another TSL. The network beyond this maximum depth is ignored.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Issue GPPTS (Pop TSL) before GPPSTS so that subsequent TSLs will be pushed on the stack.
Error Number: 612
| 613 TSL STACK UNDERFLOW HAS OCCURRED |
Explanation: GPPTS was invoked and there was no TSL saved on the stack to pop.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Check the code sequence of calls that are using GPPTS to correct this issuance of GPPTS
Error Number: 613
| 614 UNKNOWN ELEMENT FOUND IN STRUCTURE n1 |
Explanation: A subroutine was invoked to move structure data from a source structure store or archive file to a destination structure store or archive file. The data environment of the source resource was different from that of the destination resource. During the structure data transfer, the structure elements went through a data conversion, and an element of unknown type was found during the check for data translation.
This situation can occur only when there is a mismatch in graPHIGS API release levels between graPHIGS API resources (either a shell/nucleus mismatch or an archive file/nucleus mismatch).
System Action: Structures that were transferred from the source structure store or archive file to the destination structure store or archive file before the error condition occurred are left in the destination resource. The structure where the error was found is emptied of elements and no further structure data is transferred between the source resource and the destination resource.
Programmer Response: Structure stores or archive files that contain structure elements should not be used by graPHIGS API shells or nuclei that are at a lower release level. This is true especially if the data environment is different (e.g., ASCII vs. EBCDIC, IEEE floating point vs. System/390 floating point, etc.).
Error Number: 614
| 616 NO DEVICE ADDRESSES AVAILABLE |
Explanation: A request was made, using the chgPcon command, to add a runtime connection profile entry. However, no device addresses were available.
System Action: The request is ignored.
Programmer Response: This condition may normally occur if all available device addresses are DEFINED. Use the lsgPcon command with the -s option to determine the state of device addresses in use by the graPHIGS API gateway daemon. If there is an inconsistency between this information and what is expected, contact the administrator of the graPHIGS API Gateway.
Error Number: 616
| 617 DEVICE ADDRESS xxx ALREADY ALLOCATED OR UNAVAILABLE |
Explanation: A request was made, using the chgPcon command with the -a option, to allocate a specific device address, but the specified address is not available.
System Action: The request is ignored.
Programmer Response: Verify that the specified address is correct. If it appears to be correct, use the lsgPcon command with the -s option to determine the state of the device address in use by the graPHIGS API gateway daemon. If there is an inconsistency between this information and what is expected, contact the administrator of the graPHIGS API gateway.
Error Number: 617
| 618 gPgated I/O ERROR errno, DEVICE ADDRESS xxx, COMMAND xxx |
Explanation: An error was encountered on the communication path between the specified device address and the target remote graPHIGS API nucleus. errno is the AIX system error number.
System Action: The error is logged in the graPHIGS API gateway daemon's transaction file.
Programmer Response: Use the AIX panel20 command to determine the error condition, or contact the administrator of the graPHIGS API gateway.
Error Number: 618
| 619 RESET RECEIVED ON DEVICE ADDRESS xxx |
Explanation: One of the following occurred:
System Action: The error is logged in the graPHIGS API gateway daemon's transaction file.
Programmer Response: Use the AIX panel20 command to determine the error condition, or contact the administrator of the graPHIGS Gateway.
Error Number: 619
| 620 NO CONNECTION PROFILE ENTRY FOR NUCLEUS hostname:nucid |
Explanation: A request was made, using the chgPcon command with the -d option or the lsgPcon command with the -q option, to delete a runtime connection profile entry. However, no such entry exists.
System Action: The request is ignored.
Programmer Response: Verify that the parameters specified on the chgPcon command are correct. If they appear to be correct, use the lsgPcon command with the -s option to determine the state of the device addresses in use by the graPHIGS API gateway daemon. If there is an inconsistency between this information and what is expected, contact the administrator of the graPHIGS API Gateway.
Error Number: 620
| 621 INVALID OPTION |
Explanation: The gPafut utility was used and was passed an invalid or incomplete option or parameter.
System Action: The utility is terminated.
Programmer Response: Run the utility again with valid parameters. See The graPHIGS Programming Interface: Technical Reference for information on valid parameters for the gPafut utility.
Error Number: 621
| 622 NO FUNCTION SPECIFIED |
Explanation: The gPafut utility was used and no function parameter was given.
System Action: The utility is terminated.
Programmer Response: Run the utility again with valid parameters. See The graPHIGS Programming Interface: Technical Reference for information on valid parameters for the gPafut utility.
Error Number: 622
| 623 SUBARGUMENT MISSING |
Explanation: The gPafut utility was used, and a function or option parameter was specified. However, a required parameter for the function or option was not given.
System Action: The utility is terminated.
Programmer Response: Run the utility again with valid parameters. See The graPHIGS Programming Interface: Technical Reference for information on valid parameters for the gPafut utility.
Error Number: 623
| 624 CONVERSION TYPE IS INVALID |
Explanation: GPCCV was invoked with an invalid conversion type value in the ctype parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPCCV that caused the error. Correct the conversion type value in the ctype parameter. See The graPHIGS Programming Interface: Subroutine Reference for more information on converting coordinate values.
Error Number: 624
| 625 POINT TYPE IS INVALID |
Explanation: GPCCV was invoked with an invalid point type 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 point type value. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 625
| 626 NO CONNECTION PROFILE ENTRIES EXIST |
Explanation: A request was made, using the lsgPcon command with the -Q option, to inquire runtime connection profile entries. However, no entries exist.
System Action: The request is ignored.
Programmer Response: Verify that the parameters specified on the lsgPcon command are correct. If they appear to be correct, then if there is an inconsistency between this information and what is expected, contact the administrator of the graPHIGS API Gateway.
Error Number: 626
| 627 NUMBER OF HALF-SPACES < ZERO |
Explanation: GPMCV2 or GPMCV3 was invoked with an invalid number of half-spaces. The specified number of half-spaces must be >= 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 parameter.
Error Number: 627
| 628 OPERATOR IS INVALID |
Explanation: GPMCV2 or GPMCV3 was invoked with an invalid modeling clipping operator.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Correct the modeling clipping operator value. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 628
| 629 BLENDING FUNCTION IS INVALID |
Explanation: GPBBLF or GPBLF was invoked with an invalid blending function 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 blending function value. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 629
| 630 DATA MAPPING INDEX < ZERO |
Explanation: GPDMI, GPBDMI, GPDMR or GPQDMR was invoked with an invalid data mapping index parameter. The specified data mapping index must be >= zero, except for GPDMR where it must be >=1.
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 mapping index parameter.
Error Number: 630
| 631 FILTERING METHOD IS INVALID |
Explanation: GPDFM or GPBDFM was invoked with an invalid filtering method 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 filtering method value. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 631
| 632 BOUNDING METHOD IS INVALID |
Explanation: GPDFM or GPBDFM was invoked with an invalid bounding method 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 bounding method value. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 632
| 633 MATRIX VALUE IS INVALID |
Explanation: GPDM2 or GPBDM2 was invoked with an invalid matrix 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 matrix. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 633
| 634 DATA MAPPING COLOR TYPE NOT SUPPORTED |
Explanation: GPDMR was invoked with an invalid data mapping color type parameter, or a data mapping color type that is not supported by the workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDMR that caused the error. Correct the data mapping color type parameter. See The graPHIGS Programming Interface: Subroutine Reference for valid parameter values and The graPHIGS Programming Interface: Understanding Concepts for an explanation of data mapping.
Error Number: 634
| 635 DATA ORGANIZATION FORMAT IS INVALID |
Explanation: GPDMR was invoked with an invalid data organization format parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDMR that caused the error. Correct the data organization format parameter. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 635
| 636 FULLWORDS OF VERTEX DATA EXCEEDS MAXIMUM OF 255 |
Explanation: GPPGD2, GPPGD3, GPPLD3, GPTS3 or GPQM3 was invoked with more than 255 fullwords of data per vertex.
System Action: The subroutine call in error is ignored.
Programmer Response: Check the error log to determine which function caused the error. Decrease the amount of data per vertex to 255 fullwords or less.
Error Number: 636
| 637 DATA LIST INDEX IS INVALID |
Explanation: GPDMR was invoked with an invalid data list index.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDMR that caused the error. Correct the data mapping method parameter to include a valid data list index. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 637
| 638 COLOR DATA LENGTHS PARAMETER IS INVALID |
Explanation: GPDMR was invoked with an invalid color data lengths parameter.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPDMR that caused the error. Correct the color data lengths parameter. See the The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 638
| 639 SPECIFIED ALPHA VALUE IS INVALID |
Explanation: GPXVR was invoked with an invalid alpha value parameter. Alpha must be 0 <= value <= 255.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPXVR that caused the error. Correct the alpha value parameter. See The graPHIGS Programming Interface: Subroutine Reference for more information.
Error Number: 639
| 647 UNICODE IS NOT SUPPORTED ON THE SPECIFIED WORKSTATION |
Explanation: GPACFO was invoked with the Unicode character set identifier which is not supported by the specified workstation.
System Action: The subroutine call in error is ignored.
Programmer Response: Locate the specific invocation of GPACFO that caused the error. See The graPHIGS Programming Interface: Technical Reference or use the inquiry function GPQWDT to determine if the specified workstation supports Unicode.
Error Number: 647
| 648 PROCOPT SPECIFIES AN INVALID DISPLAY WIDTH AND/OR HEIGHT |
Explanation: GPCRWS or GPOPWS was invoked with an invalid display width and/or height. The DCUNITS or DCMETERS PROCOPT contains a value 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 DCUNITS or DCMETERS option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, so that it specifies a valid display width and height. See The graPHIGS Programming Interface: Technical Reference for details.
Error Number: 648
| 649 PROCOPT SPECIFIES AN INVALID IMAGE OUTPUT FORMAT |
Explanation: GPCRWS or GPOPWS was invoked with an invalid image output format. The IMAGEFMT PROCOPT contains a value 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 IMAGEFMT option as set in the External Defaults File (EDF), or Application Defaults Interface Block (ADIB), or GPCRWS call, so that it specifies a valid image output format. See The graPHIGS Programming Interface: Technical Reference for more details.
Error Number: 649
| 650 PROCOPT SPECIFIES AN INVALID HLHSR COORDINATE SYSTEM |
Explanation: GPCRWS or GPOPWS was invoked with an invalid HLHSR coordinate system. The PNTHLHSR PROCOPT contains a value 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 PNTHLHSR option as set in the External Defaults File (EDF), Application Defaults Interface Block (ADIB), or GPCRWS call, so that it specifies a valid HLHSR coordinate system. See The graPHIGS Programming Interface: Technical Reference for more details.
Error Number: 650