2001
| INVALID SYNTAX IN SOURCE STATEMENT
Meaning A string which could not be interpreted was used as the name. The next valid begin keyword is searched for. Response Enter the correct statement. |
2002
| STATEMENT BEGINNING WITHOUT CORRECT PRIMARY KEYWORD
Meaning A statement does not begin with a permissible begin keyword. The next valid begin keyword is searched for. Response Enter the correct statement. |
2003
| NO VALID STATEMENT INPUT
Meaning No statement which can be interpreted has been input. BGSIA terminates. Response Restart BGSIA using the correct statement. |
2004
| DATABASE COULD NOT BE OPENED. DB-STATUS = NNNNN
Meaning Error occurring when entering the READY statement to the linked-in DBH. Response According to the DB status. |
2005
| SCHEMA-NAME MISSING, NAME OF USERSCHEMA IS ASSUMED
Meaning The schema name has not been specified in any statement. The name of the user schema is taken from the compiler database. Response None. |
2006
| NO [AREA|RECORD|SET] WITH NAME oldname FOUND IN OLD SIA
Meaning No suitable object with the name oldname exists in the old SIA. The names and structures of the old and new SIA do not satisfy the conditions for renaming. Response Correct DDL/SSL source or RENAME statement; repeat cycle or BGSIA. |
2010
| DISPLAY/ESTIMATE CLAUSE WITHOUT GENERATE CLAUSE
Meaning The DISPLAY statement can only be used in conjunction with the GENERATE statement. BGSIA terminates. Response Restart either BPSIA or BGSIA using the correct statement. |
2011
| DIFFERENT NAMES IN THE DISPLAY AND GENERATE CLAUSE
Meaning Warning: The schema names in the DISPLAY and GENERATE statements do not match. The statement last entered is ignored completely and the next valid begin keyword is searched for. Response Specify schema names within one statement only. |
2015
| NO MEDIA SPACE AVAILABLE ON DBDIR
Meaning DBDIR overflow when storing the user SIA. Response Increase size of DBDIR, repeat BGSIA. |
2016
| NO SPACE FOUND FOR SIA/SSIA
Meaning The SIA/SSIA is too large and cannot be internally stored. Response Reduce the schema and recreate. |
2018
| WRONG SYNTAX OF RENAME STATEMENT
Meaning The RENAME statement was specified with incorrect syntax. Response Correct RENAME statement; repeat BGSIA. |
2020
| NO CORRECT OUTPUT OF THE SCHEMA-COMPILATION
Meaning There is no user schema definition in the compiler database; DDL compilation has not run correctly. Response Repeat schema compilation. |
2021
| THE SCHEMA NAME IS DIFFERENT FROM THE COMPILED SCHEMA
Meaning The specified schema name does not match that of the DDL compilation. Response Either no action or specify correct name and repeat BGSIA. |
2022
| BGSIA ALREADY EXECUTED
Meaning BGSIA has already been executed. The BGSIA of a UDS/SQL version lower than V2.0B30 has been executed and the schema of the database involved contains YEAR or REFERENCE-YEAR specifications.
Response None. Use the correct UDS/SQL version (>= V2.0B30).
|
2023
| ONE SPECIFIED KEY IS TOO LONG FOR THE PAGE-LENGTH
Meaning Self-explanatory. Response Reduce length of key, repeat definition. |
2024
| RECORD recordname DOES NOT FIT WITHIN ONE PAGE
Meaning The indicated record type exceeds the usable page length (in the case of direct CALC, take account of the additional space required for the key). Response Reduce length of record type, repeat definition. |
2025
| recordname : MIN 2 REC. MUST FIT WITHIN ONE PAGE
Meaning At least two records must fit on one page for this record type which is a member in a set with MODE IS LIST. Response Reduce length of record type or select set mode other than LIST, repeat definition. |
2026
| NO AREAS IN SCHEMA
Meaning Error when reading the first realm definition from the compiler database. Response Repeat definition. |
2027
| NO RECORDS IN SCHEMA
Meaning Error when reading the first record type definition from the compiler database. Response Repeat definition. |
2028
| RECORD recordname HAS NO WITHIN-AREA-CLAUSE
Meaning Error when reading the first AREA WITHIN definition of the indicated record type from the compiler database. Response Repeat definition. |
2029
| SET setname HAS NO USER KEYS
Meaning Error when reading the first USER-KEY-CLAUSE definition of the set indicated from the compiler database. Response Repeat definition. |
2030
| INCONSISTENT USER-SIA FOUND
Meaning When estimating the realm sizes (output in the Estimate Report) BGSIA found discrepancies in the SIA which has just been generated. No Estimate Report is output. Response Repeat definition; if reproduction is possible, compile diagnostic documentation and write error report. |
2037
| DURING DB CREATION RENAME STATEMENTS ARE IGNORED
Meaning RENAME statements are ignored while a database is being created. Response Remove RENAME statement from creation procedures; if necessary, repeat BGSIA. |
2038
| SOME RENAME STATEMENTS HAVE NOT BEEN USED
Meaning One or more renaming statements could not be executed because the old name specified was not found in the old schema. Response Check RENAME statement; if necessary, repeat BGSIA. |
2039
| WHILE RESTRUCTURING RENAME STATEMENTS ARE IGNORED
Meaning RENAME statements are ignored during restructuring. Response Remove RENAME statement from restructuring procedures; if necessary, repeat BGSIA. |
2040
| THE OLD USER-SIA COULD NOT BE READ
Meaning The SIA of the old schema could not be read in. |
2040
| WHILE RESTRUCTURING, THE OLD USER-SIA COULD NOT BE READ
Meaning During DB restructuring the SIA of the old schema, from which the old references were to be taken, could not be read. Response Repeat restructuring. |
2041
| NOT ENOUGH FREE REC-REFS AVAILABLE
Meaning The database contains too many record types (> 254 for 2-Kbyte database, > 32766 for 4/8-Kbyte database). During restructuring, both the retained old and the new record types count. Response Repeat with fewer (new) record types, or convert 2-Kbyte database to 4-Kbyte or 8-Kbyte database. |
2042
| NOT ENOUGH FREE SET-REFS AVAILABLE
Meaning The database contains too many sets (>32766). During restructuring, both the old and the new sets count. Response Repeat definition. |
2043
| NOT ENOUGH FREE AREA-REFS AVAILABLE
Meaning The database contains too many realms (>125 for 2-Kbyte records, >247 for 4/8-Kbyte records). During restructuring, both the old and the new realms count. Response Repeat definition. |
2044
| NOT ENOUGH FREE KEY-REFS AVAILABLE
Meaning The database contains to many keys (>32676) Response Correct schema ; restart BGSIA. |
2099
| NUMBER KEYS OF SET setname EXCEEDS 255
Meaning A maximum number of 255 keys may be defined for an owner record type. Response Correct schema ; restart BGSIA. |