Text |
Label does not match label ... at line .... |
Explanation |
The label given after END-... is not the label specified at the beginning of this block. If a label is given between parentheses after END-..., it must be the same as the one used to define this block. The label and line number are indicated in the error message. |
Action |
Correct the label between parentheses; or remove this reference (not recommended). |
Text |
... class .../... failed, reason ... .... |
Explanation |
Reason 1: Error during "SEARCH CLASS" occurred.
2: Class or classes not found.
3: COM not available.
4: NATGWCOM cannot be loaded.
5: Return code from NATGWCOM.
6: Class already registered with a different class GUID.
7: Cannot OPEN registry.
8: Error during register server information.
9: Error during register client information.
10: No valid Natural environment (NATDIR/NATVERS).
11: Invalid activation policy or no default server specified.
12: Internal error.
|
Text |
Nested PARSE XML loops not allowed. |
Explanation |
Invalid usage of nested PARSE XML statements parser. A PARSE XML loop must not be placed within another PARSE XML loop. |
Action |
Correct program. |
Text |
Nested parse JSON loop not allowed |
Explanation |
Natural detected a recursive call to the JSON parser. |
Action |
Correct program. |
Text |
Handle/dynamic variables and X-arrays cannot be redefined. |
Explanation |
A variable declared DEFINE DATA LOCAL
- with type HANDLE, -> 1 #H HANDLE OF OBJECT
- as an alphan. or binary field -> 1 #AD (A) DYNAMIC
with a dynamic length,
- as an array with a variable -> 1 #VA (A10/1:*)
number of occurrences END-DEFINE
cannot be redefined, and it must not result from a redefinition.
If a group contains one of these fields in the first position, the
group cannot be redefined.
|
Action |
Check and correct the variable definitions. |
Text |
FETCH FIRST, OFFSET, OPTIMIZE FOR, UNION/EXCEPT/INTERSECT invalid. |
Explanation |
1) Neither an OPTIMIZE FOR nor an UNION/EXCEPT/INTERSECT clause may be specified for a SELECT SINGLE statement. 2) The value specified in the FETCH FIRST, OFFSET, OPTIMIZE FOR clause is neither an integer constant nor a numeric variable. 3) The keyword ROWS or ROWS ONLY is missing after the integer constant or numeric variable. 4) The OFFSET clause is not allowed at that place (CTE, fullselect) |
Action |
Check and correct syntax. |
Text |
Incorrect use of UPDATE/DELETE .. WHERE CURRENT CURSOR. |
Explanation |
An UPDATE/DELETE table WHERE CURRENT CURSOR must reference a SELECT statement. It cannot, for example, reference a FIND statement. |
Action |
Check and correct syntax. |
Text |
UPDATE/DELETE table mismatch with SELECT statement. |
Explanation |
The table referenced in an UPDATE table WHERE CURRENT CURSOR or DELETE FROM table WHERE CURRENT CURSOR statement is not the table specified in the corresponding SELECT statement. |
Action |
Check and correct syntax. |
Text |
Incorrect alphanumeric constant specified in <<...>>. |
Explanation |
The constant specified in <<...>> does not adhere to the rules for Natural constants. For example, alpha constants must be enclosed in apostrophes. |
Action |
Check and correct syntax. |
Text |
Variable reference in <<...>> cannot be resolved. |
Explanation |
1) The token directly following the variable indicator (:) does not adhere to the rules for variable names. 2) The variable specified is not defined in the program. |
Action |
Check and correct syntax. |
Text |
No valid correlation name after AS keyword in FROM clause. |
Explanation |
A correlation name is required after the keyword AS in the FROM clause of a SELECT statement. This name could not be found. |
Action |
Either drop the keyword AS or insert a valid correlation name behind the keyword. |
Text |
Keyword JOIN expected after INNER, LEFT, RIGHT, FULL, etc. |
Explanation |
The keyword JOIN is required after one of the keywords INNER, LEFT, LEFT OUTER, RIGHT, RIGHT OUTER, FULL, FULL OUTER. |
Action |
Insert the keyword JOIN. |
Text |
A correlation name is required in the FROM clause. |
Explanation |
When a subquery is specified in a FROM clause, a correlation name is required. This name must follow the SUBSELECT clause. |
Action |
Insert a correlation name after the subquery within the FROM clause. |
Text |
No valid table reference found in FROM clause. |
Explanation |
The FROM clause contains no valid table name. Either specify a table name or a subquery of a joined table expression. |
Action |
Correct the FROM clause by specifying a valid table name. |
Text |
Illegal use of keyword VALUE or COALESCE in join. |
Explanation |
The keywords VALUE and COALESCE can only be used in a join expression if the related join operation is a FULL join or a FULL OUTER join. |
Action |
Use VALUE and COALESCE keywords only if a FULL join is specified. |
Text |
Closing bracket missing in nested joined-table expression. |
Explanation |
In a nested joined-table expression, the number of opening brackets must be equal to the number of closing brackets. |
Action |
Insert a closing bracket. |
Text |
Expression requires join-condition keyword ON. |
Explanation |
The keyword ON is missing in a joined-table expression. The joined- table expression must have a join-condition which starts with the keyword ON. The join-condition expression looks like: ON <join-expression> <relational-operator> <join-expression> |
Action |
Insert the keyword ON. |
Text |
Join-condition contains an invalid relational operator. |
Explanation |
The join-condition contains an invalid relational operator. The following relation operators are valid: = <> > < >= <= For a FULL join or FULL OUTER join, only "=" is valid. See the Natural Statements documentation for further information. |
Action |
Specify a valid relational operator. |
Text |
At least two column names must follow VALUE or COALESCE. |
Explanation |
After the keyword VALUE or COALESCE, at least two column names must follow. These column names must be separated by a comma and placed within parentheses. For example: VALUE (column1,column3,...,columnX) Ensure that none of the following syntax elements is missing: - An opening parenthesis. - A closing parenthesis. - A separating comma. |
Action |
Insert the missing comma, operand, or parenthesis. |
Text |
Column name does not belong to any table to be joined. |
Explanation |
The join-expression may only contain column names which belong to one of the tables to be joined. At least one of the column names does not belong to any of the joined tables. |
Action |
Check column names to determine which do not belong to a joined table. Correct the table name in the join expression. |
Text |
Nested PARSE XML and PARSE JSON not allowed. |
Explanation |
Invalid usage of nested PARSE XML and PARSE JSON statements. A PARSE XML loop must not be placed within a PARSE JSON loop. Nor can a PARSE JSON be placed within a PARSE XML loop. |
Action |
Correct program. |
Text |
Program cannot be executed. |
Explanation |
While loading the Natural program, an internal, non-recoverable error has occurred. The program could not be loaded into the Natural buffer pool. |
Action |
Check program and/or contact your Natural administrator. |
Text |
Buffer pool full. |
Explanation |
The Natural buffer pool is full. To execute a Natural object, it must be loaded into the Natural buffer pool. If not enough space is available in the Natural buffer pool, the Natural object cannot be executed. |
Action |
Contact your Natural administrator. |
Text |
Program not ready for execution. |
Explanation |
The program to be executed is in the process of being cataloged by another user. When loading this program into the Natural buffer pool, Natural can not guarantee that the program code is in a correct and executable state. |
Action |
Execute the program at a later point in time. |
Text |
Program cannot be executed. |
Explanation |
This message appears if Natural has tried unsuccessfully 32 times to load the program into the Natural buffer pool. |
Action |
Contact your Natural administrator. |
Text |
Invalid Case-expression or invalid WHEN-clause in MERGE statement. |
Explanation |
1) The specified Case-Expression is invalid: The keywords ELSE, THEN, WHEN , END are misplaced, or one of these keywords is missing, or one of the sub-expressions is invalid. 2) The specified WHEN-clause in the MERGE statement is invalid: Either no WHEN-clause or duplicate WHEN-clauses or invalid WHEN-clauses are specified in a MERGE statement. |
Action |
Check the syntax of the case-expression or of the MERGE statement. |
Text |
Internal Natural Db2 error. |
Action |
Provide the Natural source and object program and contact Software AG support. |
Text |
No fields were selected by a FIND or READ statement. |
Explanation |
A FIND or READ statement does not retrieve any fields (empty view), but is directed to access an SQL database (e.g. Db2). This will result in the generation of an SQL SELECT statement with an empty column list. However, this is not permitted. |
Action |
Retrieve at least one field in the FIND or READ statement. |
Text |
Invalid Natural statement for Db2 access. |
Explanation |
The following Natural statements are not supported when accessing a Db2 database: - GET - STORE USING NUMBER (ISN) |
Action |
Check program and correct error. |
Text |
Insufficient space for SQL ... generation. |
Explanation |
During the generation, the corresponding buffer has overflowed. Either provide a greater thread/partition/region, or split the program"s SQL parts and put them into different programs. The message relates either to the buffer containing the SQL statements or to the buffer containing the SQL XREF data. |
Action |
Start Natural in greater thread/partition/region, or reduce the number or size of SQL statements. |
Text |
Internal Natural Db2 error. |
Action |
Provide the Natural source and object program, and contact Software AG support. |
Text |
No fields assigned for an UPDATE statement. |
Explanation |
Natural Db2: An UPDATE statement is present, but no database fields are specified for the view. |
Action |
Assign a value to a Db2 column. |
Text |
A read-only field may not be modified. |
Explanation |
Natural for Db2: Read-only fields were specified in an UPDATE statement. This is not allowed, because these fields may not be modified. |
Action |
Check program and correct error. |
Text |
UPDATE/DELETE must not be used in conj. with FIND SORTED. |
Explanation |
UPDATE/DELETE must not be used in conjunction with READ BY, FIND ... ORDER BY, SELECT ... ORDER BY or READ RESULT SET according to Db2 processing logic. |
Action |
Correct error in program. |
Text |
Field in SORTED BY clause is not referenced. |
Explanation |
Natural for Db2: A field referenced in the SORTED BY clause is not referenced anywhere in the program. |
Action |
Check program and correct error. |
Text |
No primary key in an IMS access. |
Explanation |
Natural for Db2 needs a primary key for UPDATE or DELETE if the loop contains a terminal statement. |
Action |
Change program according to the Natural for Db2 file-server logic. |
Text |
Data type not supported. |
Explanation |
The search criterion contains a Natural variable or constant
of a format that is not supported by the Db2 database manager.
Unsupported formats are:
I1 (integer with length of 1)
L (logical)
|
Action |
Do not use the above formats in a program that accesses a Db2 database. |
Text |
Null or length referenced without the master field. |
Explanation |
When referencing a length-indicator or null-indicator field, the corresponding master field to which the length or null indicator applies must also be referenced. |
Action |
Correct program. |
Text |
Null or length indicator cannot be used as descriptor. |
Explanation |
A null indicator or length indicator cannot be used as a descriptor, only master fields can be used as search criteria. |
Action |
Change search criterion in Natural program. |
Text |
SELECT FOR UDPATE, but UPDATE not allowed. |
Explanation |
This message also appears with the statement SELECT SINGLE FOR UPDATE where UPDATE is not allowed. |
Action |
Check and correct program. |
Text |
Nested PARSE XML loops not allowed. |
Explanation |
Invalid usage of nested PARSE XML statements. A PARSE XML loop must not be placed within another PARSE XML loop. |
Action |
Correct program. |
Text |
Nested PARSE JSON loops not allowed. |
Explanation |
Invalid usage of nested PARSE JSON statements. A PARSE JSON loop must not be placed within another PARSE JSON loop. |
Action |
Correct program. |
Text |
Invalid use of set name in search criterion. |
Explanation |
A set name has been specified in the basic search criterion of a FIND statement; however - the file to be accessed is not an Adabas file, or - the search criterion belongs to a COUPLED criterion. In either case, a set name must not be used. See the Natural documentation, FIND statement, for information on the use of a set name. |
Action |
Change the search criterion in your program. |
Text |
Invalid common table expression. |
Explanation |
The specified common table expression is invalid. A common table expression has to follow the keyword WITH̲CTE and has the syntax: cte-name (colname,...) AS (fullselect). Most likely, parentheses, the keyword AS or commas are missing or specified too often. |
Action |
Correct the common table expression. |
Text |
Scalar fullselect has to consist of a single column value. |
Explanation |
Scalar fullselect can be used as scalar values in expressions. Scalar fullselect is a fullselect enclosed in parentheses which returns a single row consisting of a single column value. The specified fullselect result set consists of more than one column. |
Action |
Specify only one column in the selection list of the fullselect. |