[ Previous | Next | Contents | Glossary | Home | Search ]
The graPHIGS Programming Interface: Messages and Codes

Chapter 3. System Service Messages (1000-1399)

1003       INCORRECT NUMBER OF ARGUMENTS (=0) ON REENTRANT CALL

Explanation: An Application Anchor Block (AAB), required for all calls to the graPHIGS API through the reentrant interface, was absent.

System Action: The subroutine call in error is ignored.

Programmer Response: Correct the call so that the required arguments are present.

Error Number: 1003

1004       INCORRECT NUMBER OF ARGUMENTS (=0) ON SPI CALL

Explanation: Both an Application Anchor Block (AAB) and a function request code are required for any call to the graPHIGS API through the system programmer interface (SPI). Both were missing.

System Action: The subroutine call in error is ignored.

Programmer Response: Correct the call so that the required arguments are present.

Error Number: 1004

1005       INCORRECT NUMBER OF ARGUMENTS (=1) ON SPI CALL

Explanation: Both an Application Anchor Block (AAB) and a function request code are required for any call to the graPHIGS API through the system programmer interface (SPI). One was missing.

System Action: The subroutine call in error is ignored.

Programmer Response: Correct the call so that the required arguments are present.

Error Number: 1005

1006       AMODE (31) APPLICATION CALL BUT graPHIGS INITIALIZED IN AMODE (24)

Explanation: An application executing in 31-bit addressing mode called the graPHIGS API This call is not an initialization call GPOPPH The graPHIGS API is initialized in 24-bit mode and cannot process calls made in 31-bit mode.

System Action: The subroutine call in error is ignored.

Programmer Response: Contact your system programmer to ensure that the GDDM/graPHIGS API is properly installed. If it is properly installed, change your application to ensure that the call to GPOPPH is made in 31-bit mode (if any part of the application uses 31-bit mode).

Error Number: 1006

1007       INCORRECT ARGUMENTS

Explanation: The second parameter on the GPOPPH function is a zero and not a pointer to a zero.

System Action: The subroutine call in error is ignored.

Programmer Response: Review the GPOPPH invocation in your application and be sure the second parameter is a zero. If your program is written in C, check to see that all the graPHIGS API calls are in uppercase.

Error Number: 1007

1008       INSUFFICIENT STORAGE FOR INITIALIZATION

Explanation: The system was unable to allocate sufficient storage to initialize the graPHIGS API

System Action: The subroutine call in error is ignored.

Programmer Response: The user exceeded the system imposed maximum for memory allocation. Use the "ulimit" system call for changing this maximum. See AIX Operating System Technical Reference, for more information.

Error Number: 1008

1009       UNABLE TO ALLOCATE STORAGE POOLS

Explanation: The system was unable to build the required graPHIGS API buffer pools.

System Action: The subroutine call in error is ignored.

Programmer Response: The user exceeded the system imposed maximum for memory allocation. Use the "ulimit" system call for changing this maximum. See AIX Operating System Technical Reference, SV21-8009, for more information.

Error Number: 1009

1010       UNABLE TO CREATE CHILD PROCESS

Explanation: The FORK system call failed.

System Action: The subroutine call in error is ignored.

Programmer Response: The user exceeded the system imposed maximum for processes. Reduce the number of active processes and start the application again.

Error Number: 1010

1011       PERSONAL graPHIGS API NOT INSTALLED PROPERLY

Explanation: A required part of the Personal graPHIGS API was not found.

System Action: The subroutine call in error is ignored.

Programmer Response: Check the installation of the Personal graPHIGS API.

Error Number: 1011

1051       DEFAULTS ERROR. INVALID SYNTAX OR VALUE AT a2

Explanation: A user default specification (UDS) contains invalid values or syntax at the point listed.

System Action: This UDS and all additional UDSs in the list of UDSs are ignored.

Programmer Response: Correct the UDS in the External Defaults File (EDF). See The graPHIGS Programming Interface: Technical Reference for information on supported defaults.

Error Number: 1051

1052       NUMBER OF ARGUMENTS IS n1, SHOULD BE n2

Explanation: A call to the graPHIGS API contains fewer arguments than were defined for the routine invoked. The most common reason for this message is that a program has been linked with the reentrant interface, but the graPHIGS API calls are coded in the non-reentrant format.

System Action: The subroutine call in error is ignored.

Programmer Response: Correct the call so that all required arguments are present or link-edit with the correct interface library.

Error Number: 1052

1053       UNSUPPORTED FUNCTION CODE ON SPI CALL

Explanation: An invalid request control parameter (RCP) code was supplied to the graPHIGS API system programmer interface (SPI).

System Action: The subroutine call in error is ignored.

Programmer Response: Determine which SPI call generated the error and correct the RCP code parameter. See The graPHIGS Programming Interface: Subroutine Reference under each graPHIGS API function, for the correct RCP code value.

Error Number: 1053

1054       DEFAULTS ERROR. a1 UDS KEYWORD a2 IS IN CONFLICT

Explanation: The keyword a2 in the NICKNAME or AFMMNICK user default specification (UDS) was repeated incorrectly or is mutually exclusive with a previously specified keyword.

System Action: This UDS and all additional UDSs in the list of UDSs are ignored.

Programmer Response: Correct the UDS in the External Defaults File (EDF). See The graPHIGS Programming Interface: Technical Reference to determine the supported UDS keywords.

Error Number: 1054

1055       TOO MANY ARGUMENTS, SHOULD BE n1

Explanation: A call to the graPHIGS API contains more arguments than were defined for the routine invoked. The most common reason for this message is that a program has been linked with the non-reentrant interface, but the graPHIGS API calls were coded in the reentrant format.

System Action: The subroutine call in error is ignored.

Programmer Response: Remove the excess arguments or link-edit with the correct interface library.

Error Number: 1055

1056       (gggggg, CALLED FROM )ffffff, AT 'xxxxxxxx'X

Explanation: This is an informational message that is generated with some errors to identify where the function was invoked. ffffff contains the graPHIGS API function name and xxxxxxxx is the hexadecimal value in Register 14. When present, gggggg contains the name of a graPHIGS API function invoked as part of the processing of function ffffff

System Action: None.

Programmer Response: None required. The message is only informational.

Error Number: 1056

1057       DEFAULTS ERROR. ADS LENGTH, n1, INVALID IN ADIB SPECIFICATION

Explanation: An application default specification (ADS) has a length that is greater than 32,000 characters or has a length greater than the specified Application Default Interface Block (ADIB) total length.

System Action: This ADS and all additional ADSs in the ADIB are ignored.

Programmer Response: Correct the ADS in the ADIB. See The graPHIGS Programming Interface: Technical Reference for information on ADSs.

Error Number: 1057

1058       DEFAULTS ERROR. INVALID LENGTH n1 FOR a1 UDS

Explanation: A user default specification (UDS) of type a1 has a length n1 that is either negative or greater than 32,000 characters. The UDS was specified in the External Defaults File (EDF).

System Action: This UDS and all additional UDSs in the External Defaults File are ignored.

Programmer Response: Correct the length of the UDS in the External Defaults File. See The graPHIGS Programming Interface: Technical Reference for information on UDSs.

Error Number: 1058

1059       DEFAULTS ERROR. LABEL a2 IN SOURCE UDS TOO LONG

Explanation: A user default specification (UDS) has a label, a2, which is longer than eight characters. The UDS was specified in the External Defaults File (EDF).

System Action: This UDS and all additional UDSs in the External Defaults File are ignored.

Programmer Response: Correct the UDS in the External Defaults File. See The graPHIGS Programming Interface: Technical Reference for information on UDSs.

Error Number: 1059

1060       DEFAULTS ERROR. INVALID TOTAL LENGTH n1 IN ADIB

Explanation: Total ADIB length exceeds maximum.

System Action: Defaults are ignored; the graPHIGS API is not opened.

Programmer Response: Decrease ADIB size.

Error Number: 1060

1061       DEFAULTS ERROR. SOURCE UDS FOR a1 NOT COMPLETE

Explanation: A user default specification (UDS) of type a1 does not contain any text for its value. The UDS was specified in the External Defaults File (EDF).

System Action: This UDS and all additional UDSs in the External Defaults File are ignored.

Programmer Response: Correct the UDS in the External Defaults File. See The graPHIGS Programming Interface: Technical Reference for information on UDSs.

Error Number: 1061

1062       DEFAULTS ERROR. UDS TYPE a1 KEYWORD a2 CODE n1 NOT ALLOWED IN a2

Explanation: Default not supported in current subsystem environment.

System Action: Defaults are ignored; the graPHIGS API is not opened.

Programmer Response: Specify the default only in a valid subsystem environment.

Error Number: 1062

1063       DEFAULTS ERROR. UDS TYPE a1 CODE n1 UNKNOWN

Explanation: An unknown user default specification (UDS) of type a1 or code n1 has been defined.

System Action: This UDS and all additional UDSs in the list of UDSs are ignored.

Programmer Response: Correct the UDS. The type should be AFMMDFT, AFMMNICK, DEFAULT, or NICKNAME. If the type is one of these, check that at least one blank precedes it. If the type is positioned in column 1, it was interpreted as a label, and subsequent key word text was interpreted incorrectly as a type. See The graPHIGS Programming Interface: Technical Reference for information on defaults and nicknames.

Error Number: 1063

1064       DEFAULTS ERROR. a1 UDS KEYWORD a2 UNKNOWN

Explanation: An unknown user default specification (UDS) of type a1 or keyword a2 has been defined.

System Action: This UDS and all additional UDSs in the list of UDSs are ignored.

Programmer Response: Correct the UDS in the External Defaults File (EDF). See The graPHIGS Programming Interface: Technical Reference for information on defaults and nicknames.

Error Number: 1064

1065       DEFAULTS ERROR. VALUE OF a1 DEFAULT KEYWORD a2 CODE n1 IS INVALID

Explanation: A default specification of type a1, keyword a2, or code n1, has an invalid value.

System Action: This default and all additional defaults specified through the current mode are ignored.

Programmer Response: Correct the default. See The graPHIGS Programming Interface: Technical Reference for information on defaults and nicknames.

Error Number: 1065

1066       DEFAULTS ERROR. DEFAULT KEYWORD a2 CODE n1 NOT VALID ON THIS SUBSYSTEM

Explanation: A default specification with keyword a1 or code n1 is not supported on the subsystem being used.

System Action: This default and all additional defaults specified through the current mode are ignored.

Programmer Response: Remove the default. See The graPHIGS Programming Interface: Technical Reference for details on the defaults that are valid for your subsystem.

Error Number: 1066

1067       DEFAULTS ERROR. a1 KEYWORD a2 CODE n1 - TOO MANY OPERANDS

Explanation: A user default specification (UDS) of type a1, keyword a2, or code n1 has too many operands.

System Action: This UDS and all additional UDSs in the list of UDSs are ignored.

Programmer Response: Correct the UDS in the External Defaults File (EDF). See The graPHIGS Programming Interface: Technical Reference for information on UDSs and external defaults.

Error Number: 1067

1068       DEFAULTS ERROR. a1 PROCOPT a2 UNKNOWN

Explanation: An unknown PROCOPT keyword a2 was defined in a NICKNAME or AFMMNICK user default specification (UDS).

System Action: This UDS and all additional UDSs in the list of UDSs are ignored.

Programmer Response: Correct the UDS. See The graPHIGS Programming Interface: Technical Reference for the PROCOPT values you can specify in a nickname UDS.

Error Number: 1068

1101       NOT ENOUGH STORAGE TO PERFORM REQUESTED FUNCTION

Explanation: Insufficient storage was available to complete the requested function.

System Action: The function is terminated.

Programmer Response: Specify additional storage and re-invoke the graPHIGS API

Error Number: 1101

1103       a1 ABEND/ERROR CODE a2 - xxx X-nn, ON a2 ( - eeee )

Explanation: An abend or error occurred while attempting to perform operation a1 on a2 The operation terminated with a subsystem ABEND and error codes XXX and nn The message text may include a character string eeee..., which is an interpretation of the error.

System Action: The operation is terminated.

Programmer Response: Determine the cause of the error and re-execute the program.

Error Number: 1103

1104       a2 HAS AN INVALID FIRST RECORD

Explanation: The specified subroutine required reading the graPHIGS API file a2 The first record in the file is invalid for the indicated type of file.

System Action: The subroutine call in error is ignored.

Programmer Response: Check to see if the file was incorrectly overwritten, for example, by an attempt to renumber or sequence the file. Correct or recreate the file and re-execute the program.

Error Number: 1104

1105       INVALID FILE NAME, a2

Explanation: The specified subroutine required the input or output of the graPHIGS API file a2, which contains an invalid file name.

System Action: The subroutine call in error is ignored.

Programmer Response: Correct the call to the graPHIGS API Specify a valid name and re-execute the program.

Error Number: 1105

1106       FILE OPERATION ON a2 IGNORED BECAUSE OF PREVIOUS ABEND

Explanation: Because of a previous ABEND, the graPHIGS API is unable to perform input or output on the file a2

System Action: The subroutine call in error is ignored.

Programmer Response: Determine the cause of the original error and re-execute the program.

Error Number: 1106

1107       FILE a2 NOT FOUND

Explanation: The specified subroutine required reading the graPHIGS API file a2 from auxiliary storage; however, the file cannot be found on auxiliary storage.

System Action: The subroutine call in error is ignored.

Programmer Response: Access or create the required file and re-execute the program.

Error Number: 1107

1108       a1 ERROR CODE n1 ON a2

Explanation: An error occurred while attempting to perform an I/O function a1 on the graPHIGS API file a2 The I/O function terminated with subsystem return code n1

System Action: The file operation is terminated.

Programmer Response: Determine the cause of the error and re-execute the program.

Error Number: 1108

1109       FUNCTION NOT SUPPORTED

Explanation: An unsupported RCP code has been encountered or a subroutine was issued that is not supported by the graPHIGS API

System Action: No function is performed.

Programmer Response: If your application is using the SPI interface, correct the RCP code in error. If your application is issuing a subroutine that is not supported, it should issue the appropriate inquiries before issuing the subroutine in order to avoid the error.

Error Number: 1109

1110       CONCURRENT USAGE OF FILE a2 NOT ALLOWED

Explanation: An attempt was made to write or read to file a2 while the application or another user was reading or writing to the file.

System Action: The file operation is terminated.

Programmer Response: Correct the application to remove multiple accesses to the file or wait for the other user to finish accessing the file.

Error Number: 1110

1111       FILE a2 HAS INVALID RECORD CONTENT

Explanation: The specified subroutine required reading the graPHIGS API file a2 The content of the file is invalid.

System Action: The subroutine call in error is ignored.

Programmer Response: Correct or recreate the file and re-execute the program.

Error Number: 1111

1112       UNABLE TO OPEN a2 DD STATEMENT MISSING

Explanation: An error was found while attempting to open the graPHIGS API file a2 statement for the file was not specified.

System Action: The file operation remains incomplete.

Programmer Response: Allocate a DD statement for the specified file and re-execute the program.

Error Number: 1112

1113       FILE IS READ ONLY

Explanation: This message is either:

  • a warning that is returned by GPOPAR when the archive file is in a read-only state and the archive flag is set to 1=OPEN_READ_WRITE or

  • an error that occurred while an attempt was being made to perform an I/O function on a graPHIGS API file.

    System Action: If the message is a warning issued by GPOPAR, then the archive file is opened. However, structures cannot be added to or deleted from the archive file. If the message is an error issued by another subroutine, the file operation is terminated.

    Programmer Response: Check the error log to determine which function caused the error. If the message is a warning issued by GPOPAR, do one of the following:

  • set up the file so that it can be written to by the graPHIGS API nucleus

  • change the archive file to 2=OPEN_READ_ONLY

  • take no action If the message is an error issued by another subroutine, make sure that the file is on a disk/file system/directory to which the nucleus has write access.

    Error Number: 1113

    1114       FILE CANNOT BE CREATED. DISK IS READ ONLY

    Explanation: GPOPAR was invoked with a file descriptor of a file that does not exist and could not be created because the location is read only or the archive flag parameter is set to 2=READ_ONLY

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of GPOPAR that caused the error. If the archive flag parameter is set to 2=READ_ONLY , then change it to 1=READ_WRITE If the file is supposed to exist, then change the file descriptor to match the file or change the file mode (for VM) or the disk/directory characteristics so that the graPHIGS API nucleus has read/write capability.

    Error Number: 1114

    1115       FILE a2 HAS INVALID DCB CHARACTERISTICS

    Explanation: The specified subroutine required opening file a2 for input. The DCB characteristics of the file are incompatible with the requirements.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Correct or recreate the file and then re-execute the program.

    Error Number: 1115

    1116       UNABLE TO OPEN a2 FILE MISSING OR INVALID

    Explanation: An error was encountered during an attempt to open the the graPHIGS API file a2 Possible causes are:

  • file organization is inconsistent with the anticipated organization

  • DDNAME was not allocated (MVS)

  • an attempt was made to open a read-only file for output

    System Action: The subroutine call in error is ignored.

    Programmer Response: Correct the file definition and then re-execute the program.

    Error Number: 1116

    1117       INCORRECT RECORD LENGTH OR FORMAT ON a2

    Explanation: The specified subroutine required opening file a2 for input. The record length or the format of the file is incompatible with the requirements.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Correct or recreate the file and then re-execute the program.

    Error Number: 1117

    1118       NO MORE DISK SPACE AVAILABLE, WHEN WRITING TO a1

    Explanation: Additional disk space is unavailable for new data in the specified file or data set a1

    System Action: The operation is terminated.

    Programmer Response: Provide more disk space, possibly by rebuilding the library or data set.

    Error Number: 1118

    1119       FILE a2 ALREADY EXISTS

    Explanation: The specified subroutine required writing to the graPHIGS API file a2 without replacing any existing file(s) having the same name. A file of the same name already exists.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Correct the program by specifying a file name that does not currently exist.

    Error Number: 1119

    1121       UNRECOVERABLE I/O ERROR

    Explanation: A previous error has occurred in an archive file subroutine which has left the file in a state such that it cannot continue to be used.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Run the gPafut utility to recover the archive file to make it usable by archive file subroutines. See The graPHIGS Programming Interface: Technical Reference for more information on using the gPafut utility.

    Error Number: 1121

    1122       a1 ERROR CODE n1-n2, ON a2

    Explanation: An error occurred during an attempt to perform an I/O function a1 on the graPHIGS API file a2 The I/O function terminated with subsystem return codes n1 (decimal) and n2 (decimal).

    System Action: The file operation is terminated.

    Programmer Response: Determine the cause of the error and re-execute the program. See the bibliography for a list of manuals containing information on subsystem and return codes.

    Error Number: 1122

    1123       PACKAGING ERROR. RMODE OF a1 CONFLICTS WITH INITIALIZATION AMODE

    Explanation: Dynamically loaded routine a1 requires execution in 31-bit addressing mode. The graPHIGS API is initialized in 24-bit mode and cannot execute routines requiring 31-bit mode. Successful execution of subsequent the graPHIGS API calls cannot be guaranteed.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Contact your system administrator to check the installation of the GDDM/graPHIGS API. If the graPHIGS API is properly installed, change the loaded routine to execute in 24-bit mode.

    Error Number: 1123

    1124       ABEND CODE n1

    Explanation: The specified subroutine terminated abnormally and gave the user ABEND number n1 in decimal form.

    System Action: The function is terminated.

    Programmer Response: If the remedy is not apparent, inform your system programmer. See the ABEND codes in the appendix.

    Error Number: 1124

    1125       INVALID VERSION IDENTIFIER IN FILE a1

    Explanation: An unsupported version identifier has been found in the version identifier field of the file a1

    System Action: The subroutine call in error is ignored.

    Programmer Response: Check the file a1 to ensure that the format, including the version number, is correct. See The graPHIGS Programming Interface: Technical Reference for more information.

    Error Number: 1125

    1126       FILE a1 IS NOT VALID IN THIS ENVIRONMENT

    Explanation: File a1 is not valid under one of the following conditions:

  • current environment is ASCII, but ASCII index flag in file a1 is off

  • current environment is EBCDIC, but EBCDIC index flag in file a1 is off

  • EBCDIC to ASCII translation table requested, but EBCDIC to ASCII translation table flag is off in file a1

  • ASCII to EBCDIC translation table requested, but ASCII to EBCDIC translation table flag is off in file a1

    System Action: The subroutine call in error is ignored.

    Programmer Response: Check the file a1 to ensure that the format and content, including the flag settings, are correct. See The graPHIGS Programming Interface: Technical Reference for more information.

    Error Number: 1126

    1127       INVALID DEFAULT CHARACTER IN FILE a1

    Explanation: An invalid default character has been found in processing file a1

  • If file a1 is for a single-byte character set, possible errors include:

  • the default character is out of the given codepoint range

  • the symbol id for the default character is zero

  • the symbol id index entry for the default character has the 'undefined symbol' flag on

  • If file a1 is for a double-byte character set, possible errors include:

  • the first byte of the default character is out of the given B1 table range

  • the second byte of the default character is out of the given B2 table range

  • the symbol id for the default character is zero

  • the symbol id index entry for the default character has the 'undefined symbol' flag on

    System Action: The subroutine call in error is ignored.

    Programmer Response: Check the file a1 to ensure that the format and content are correct. See The graPHIGS Programming Interface: Technical Reference for more information.

    Error Number: 1127

    1128       INVALID INDEX VALUE IN FILE a1

    Explanation: An incorrect index value (or values) has been found in processing file a1 Possible errors include:

  • the start index value is greater than the end index value

  • for symbol files, the start symbol index is zero

  • for character set files, the start and end index is not within the range of valid index values ('40'X to 'FE'X in GDDM/graPHIGS or '20'X to 'FF'X in the Personal graPHIGS API.)

    System Action: The subroutine call in error is ignored.

    Programmer Response: Check the file a1 to ensure that the format and content, including index values, are correct. See The graPHIGS Programming Interface: Technical Reference for more information.

    Error Number: 1128

    1129       SYMBOL DEFINITION OFFSET INVALID IN FILE a1

    Explanation: While processing an entry in the symbol ID index of file a1, the offset to locate the symbol definition, plus the number of bytes for that symbol ID exceeded the length of the symbol definitions.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Check the file a1 to ensure that the format and content are correct. See The graPHIGS Programming Interface: Technical Reference for more information.

    Error Number: 1129

    1130       INVALID OFFSET DATA IN FILE a1

    Explanation: There is invalid data in the header of the symbol file a1 Possible errors include:

  • offsets that are past the end of the file

  • offsets that are equal

    System Action: The subroutine call in error is ignored.

    Programmer Response: Check the file a1 to ensure that the format and content, including header data, are correct. See The graPHIGS Programming Interface: Technical Reference for more information.

    Error Number: 1130

    1132       RESOURCE CREATION AFS USERID/PASSWORD VALIDATION SUBSYSTEM TIMEOUT

    Explanation: GPEXAP was invoked on an AIX system with AFS installed and AFS could not validate the userid and password within a time limit.

    System Action: The request is ignored.

    Programmer Response: Check that the AFS subsystem is running and active. Rerun the application. If the problem persists, contact your system administrator.

    Error Number: 1132

    1133       RESOURCE CREATION REQUIRED AN AFS TOKEN THAT DOES NOT EXIST

    Explanation: GPEXAP was invoked on an AIX system with AFS installed to a nucleus that was started by a user who does not have an active token for the user in the userid parameter.

    System Action: The request is ignored.

    Programmer Response: Create an AFS token for the user specified in the GPEXAP call on the nucleus host processor from the same user that started the remote nucleus or start the remote nucleus as root user. Rerun the application.

    Error Number: 1133

    1150       SF ERROR. SF: a1, RSID: a2, OFS: a3, EC: a4

    Explanation: A structured field error has occurred at offset a3 within structured field a1 The resource identifier is a2 and the error code is a4

    System Action: The structured field is ignored.

    Programmer Response: If possible, reproduce the error with the graPHIGS API trace turned on. Contact and inform a service representative of the error number and conditions surrounding its occurrence.

    Error Number: 1150

    1201       SYSTEM SERVICE xxx ERROR RETURN CODE = yyy

    Explanation: An AIX system call or C library subroutine xxx has completed with yyy in error number.

    System Action: The subroutine call in error is ignored.

    Programmer Response: See AIX Operating System Technical Reference, SV21-8009, for an explanation of error number yyy for function xxx If the remedy is not apparent, contact your system programmer.

    Error Number: 1201

    1202       MESSAGE NUMBER xxx CANNOT BE FOUND

    Explanation: The required message cannot be located.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Inform a service representative of the error number and conditions surrounding its occurrence.

    Error Number: 1202

    1203       FILE SERVICE xxx ERROR RETURN CODE = yyy ON FILE nn

    Explanation: An AIX file service xxx has completed with error yyy in error number when accessing file nnn

    System Action: The subroutine call in error is ignored.

    Programmer Response: Check to see that you have the required authority to read, write, and create files in the current directory and that there is available disk space. See AIX Operating System Technical Reference, SV21-8009, for an explanation of error number YYY for function XXX

    Error Number: 1203

    1204       graPHIGS ABORT CODE = n1

    Explanation: A very severe error occurred. The graPHIGS API could not continue.

    System Action: The application process is terminated by calling the AIX system call, ABORT. See AIX Operating System Technical Reference, for a description of this function.

    Programmer Response: See Appendix B. "ABORT Codes for the Personal graPHIGS API" for an explanation of the condition associated with the ABORT code n1 If a remedy is not apparent, inform a service representative of the error number and the conditions surrounding its occurrence.

    Error Number: 1204

    1205       FILE IS NOT A VALID graPHIGS ARCHIVE FILE

    Explanation: GPOPAR was invoked, and the archive file specified in the archive file descriptor is not a valid graPHIGS API archive file.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of GPOPAR that caused the error. Verify that the file specified in the archive file descriptor is a file that was generated by the graPHIGS API as an archive file. (The graPHIGS API archive format is the only binary format that is currently supported.) If the file is a graPHIGS API archive file, then run the gPafut utility to recover the file. The archive file must have a fixed record format and a record length of 256 bytes. See The graPHIGS Programming Interface: Technical Reference for more information on using the gPafut utility.

    Error Number: 1205

    1206       VERSION OF graPHIGS ARCHIVE FILE NOT RECOGNIZED

    Explanation: GPOPAR was invoked, and the archive file specified in the archive file descriptor is a valid graPHIGS API archive file. However, the format of the archive file is not known to the current graPHIGS API nucleus. This situation can happen only if:

  • an archive file is generated by a graPHIGS API nucleus which is of a later release than the graPHIGS API nucleus that is trying to open the archive file

    and

  • the later graPHIGS API release underwent an archive file format change that is not backwards compatible.

    System Action: The subroutine call in error is ignored.

    Programmer Response: The archive file cannot be used by the older graPHIGS API nucleus. It can be used only by applications that are using the later graPHIGS API release. Make sure the graPHIGS API releases are compatible.

    Error Number: 1206

    1207       LINK ADDRESS CONFLICT

    Explanation: A request was made, using the chgPcon command, to allocate a device address, but gPgated determined that there was a configuration conflict.

    System Action: The request is ignored.

    Programmer Response: Contact your system administrator to determine the correct configuration for the gateway or other devices (e.g., 5086s) that may be sharing the link.

    Error Number: 1207

    1208       gPgated CHILD EXITING, RECEIVED SIGNAL n1

    Explanation: A gPgated child has exited as a result of either a user request or an error.

    System Action: Connection to the application is terminated.

    Programmer Response: If the signal received was 2, then this message is a confirmation of a user-generated interrupt (e.g., CTRL-C ). No response is needed. If the signal received was other than 2, then check the error log to determine what caused the error. Rerun the application.

    Error Number: 1208

    1209       gPgated SHUTDOWN, RECEIVED SIGNAL n1

    Explanation: All gPgated child processes have exited as a result of either a user request or an error.

    System Action: All connections managed by the gateway are terminated.

    Programmer Response: If the signal received was 2, then this message is a confirmation of a user-generated interrupt (e.g., CTRL-C ). No response is needed. If the signal received was other than 2, then check the error log to determine what caused the error. Rerun the application.

    Error Number: 1209

    1210       RECOVERY ACTION ON DEVICE ADDRESS xxx ALLOCATED TO hostname:nucid IS COMPLETE

    Explanation: A gPgated connection was terminated and an attempt was made to recover the connection.

    System Action: System attempted to recover the connection.

    Programmer Response: The connection has been reset, but the application state information has been lost. Rerun the application.

    Error Number: 1210

    1301       SPECIFIED APPLICATION PROCESS ID ALREADY IN USE

    Explanation: GPEXAP or GPINAP was invoked with an application process identifier for which an application process already exists.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of GPINAP that caused the error. Assign a unique application process identifier. Guarantee that a unique application process identifier is supplied for each application process initiated.

    Error Number: 1301

    1302       SPECIFIED APPLICATION PROCESS ID DOES NOT EXIST

    Explanation: GPTMAP was invoked with an application process identifier that does not exist.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error. Assign a correct application identifier. Be sure that GPINAP was successful for the application process identifier involved.

    Error Number: 1302

    1303       SIZE OF APPLICATION PROCESS REGION IS TOO LARGE

    Explanation: GPINAP or GPEXAP was invoked with a size which exceeds the memory available on the target nucleus.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error. Check for the correct memory size allocated. Memory for items such as structure store, image board, and application regions come from a common pool. Decrease memory use of the pool.

    Error Number: 1303

    1304       APPLICATION PROCESS REQUEST EXCEEDS NUCLEUS CAPACITY

    Explanation: GPEXAP or GPINAP was invoked and the nucleus does not support this service or too many application processes have been created on the nucleus.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused error. Check for the correct nucleus identifier. Guarantee that the nucleus identifier is for a nucleus running on a 9999. If you wish to start this application process, then you may need to terminate existing applications.

    Error Number: 1304

    1305       LENGTH OF APPLICATION MODULE NAME IS INVALID

    Explanation: GPEXAP or GPINAP was invoked with an invalid file name length.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error. Correct the file name length parameter.

    Error Number: 1305

    1307       APPLICATION MODULE HAS UNRESOLVED EXTERNAL REFERENCE a1

    Explanation: GPEXAP or GPINAP was invoked for a program module that resulted in an unresolved external reference, when an attempt was made to load the module.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error. Determine why the specified external reference cannot be resolved and correct it.

    Error Number: 1307

    1308       PARAMETER TYPE IS INVALID

    Explanation: GPEXAP or GPINAP was invoked with an invalid parameter format type.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error. Correct the parameter format type.

    Error Number: 1308

    1309       PARAMETER LENGTH < ZERO

    Explanation: GPEXAP or GPINAP was invoked with a parameter length less than zero.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error and correct the parameter length.

    Error Number: 1309

    1310       APPLICATION MODULE SIZE > REGION SIZE

    Explanation: GPEXAP or GPINAP was invoked with a program module larger than the size parameter specified.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error. Correct the size parameter or the program module size, or both, if incorrect.

    Error Number: 1310

    1311       APPLICATION LOAD MODULE IS INVALID

    Explanation: GPEXAP or GPINAP was invoked with a program module containing format errors.

    System Action: The subroutine call in error is ignored.

    Programmer Response: Locate the specific invocation of the subroutine that caused the error. Correct the program module. See The graPHIGS Programming Interface: Subroutine Reference for an explanation of the program module format required.

    Error Number: 1311

    1312       APPLICATION REGION IS NOT IN " LOAD PENDING " STATE

    Explanation: GPINAP has been invoked and an unexpected error was encountered.

    System Action: More errors may be generated depending on the cause of the error.

    Programmer Response: This is probably not an application error. If possible, reproduce the error with the graPHIGS API trace turned on. Inform a service representative of the error number and conditions surrounding its generation.

    Error Number: 1312

    1313       APPLICATION REGION IS NOT IN " ACTIVATE PENDING " STATE

    Explanation: GPINAP has been invoked and an unexpected error was encountered.

    System Action: More errors may be generated depending on the cause of the error.

    Programmer Response: This is probably not an application error. If possible, reproduce the error with the graPHIGS API trace turned on. Inform a service representative of the error number and conditions surrounding its generation.

    Error Number: 1313

    1314       ABEND IN APPLICATION PROCESS. ID= n1 CODE= n2 OFFSET=n3

    Explanation: An execution error has occurred at offset n3 within the load module for the distributed application process with identifier n1 Code n2 indicates the cause of the ABEND. For valid codes, see Appendix A, "Distributed Application Process" in The graPHIGS Programming Interface: Writing Applications

    System Action: The application process is terminated. However, the allocated memory is not freed. The nucleus is disconnected and all open files are closed.

    Programmer Response: Determine the cause of the error at the given offset within the distributed application process load module. Correct the error.

    Error Number: 1314

    1315       ABEND IN SYSTEM SERVICE CALLED BY APPLICATION PROCESS. ID=n1 CODE=n2 OFFSET= n3

    Explanation: An execution error in a system service has occurred. The system service which detected the error was called at offset n3 within the load module for the distributed application process with identifier n1 Code n2 indicates the cause of the ABEND. For valid codes, see Appendix A, "Distributed Application Process" in The graPHIGS Programming Interface: Writing Applications

    System Action: The application process is terminated. However, the allocated memory is not freed. The nucleus is disconnected and all open files are closed.

    Programmer Response: Determine the cause of the error at the given offset within the distributed application process load module. Correct the error.

    Error Number: 1315

    1316       APPLICATION PROCESS ID=n1 EXITED WITH CODE=n2

    Explanation: The distributed application process with identifier n1 has exited processing with code n2 This is an application specified code.

    System Action: The application process is terminated.

    Programmer Response: Determine the reason that the application has exited and correct the error.

    Error Number: 1316

    1317       FLAG PARAMETER IS INVALID

    Explanation: GPEXAP was invoked with an invalid value for the transfer and/or execute parameter xferflag

    System Action: The subroutine call in error is ignored.

    Programmer Response: See The graPHIGS Programming Interface: Subroutine Reference for valid values.

    Error Number: 1317

    • [ Previous | Next | Contents | Glossary | Home | Search ]