Natural System Error Messages 3250-3299

#### Search Results

Search

# Natural System Error Messages 3250-3299

#### NAT3250: Function not yet implemented. DB/FNR :1:/:2:.

    Text
    Function not yet implemented. DB/FNR .../....
    Explanation
    Function not yet implemented.
    Action
    Wait for a later version of Adabas.

#### NAT3251: Invalid utility call - versions conflict. DB/FNR :1:/:2:.

    Text
    Invalid utility call - versions conflict. DB/FNR .../....
    Explanation
    Invalid utility call - versions conflict.
    Action
    Check whether utilities and database nuclei are of the same
    version. Contact your nearest support centre.

#### NAT3252: Invalid subroutine call - coding error. DB/FNR :1:/:2:.

    Text
    Invalid subroutine call - coding error. DB/FNR .../....
    Explanation
    Invalid subroutine call - coding error.
    This response may also be returned on setting the NET-WORK timeout via
    Adaset Timeout if NET-WORK is not correctly installed.
    Action
    Contact technical support.

#### NAT3253: System file not loaded or inconsistent. DB/FNR :1:/:2:.

    Text
    System file not loaded or inconsistent. DB/FNR .../....
    Explanation
    System file not loaded or inconsistent.
    Action
    Check the system files by running ADAVFY.

#### NAT3255: Insufficient Adabas resources. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Insufficient Adabas resources. DB/FNR/Subcode .../.../...
    Explanation
    The Adabas command could not be processed because not enough Adabas
    nucleus or operating system resources are available.
    See the Adabas documentation for the explanation of the subcode.
    Action
    Contact your database administrator.

#### NAT3288: Invalid column name list of correlation clause.

    Text
    Invalid column name list of correlation clause.
    Explanation
    The column name list of the correlation clause has to be enclosed
    in round brackets and the column names have to be separated by comma.
    Each column name is a long identifier and has to be unique within
    the column name list.
    Action
    Correct the column name list.

#### NAT3289: Invalid table locator reference in FROM clause.

    Text
    Invalid table locator reference in FROM clause.
    Explanation
    A table locator reference has to conform to the following syntax:
    TABLE ( table̲locator̲variable LIKE table̲name )
    The table̲locator̲variable has to be of format I4.
    The table̲name has to be the name of a valid DB2 DDM.
    Action
    Correct the table locator reference in the FROM clause.

#### NAT3290: Invalid table function reference in FROM clause.

    Text
    Invalid table function reference in FROM clause.
    Explanation
    A table function reference has to conform to the following syntax:
    TABLE ( function̲name ( expr , ... )) correlation̲clause
    Check for matching opening and closing parentheses.
    Table function references must have a correlation clause.
    The function̲name is a long identifier; it can be qualified by a
    schema̲name, which is a short identifier.
    Action
    Correct the table function reference in the FROM clause

#### NAT3291: Invalid CAST expression.

    Text
    Invalid CAST expression.
    Explanation
    A CAST expression has to conform to the following syntax:
    CAST ( expression AS data̲type )
    Check the correct setting of parentheses and keywords. The data̲type
    can be either a built-in data type or a distinct̲type, which is
    a long identifier that can be qualified by a schema name (short
    identifier).
    Action
    Correct the CAST expression.

#### NAT3292: Invalid value specified as QUERYNO.

    Text
    Invalid value specified as QUERYNO.
    Explanation
    The QUERYNO has to be specified as a non-negative integer number.
    Action
    Specify a non-negative integer number as QUERYNO.

#### NAT3293: Content of scroll variable is invalid at offset :1:.

    Text
    Content of scroll variable is invalid at offset ....
    Explanation
    The content of a scroll variable has to conform to the following
    rule: <sensitivity> <direction> <integer>
    - <sensitivity> is optional and can be either INSENSITIVE or SENSITIVE.
    - <direction> can be one of the following: NEXT, PRIOR, FIRST, LAST,
      CURRENT, BEFORE, AFTER, RELATIVE, ABSOLUTE. The default is NEXT.
    - <integer> has to specified if <direction> is RELATIVE or ABSOLUTE.
      It has to be a integer number, like -5 or 0 or 6. It cannot be
      specified with any <direction> other than RELATIVE or ABSOLUTE.
    The specifications of <sensitivity> <direction> <integer>
    have to be separated from one another by one or more spaces.
    Action
    Correct the content of the scroll variable.

#### NAT3294: SENSITIVE STATIC not allowed for READ-ONLY cursors.

    Text
    SENSITIVE STATIC not allowed for READ-ONLY cursors.
    Explanation
    SENSITIVE STATIC SCROLLABLE cursors are only allowed if the associated
    query is not READ-ONLY.
    Queries are READ-ONLY if they contain UNION, GROUP BY, HAVING, or
    nested TABLE expressions, and if they are used in a READ RESULT SET
    statement.
    Action
    Either change the query, or change to INSENSITIVE STATIC SCROLL
    cursors.

#### NAT3295: Conversion of DATE/TIME string :1: failed with error :2:.

    Text
    Conversion of DATE/TIME string ... failed with error ....
    Explanation
    The conversion of a DB2 DATE/TIME string failed with the Natural error
    indicated in this message, because the DATE/TIME string received from
    DB2 could not be converted to a Natural date/time variable.
    This could happen if, for example, a date prior to 01.01.1582
    stored in DB2 is to be placed into a Natural date variable.
    This also occurs if a DB2 TIME string is retrieved which is
    either "00:00 AM" or "24.00.00".
    See the Natural error code for further information.
    Action
    Do not use DATE/TIME strings which cannot be handled by Natural.

#### NAT3296: Limit of successive "not found" conditions exceeded.

    Text
    Limit of successive "not found" conditions exceeded.
    Explanation
    The limit of successive "not found" (SQLCODE +1oo) conditions has been
    exceeded. This occurs if, within a processing loop involving
    scrollable cursors, the number of "not found" conditions exceeds
    its limit. The limit is 5. The processing loop is closed.
    The counter of successive "not found" conditions is reset when a
    condition other than "not found" occurs, or when a terminal I/O occurs.
    The limit check is performed to avoid undesired database loops.
    Action
    Change program logic to avoid this condition.

#### NAT3297: NDB :1: conversion failed with FC :2: / RC :3: :4: :5:

    Text
    NDB :1: conversion failed with FC :2: / RC :3: :4: :5:
    Explanation
    NDB Stored Procedures encoded with UNICODE using Natural alphanumeric
    fields (A) receive UTF8 encoded data which have to be converted to
    EBCDIC. This conversion failed with the specified function and reason
    code. :4: is the destination length, and :5: is the destination length
    necessary to fully convert the UTF8 data to EBCDIC.
    Action
    Contact technical support.

#### NAT3298: Error during Multifetch: :1:.

    Text
    Error during Multifetch: ....
    Explanation
    During creation of the NDB Multifetch buffer (DB2SIZE6) an error
    has occurred; the error message indicates which kind of error.
    Usually, this is a getmain error or an internal error.
    Action
    In the case of a getmain error, either increase the thread size or
    decrease the multifetch factor specified in the program.
    In the case of an internal error, contact Natural support.

#### NAT3299: Rowset positioning requires integer value or variable.

    Text
    Rowset positioning requires integer value or variable.
    Explanation
    The Rowset positioning clause requires the specification of an integer
    value or variable which determines the size (number of rows) of the
    multi-fetch buffer.
    The Rowset positioning clause has the following syntax:
    WITH ROWSET POSITIONING FOR int ROWS
    where "int" can be an integer numeric constant or a variable of
    format/length I4.
    Action
    Correct the Rowset positioning clause accordingly.