Natural System Error Messages 0650-0699

#### Search Results

Search

# Natural System Error Messages 0650-0699

#### NAT0650: Incorrect comparator used in READ/HISTOGRAM for :1:.

    Text
    Incorrect comparator used in READ/HISTOGRAM for ....
    Explanation
    The comparators LT, GT, LE and GE cannot be used with the
    database type you are using.
    When the comparator LT, GT, LE or GE is used in a READ/HISTOGRAM
    statement, the underlying database has to be Adabas Version 7 (or
    above), VSAM, DL/I or Db2.
    Moreover, when a Super Natural user file is accessed, the comparators
    LT, GT, LE and GE are not applicable.
    For details as to which statements support which database
    types, see the Natural documentation.
    Action
    Check program and correct error.

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

    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.

#### NAT0652: Sequence clause not valid for :1:.

    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 or VARIABLE requires Adabas Version 8.6 (or above);
      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.

#### NAT0653: Invalid direction operand specified.

    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.

#### NAT0654: Invalid use or definition of NULL indicator field.

    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.

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

    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).

#### NAT0656: Specified column :1: of ORDER BY clause is not unique.

    Text
    Specified column ... of ORDER BY clause is not unique.
    Explanation
    Column names specified within the ORDER BY clause must be
    unique within the select column list.
    Action
    Either define a unique name using the AS clause within the select
    column list and use this name or specify the number representing the
    position of the column within the select column list as order criteria.

#### NAT0657: Join-expression operands belong to same set of tables.

    Text
    Join-expression operands belong to same set of tables.
    Explanation
    The join-expression operands on different sides of the
    join-expression must belong to separate sets of joined-tables.
    Action
    Correct the join-expression so that the join-expression operands
    belong to separate tables.

#### NAT0658: Indicator variable not allowed for dynamic text variables.

    Text
    Indicator variable not allowed for dynamic text variables.
    Explanation
    The specification of indicator variables for dynamic text variables
    is not allowed.
    Action
    Remove the indicator variable from the dynamic text variable.

#### NAT0659: Illegal use of keyword UR within the WITH clause.

    Text
    Illegal use of keyword UR within the WITH clause.
    Explanation
    The specification of "WITH UR" is only valid in select statements.
    In DELETE, UPDATE, and INSERT statements, the WITH clause can
    be specified only with the keyword CS or RR.
    Action
    Change the keyword in the WITH clause to either CS or RR or
    else omit the WITH clause.

#### NAT0660: Time-stamp inconsistency for segments of GDA :1:.

    Text
    Time-stamp inconsistency for segments of GDA ....
    Explanation
    The object and symbol table of a GDA were loaded, but their time
    stamps differ. Using such inconsistent GDA segments would cause
    odd compiler malfunctions.
    Usually both items should have the same creation time stamp, because
    they are built at the same time when a GDA is cataloged.
    The inconsistency be due to the GDA having been cataloged at
    almost the same time in different Natural sessions which do not
    share the same buffer pool.
    Action
    Remove the GDA object and the symbol table from buffer pool with the
    SYSBPM utility. Then retry to catalog the program.

#### NAT0661: Restored joinlists level/layer doesn"t match actual layer.

    Text
    Restored joinlists level/layer doesn"t match actual layer.
    Explanation
    An internal compiler error occurred.
    For processing nested joined-tables, the compiler saves the
    joinlists with the context of the select level/layer on a stack.
    While restoring such a saved joinlist entry, the compiler
    detected that the actual level/layer did not match the saved
    select level/layer.
    This indicates that compiler processing in erroneous.
    Action
    Contact customer service.

#### NAT0662: Too many tables used in SELECT statement.

    Text
    Too many tables used in SELECT statement.
    Explanation
    The compiler can only process a maximum of 256 tables
    within one SQL statement. This limit has been exceeded.
    Action
    Use fewer tables in the SELECT statement.

#### NAT0663: Internal error: compiler detected a select level of zero.

    Text
    Internal error: compiler detected a select level of zero.
    Explanation
    The compiler detected a select level of zero, although this
    value should always be greater than zero.
    This is the result of an internal error.
    Action
    Contact customer service.

#### NAT0664: Nesting level of SELECT clauses exceeds maximum.

    Text
    Nesting level of SELECT clauses exceeds maximum.
    Explanation
    The compiler can only process SELECT statements which have
    a SELECT clause nesting level of ten or less.
    Action
    Do not nest SELECT clauses more than ten times.

#### NAT0665: Too many SELECT statements on a single nesting level.

    Text
    Too many SELECT statements on a single nesting level.
    Explanation
    The compiler can only process up to 255 SELECT statements on
    a single level of nested SELECT statements.
    Action
    Reduce the number of SELECT statements on a single level.

#### NAT0666: Continue with creation of program after help request.

    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.

#### NAT0667: Online help not available in batch mode.

    Text
    Online help not available in batch mode.
    Action
    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.
    Action
    Check program and correct error.

#### NAT0669: The symbol table (SYT) of the GDA :1: could not be loaded.

    Text
    The symbol table (SYT) of the GDA ... could not be loaded.
    Explanation
    During compilation, the symbol table of the GDA referenced in the
    DEFINE DATA GLOBAL statement must be loaded.
    The load request failed and the compiler could not continue.
    Possible reason:
    The symbol table of the GDA object was removed when it was
    transferred with SYSOBJH/INPL.
    Action
    Provide a GDA including the symbol table.

#### NAT0670: "SELECT" missing after "UNION".

    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.

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

    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.

#### NAT0672: Invalid specification of order element.

    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.

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

    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.

#### NAT0674: Invalid expression definition in SELECT list.

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

#### NAT0675: Invalid definition of INTO list/indicator variable.

    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.

#### NAT0676: Invalid view name definition or view not found.

    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.

#### NAT0677: Invalid scalar-function expression.

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

#### NAT0678: Invalid aggregate-function expression.

    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.

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

    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.

#### NAT0680: The specified condition is invalid.

    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.

#### NAT0681: Invalid condition specified.

    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.

#### NAT0682: Invalid LIKE condition specified.

    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.

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

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

#### NAT0684: Invalid BETWEEN or IN condition specified.

    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.

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

    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.

#### NAT0686: Invalid subquery.

    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.

#### NAT0687: Invalid column-reference in GROUP BY clause.

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

#### NAT0688: Invalid INTO fields for "SELECT *".

    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.

#### NAT0689: The specified view is empty.

    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.

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

    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.

#### NAT0691: Invalid format/length/range for indicator :1:.

    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.

#### NAT0692: Range variable :1: incorrectly specified.

    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.

#### NAT0693: Indicator variable not allowed as a column reference.

    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 z/OS, "@" is the character with the hexadecimalvalue H"7C".
    Action
    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.
    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.

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

    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.

#### NAT0697: Inconsistent setting of parentheses in SELECT UNION.

    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.

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

    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.

#### NAT0699: Column :1: not found within table.

    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.