Version 6.3.13 for Windows
 —  Messages and Codes  —

Natural System Error Messages 0651-0700

NAT0651: Number of parameters (:1: / :2:) do not match.

Text Number of parameters (CALLNAT NBR/SUBPGM NBR) do not match.
Expl. The number of parameters defined in the referenced subprogram
and supplied in the CALLNAT do not match.

NAT0652: Sequence clause not valid for :1:.

Text Sequence clause not valid for ....
Expl. 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.
Actn. Correct the specified database view or sequence clause.

NAT0653: Invalid direction operand specified.

Text Invalid direction operand specified.
Expl. 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).
Actn. Check program and correct error.

NAT0654: Invalid use or definition of NULL indicator field.

Text Invalid use or definition of NULL indicator field.
Expl. 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 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 may not be used as sort field in a
FIND .. SORTED BY .. clause.
4. If the FIND statement is generated for a DB2 access, the
search value supplied must be a numeric constant.

NAT0655: Incorrect use of WITH REPOSITION clause for :1:.

Text Incorrect use of WITH REPOSITION clause for ....
Expl. 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.
Actn. Remove the WITH REPOSITION clause, or correct the database type
definition (see also profile parameter DB).

NAT0666: Continue with creation of program after help request.

Text Continue with creation of program after help request.
Expl. 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.
Actn. Carry on programming.

NAT0667: Online help not available in batch mode.

Text Online help not available in batch mode.
Actn. Check program and correct error.

NAT0668: Invalid block name specified or block does not exist.

Text Invalid block name specified or block does not exist.
Actn. Check program and correct error.

NAT0670: "SELECT" missing after "UNION".

Text "SELECT" missing after "UNION".
Expl. 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.
Actn. Correct error in program.

NAT0671: "INTO" or "FROM" missing or misplaced.

Text "INTO" or "FROM" missing or misplaced.
Expl. 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.
Actn. Correct error in program.

NAT0672: Invalid specification of order element.

Text Invalid specification of order element.
Expl. Only integer-type constants and column variables are allowed as
order elements.
If the SELECT construct includes a "UNION", only integer-type
constants are allowed.
If the SELECT contains receiving dynamic fields, integer-type
constants are not allowed, because receiving values might be
truncated.
Actn. Correct error in program.

NAT0673: Number of :1: and :2: elements do not match.

Text Number of list-1 and list-2 elements do not match.
Expl. 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.
Actn. Correct the number of elements in lists involved in the SQL statement.

NAT0674: Invalid expression definition in SELECT list.

Text Invalid expression definition in SELECT list.
Expl. The specified SELECTION-list element is an invalid scalar expression.
Actn. Correct error in program.

NAT0675: Invalid definition of INTO list/indicator variable.

Text Invalid definition of INTO list/indicator variable.
Expl. 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).
Actn. Correct error in program.

NAT0676: Invalid view name definition or view not found.

Text Invalid view name definition or view not found.
Expl. The specified view name is invalid or the view is not found in the
program.
Actn. Correct error in program.

NAT0677: Invalid scalar-function expression.

Text Invalid scalar-function expression.
Actn. Correct error in program.

NAT0678: Invalid aggregate-function expression.

Text Invalid aggregate-function expression.
Expl. The argument specified for a COUNT, SUM, AVG, MAX or MIN function
is incorrect.
Actn. Correct error in program.

NAT0679: Invalid table name specified, or database is not DB2.

Text Invalid table name specified, or database is not DB2.
Expl. 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.
Actn. Use valid table name; or do not use this statement for this type
of database, or contact your Natural administrator.

NAT0680: The specified condition is invalid.

Text The specified condition is invalid.
Expl. Within the specified search-condition, Natural cannot resolve the
specified condition, because the condition does not exist or is
specified incompletely or incorrectly.
Actn. Correct error in program.

NAT0681: Invalid condition specified.

Text Invalid condition specified.
Expl. 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.
Actn. Correct error in program.

NAT0682: Invalid LIKE condition specified.

Text Invalid LIKE condition specified.
Expl. 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.
Actn. Correct error in program.

NAT0683: Keyword "NULL" missing in "IS <NOT> NULL" condition.

Text Keyword "NULL" missing in "IS <NOT> NULL" condition.
Actn. Correct error in program.

NAT0684: Invalid BETWEEN or IN condition specified.

Text Invalid BETWEEN or IN condition specified.
Expl. 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.
Actn. Correct error in program.

NAT0685: Wrong subquery in ALL/ANY/SOME condition.

Text Wrong subquery in ALL/ANY/SOME condition.
Expl. The subquery after the keyword "ALL", "ANY" or "SOME" is
either missing or incorrect.
Actn. Correct error in program.

NAT0686: Invalid subquery.

Text Invalid subquery.
Expl. 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.
Actn. Correct error in program.

NAT0687: Invalid column-reference in GROUP BY clause.

Text Invalid column-reference in GROUP BY clause.
Actn. Correct error in program.

NAT0688: Invalid INTO fields for "SELECT *".

Text Invalid INTO fields for "SELECT *".
Expl. 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).
Actn. Correct error in program.

NAT0689: The specified view is empty.

Text The specified view is empty.
Expl. The view specified in the INTO VIEW clause does not contain any
"real" database fields.
Actn. Correct error in program.

NAT0690: Master field for indicator :1: not in view.

Text Master field for indicator ... not in view.
Expl. The view specified in the INTO clause contains an invalid indicator
variable name: when 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.
Actn. Correct error in data area.

NAT0691: Invalid format/length def. for indicator :1:.

Text Invalid format/length def. for indic. variable ....
Expl. 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.
Actn. Correct error in program.

NAT0692: Range variable :1: incorrectly specified.

Text Range variable ... incorrectly specified.
Expl. 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.
Actn. Correct error in program.

NAT0693: Indicator variable not allowed as a column reference.

Text Indicator variable not allowed as a column reference.
Expl. Special DDM fields with the name prefix N§ or L§ cannot be used as
column references because they are unknown to the database.
Actn. Correct error in program.

NAT0694: Field :1: must not be used in SELECT or SQL UPDATE view.

Text Field ... must not be used in SELECT or SQL UPDATE view.
Expl. 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.
Actn. Remove the above-mentioned fields from the view.

NAT0695: User-defined variables not permitted in SELECT list.

Text User-defined variables not permitted in SELECT list.
Expl. 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.
Actn. Correct error in program.

NAT0696: UPDATE only possible with "SELECT * INTO VIEW".

Text UPDATE only possible with "SELECT * INTO VIEW".
Expl. 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.
Actn. Use the correct combination of SELECT and UPDATE in the program.

NAT0697: Inconsistent setting of parentheses in SELECT UNION.

Text Inconsistent setting of parentheses in SELECT UNION.
Expl. 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.
Actn. Correct error in program.

NAT0698: Field :1: must be qualified as it exists in both tables.

Text Field ... must be qualified as it exists in both tables.
Expl. 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.
Actn. Specify a qualifier with the field.

NAT0699: Column :1: not found within table.

Text Column ... not found within table.
Expl. The column specified in the SQL statement could not be found
in the table specified.
Actn. Specify a valid or defined column or omit the reference mentioned.

NAT0700: Keyword "SET" missing or invalid range-variable specified.

Text Keyword "SET" missing or invalid range-variable specified.
Expl. In the SQL UPDATE statement after the table specification, either
the keyword "SET" is missing, or the range-variable is incorrect.
Actn. Correct error in program.

Top of page