Text |
Number of parameters (CALLNAT NBR/SUBPGM NBR) do not match. |
Explanation |
The number of parameters defined in the referenced subprogram and supplied in the CALLNAT do not match. |
Text |
Sequence clause not valid for .... |
Explanation |
The specified database defined by the view name does not support the processing of records in the specified sequence in a READ or HISTOGRAM statement. In a READ .. IN LOGICAL SEQUENCE .. and HISTOGRAM statement, the use of DESCENDING requires Adabas Version 6.1 (or above), VSAM or DB2; VARIABLE requires Adabas Version 6.2 (or above), VSAM or DB2; DYNAMIC requires Adabas Version 7 (or above), or DB2; In a READ .. BY ISN .. statement, the use of DESCENDING, VARIABLE or DYNAMIC is not allowed. In a READ .. IN PHYSICAL SEQUENCE .. statement, the use of DESCENDING or VARIABLE requires VSAM or DB2; DYNAMIC requires DB2. |
Action |
Correct the specified database view or sequence clause. |
Text |
Invalid direction operand specified. |
Explanation |
The field (#DIR) used to control the read direction in a READ ... IN VARIABLE #DIR SEQUENCE ... or READ ... IN DYNAMIC #DIR SEQUENCE ...statement is not correctly specified. The expected format/length is (A1). |
Action |
Check program and correct error. |
Text |
Invalid use or definition of NULL indicator field. |
Explanation |
One of the following situations was encountered:
1. A NULL indicator field (N@..) is not defined in the DDM with
format/length (I2).
2. A NULL indicator field used as a search variable can only be
used with the equal value operator ("=", EQ). Other operations
(like NE, LT, ..) are not permitted.
3. A NULL indicator field must not be used as a sort field in a
FIND .. SORTED BY .. clause.
4. If the FIND statement is generated for DB2 access, the
search value supplied must be a numeric constant.
On mainframe platforms, "@" is the character with the hexadecimal
value H"7C".
|
Action |
Check program and correct error. |
Text |
Incorrect use of WITH REPOSITION clause for .... |
Explanation |
Repositioning in an active loop by using READ ... WITH REPOSITION ... is only allowed for a READ logical statement if the underlying database is Adabas Version 7 (or above), VSAM or DL/I. |
Action |
Remove the WITH REPOSITION clause, or correct the database type definition (see also profile parameter DB). |
Text |
Continue with creation of program after help request. |
Explanation |
This message does not indicate that an error condition exists. It is used only to re-display the last program line for modification, and to indicate that program creation may continue now that the help function was terminated normally. |
Action |
Carry on programming. |
Text |
Online help not available in batch mode. |
Action |
Check program and correct error. |
Text |
Invalid block name specified or block does not exist. |
Action |
Check program and correct error. |
Text |
"SELECT" missing after "UNION". |
Explanation |
The SELECT statement contains the keyword "UNION", which indicates that the SELECT statement is to be continued with a further sub-SELECT. The keyword "UNION" must be followed by the keyword "SELECT", which indicates the beginning of the subsequent sub-SELECT. |
Action |
Correct error in program. |
Text |
"INTO" or "FROM" missing or misplaced. |
Explanation |
The first SELECT statement of a UNION-concatenated SELECT construct must contain an INTO clause after the selection list. Any subsequent SELECT must not contain an INTO clause. |
Action |
Correct error in program. |
Text |
Invalid specification of order element. |
Explanation |
Only integer-type constants and column variables are allowed as order elements. If the SELECT construct includes a "UNION", only integer-type constants or unqualified column names are allowed in ORDER BY. If the SELECT contains receiving dynamic fields, integer-type constants are not allowed, because receiving values might be truncated. |
Action |
Correct error in program. |
Text |
Number of list-1 and list-2 elements do not match. |
Explanation |
The elements of list-1 and list-2 do not match. The number of specified list-1 elements must be the same as the number of list-2 elements. Where a view can be used instead of a list, only the actual data variables are considered, whereas redefined fields and groups are ignored. |
Action |
Correct the number of elements in lists involved in the SQL statement. |
Text |
Invalid expression definition in SELECT list. |
Explanation |
The specified SELECTION-list element is an invalid scalar expression. |
Action |
Correct error in program. |
Text |
Invalid definition of INTO list/indicator variable. |
Explanation |
The specification of an INTO-list variable or an indicator variable is not valid. If an INTO-list variable has either not yet been defined or been defined more than once, Natural requires a proper format/length definition. An indicator variable must be of format/length (B2) or (I2). |
Action |
Correct error in program. |
Text |
Invalid view name definition or view not found. |
Explanation |
The specified view name is invalid or the view is not found in the program. |
Action |
Correct error in program. |
Text |
Invalid scalar-function expression. |
Action |
Correct error in program. |
Text |
Invalid aggregate-function expression. |
Explanation |
The argument specified for a COUNT, SUM, AVG, MAX or MIN function is incorrect. |
Action |
Correct error in program. |
Text |
Invalid table name specified, or database is not DB2. |
Explanation |
The specified table name is not a valid identifier. The database ID of the referenced DDM is not labeled as a DB2 database in the NTDB macro. Another reason for this error may be that the table specification includes an explicit authorization identifier, and the table name contains a hyphen; for example: SELECT ... FROM SQL.SQL-TABLE ... This is invalid. When a table name that contains a hyphen is used, it must not be prefixed with an explicit authorization identifier. |
Action |
Use valid table name; or do not use this statement for this type of database, or contact your Natural administrator. |
Text |
The specified condition is invalid. |
Explanation |
Within the specified search-condition, Natural cannot resolve the specified condition, because the condition does not exist or is specified incompletely or incorrectly. |
Action |
Correct error in program. |
Text |
Invalid condition specified. |
Explanation |
This error may be caused by one of the following situations: - The subquery in an EXISTS condition is specified incorrectly. - For an opening parenthesis in a search-condition, the corresponding closing parenthesis is missing. |
Action |
Correct error in program. |
Text |
Invalid LIKE condition specified. |
Explanation |
One of the "atoms" specified after "LIKE" or after "ESCAPE" in a LIKE condition is invalid: an atom must be a constant or a valid user-defined variable. |
Action |
Correct error in program. |
Text |
Keyword "NULL" missing in "IS <NOT> NULL" condition. |
Action |
Correct error in program. |
Text |
Invalid BETWEEN or IN condition specified. |
Explanation |
This error may be caused by one of the following situations: - The scalar-expression after "BETWEEN" or after "AND" in a BETWEEN condition is invalid. - The keyword "AND" in a BETWEEN condition is missing. - In an IN condition, the specified subquery is invalid, or the specified atoms are invalid, or the list of atoms is not enclosed correctly in parentheses. |
Action |
Correct error in program. |
Text |
Wrong subquery in ALL/ANY/SOME condition. |
Explanation |
The subquery after the keyword "ALL", "ANY" or "SOME" is either missing or incorrect. |
Action |
Correct error in program. |
Text |
Invalid subquery. |
Explanation |
After the opening parenthesis and the keyword "SELECT" in a subquery, the selection or table-expression is missing or invalid, or the closing parenthesis at the end of the subquery is missing. |
Action |
Correct error in program. |
Text |
Invalid column-reference in GROUP BY clause. |
Action |
Correct error in program. |
Text |
Invalid INTO fields for "SELECT *". |
Explanation |
If "SELECT * ..." is used, all variable names specified in the INTO clause must be table variables: - If a view is specified in the INTO clause, all fields defined in that view must be contained in the corresponding table(s). - If individual fields are specified in the INTO clause, all these fields must be contained in the corresponding table(s). |
Action |
Correct error in program. |
Text |
The specified view is empty. |
Explanation |
The view specified in the INTO VIEW clause does not contain any "real" database fields. |
Action |
Correct error in program. |
Text |
Master field for indicator ... not in view. |
Explanation |
The view specified in the INTO clause contains an invalid indicator variable name: If a name of field in a view is prefixed with "L@" or "N@", Natural treats this field as an indicator field, which means that the name following the prefix must be the name of a database field already defined in that view. This master field is missing. On mainframe platforms, "@" is the character with the hexadecimal value H"7C". |
Action |
Correct error in data area. |
Text |
Invalid format/length/range for indicator .... |
Explanation |
The format/length of an INDICATOR or LINDICATOR variable must be either (B2) or (I2). This applies even if the master is not alphanumeric or binary. If you use COMPOPT DB2ARRY=ON, the range of the INDICATOR or LINDICATOR variable has to be equal to or greater than the range of the associated host variable array. |
Action |
Correct error in program. |
Text |
Range variable ... incorrectly specified. |
Explanation |
Possible reasons for this error: 1) A range variable cannot be qualified. 2) The same range variable has been used twice. 3) An alias range variable specified for a view is not assigned to a table. |
Action |
Correct error in program. |
Text |
Indicator variable not allowed as a column reference. |
Explanation |
Special DDM fields with the name prefix N@ or L@ cannot be used as column references, because they are unknown to the database. On mainframe platforms, "@" is the character with the hexadecimal value H"7C". |
Action |
Correct error in program. |
Text |
Field ... must not be used in SELECT or SQL UPDATE view. |
Explanation |
Views referenced in a SELECT or SQL UPDATE statement must not contain periodic-group fields or count-variable fields (C*...), as neither of these are supported by DB2. |
Action |
Remove the above-mentioned fields from the view. |
Text |
User-defined variables not permitted in SELECT list. |
Explanation |
Each field specified in the SELECT list must be either a column of a table specified in the corresponding FROM clause or a constant; user-defined variables are not permitted. |
Action |
Correct error in program. |
Text |
UPDATE only possible with "SELECT * INTO VIEW". |
Explanation |
When you use an UPDATE statement in conjunction with a SELECT statement, the SELECT statement must be of the form "SELECT * INTO VIEW"; with any other form of the SELECT statement, UDPATE is not possible. In reporting mode, you must specify "UPDATE SAME" to update a view read with a SELECT statement; an explicit specification of the columns to be updated is not possible. |
Action |
Use the correct combination of SELECT and UPDATE in the program. |
Text |
Inconsistent setting of parentheses in SELECT UNION. |
Explanation |
The grouping of multiple SELECT expressions that are concatenated with "UNION" contains an error: either there is an opening parenthesis without a corresponding closing parenthesis, or vice versa. |
Action |
Correct error in program. |
Text |
Field ... must be qualified as it exists in both tables. |
Explanation |
The SELECT statement accesses more than one table, and one of the fields referenced is contained in two (or more) tables; the reference is therefore ambiguous. |
Action |
Specify a qualifier with the field. |
Text |
Column ... not found within table. |
Explanation |
The column specified in the SQL statement could not be found in the table specified. |
Action |
Specify a valid or defined column or omit the reference mentioned. |