Natural System Error Messages 0450-0499

#### Search Results

Search

# Natural System Error Messages 0450-0499

#### NAT0450: Not enough memory to run C subroutines.

    Text
    Not enough memory to run C subroutines.
    Action
    This is an internal Natural Expert error, please contact
    Software AG.

#### NAT0451: Entire DB Request Handler cannot be found.

    Text
    Entire DB Request Handler cannot be found.
    Explanation
    The Entire DB Request Handler (NATDREQ) is not linked to Natural.
    Action
    Check the link job and re-link the Natural nucleus with module
    AERNAT5 included.

#### NAT0452: Entire cannot be initialized.

    Text
    Entire cannot be initialized.
    Explanation
    The cause is either that
    - there was not enough space to satisfy the request;
    - the Entire buffer (ZSIZE) is too small - minimum is 44;
    - the Adabas/Entire nucleus (AERNUC) is not accessible, because it
      is not linked or cannot be loaded dynamically.
    Action
    Contact your Entire DB administrator.

#### NAT0454: Relocatability error in Entire DB.

    Text
    Relocatability error in Entire DB.
    Action
    Check program and correct error.

#### NAT0455: First command to Entire not "DLOGON".

    Text
    First command to Entire not "DLOGON".
    Explanation
    Before accessing the Entire data in any way, a DLOGON statement
    must be successfully executed. This allows the user identity to
    be determined, the application to be set, and security check and
    accessibility of data to be determined.
    Action
    Ensure that the system calls a DLOGON before access, and correct code.

#### NAT0456: Invalid function code for Entire.

    Text
    Invalid function code for Entire.
    Explanation
    Entire has received a control block (same format as Adabas) which
    has a function code field (offset 2 in the CB) that cannot be
    interpreted by Entire.
    This is most likely caused by an incompatibility of systems and/or
    overwriting of the Entire work area.
    Action
    Produce an application dump and contact Software AG support.

#### NAT0457: Entire version incompatibility.

    Text
    Entire version incompatibility.
    Explanation
    This is caused by linking the interface CSECT DDIPFNAT (AERNUC)
    with another version of the initialization module ADDINIT (AERNAT).
    Action
    Check the Natural/Entire link job for "INCLUDE" datasets,
    or contact your system administrator.

#### NAT0458: No "RETAIN AS" set with the given name exists.

    Text
    No "RETAIN AS" set with the given name exists.
    Explanation
    This occurs when, for example, a FIND references a non-existent
    or released ISN set. See FIND statement, RETAIN clause, in the
    Entire DB Programmer"s Guide for further information.
    Action
    Make sure that usage of ISN sets in application program is correct.

#### NAT0459: Control Block is not aligned.

    Text
    Control Block is not aligned.
    Explanation
    The Control Block in direct command must be full-word aligned.
    Action
    Check the program and align the Control Block.

#### NAT0460: Record length is greater than Open length.

    Text
    Record length is greater than Open length.
    Explanation
    Entire DB has attempted to write a record via EXPORT/IMPORT to work
    file 1. This work file has already been opened with a record of
    length less than 4096 bytes.
    Action
    Check program for reads/writes and make sure that the first read or
    write is at least 4096 bytes. Alternatively, check the DCB.

#### NAT0461: Error in CONTROL clause of DEFINE WINDOW statement.

    Text
    Error in CONTROL clause of DEFINE WINDOW statement.
    Explanation
    The CONTROL clause of the DEFINE WINDOW statement must be specified
    as follows:
        CONTROL SCREEN, or
        CONTROL WINDOW.
    If the CONTROL clause is omitted, CONTROL WINDOW will apply by default.
    Action
    Check program and correct error.

#### NAT0462: Error in SYMBOL clause of DEFINE WINDOW statement.

    Text
    Error in SYMBOL clause of DEFINE WINDOW statement.
    Explanation
    See the Natural documentation for the correct syntax of the DEFINE
    WINDOW statement.
    Action
    Check program and correct error.

#### NAT0463: Invalid color or invalid attribute specified.

    Text
    Invalid color or invalid attribute specified.
    Explanation
    You have specified an invalid attribute or an invalid color code,
    either in the REVERSED clause or the FRAMED clause of the DEFINE WINDOW
    statement.
    The only attribute you may specify in a REVERSED or FRAMED clause
    is CD (color definition).
    The color definition must be specified as (CD=cc), where "cc" is the
    color code. For information on valid color codes, see
    the Natural documentation.
    Action
    Check program and correct error.

#### NAT0464: Window name in DEFINE/SET WINDOW missing or invalid.

    Text
    Window name in DEFINE/SET WINDOW stmt. missing or invalid.
    Explanation
    In a DEFINE/SET WINDOW statement, the name of the window
    must be specified directly after the keywords "DEFINE/SET WINDOW".
    For window names, the same rules apply as for names of user-defined
    variables (as described in the Natural documentation).
    Action
    Check program and correct error.

#### NAT0465: Inconsistent usage of WINDOW :1:.

    Text
    Inconsistent usage of WINDOW ....
    Explanation
    Either the window name has been defined twice in two
           DEFINE WINDOW statements.
    or     a window is referenced in the program (e.g. with
           an INPUT WINDOW statement), but the window has
           not been defined in a DEFINE WINDOW statement.
    Action
    Check program and correct error.

#### NAT0466: Error in SIZE clause of DEFINE WINDOW statement.

    Text
    Error in SIZE clause of DEFINE WINDOW statement.
    Explanation
    The SIZE clause of a DEFINE WINDOW statement must be specified
    as one of the following:
       SIZE AUTO
       SIZE QUARTER
       SIZE lines * columns
    If the SIZE clause is omitted, SIZE AUTO will apply by default.
    For an explanation of the DEFINE WINDOW syntax, see the
    Natural documentation.
    Action
    Check program and correct error.

#### NAT0467: Error in BASE clause of DEFINE WINDOW statement.

    Text
    Error in BASE clause of DEFINE WINDOW statement.
    Explanation
    The BASE clause of the DEFINE WINDOW statement must be specified as
    one of the following:
    - BASE CURSOR
    - BASE TOP LEFT
    - BASE TOP RIGHT
    - BASE BOTTOM LEFT
    - BASE BOTTOM RIGHT
    - BASE line-position / column-position
    If the BASE clause is omitted, BASE CURSOR will apply by default.
    For an explanation of the DEFINE WINDOW syntax, see the Natural
    documentation.
    Action
    Check program and correct error.

#### NAT0468: Error in TITLE clause of DEFINE WINDOW statement.

    Text
    Error in TITLE clause of DEFINE WINDOW statement.
    Explanation
    In the TITLE clause of a DEFINE WINDOW statement, an alphanumeric
    variable or constant must be specified immediately after the keyword
    "TITLE".
    Action
    Check program and correct error.

#### NAT0469: CLOSE WORK FILE statement has been invalidly placed.

    Text
    CLOSE WORK FILE statement has been invalidly placed.
    Explanation
    A CLOSE WORK FILE statement must not be placed within
    a READ WORK FILE loop that refers to the same work file.
    Action
    Place the CLOSE WORK FILE statement outside the READ WORK FILE loop.

#### NAT0470: Operand for RET, SORTKEY or VAL function is not valid.

    Text
    Operand for RET, SORTKEY or VAL function is not valid.
    Explanation
    The operand for RET, SORTKEY or VAL must be alphanumeric. In addition,
    the length of the SORTKEY operand should not exceed 253.
    Action
    Specify an alphanumeric program name with the RET function.
    Do not apply the system function SORTKEY or VAL to a non-alphanumeric
    field. Ensure the length of the SORTKEY operand does not exceed 253.

#### NAT0471: Invalid operands in SUBSTRING option.

    Text
    Invalid operands in SUBSTRING option.
    Explanation
    The field name specified in the SUBSTRING option must have
    alphanumeric (A), binary (B) or Unicode (U) format.
    The starting position in the field and the length of the substring must
    be numeric. They must not position beyond the physical length of the
    underlying field.
    Action
    Correct error in program.

#### NAT0472: This user-defined name is a Natural reserved word.

    Text
    This user-defined name is a Natural reserved word.
    Explanation
    The Natural profile parameter KC=ON (keyword check) has been set,
    which means that a user-defined name (identifier) must not be the
    same as a Natural reserved word.
    Action
    Use a different name.

#### NAT0473: Error in parameter of DEFINE PRINTER statement.

    Text
    Error in parameter of DEFINE PRINTER statement.
    Explanation
    This error occurs if one of the following conditions is not met:
    - The operand after "PROFILE", "FORMS" or "NAME" must be of
      alphanumeric format, and its length must not exceed 8.
    - The operand after "DISP" must be of
      alphanumeric format, and its length must not exceed 4.
    - The operand after "COPIES" must be a numeric integer
      (format N, P or I; without decimal digits).
    - Each of the above clauses must not be specified more than once.
    Action
    Correct error in program.

#### NAT0474: Field attribute DF cannot be used for this type of field.

    Text
    Field attribute DF cannot be used for this type of field.
    Explanation
    The field attribute DF can only be used for fields of
    type date.
    Action
    Correct error in program.

#### NAT0475: INCLUDE statements must be nested on less than 20 levels.

    Text
    INCLUDE statements must be nested on less than 20 levels.
    Explanation
    This program has INCLUDE statements nested on at least 20 levels.
    Action
    Reduce the number of levels on which INCLUDE statements are nested to
    less than 20.

#### NAT0476: Data size of :1: must not exceed :2:.

    Text
    Data size of ... must not exceed ....
    Explanation
    The size of a variable or a data structure exceeds the
    maximum size allowed.
    Action
    Reduce the size of the variable or data structure.

#### NAT0477: Numeric value supplied is out of valid range :1:.

    Text
    Numeric value supplied is out of valid range ....
    Explanation
    The value specified is out of the permitted bounds.
    Action
    Supply a correct numeric value.

#### NAT0478: Incorrect usage or specification of CODEPAGE clause.

    Text
    Incorrect usage or specification of CODEPAGE clause.
    Explanation
    The CODEPAGE clause can only be used for operands of format A or B.
    Action
    Correct error in program.

#### NAT0479: Invalid operand type combination in MOVE ENCODED statement.

    Text
    Invalid operand type combination in MOVE ENCODED statement.
    Explanation
    The MOVE ENCODED statement is used to convert data from one code page
    encoding into another encoding. Therefore you have to either supply one
    of the operands as an alphanumeric or binary field with a CODEPAGE
    clause appended, or specify one operand as alphanumeric or binary
    and the other operand as type Unicode.
    Valid operand combinations are:
        MOVE ENCODED A/B IN CODEPAGE <cp1>  TO  U
        MOVE ENCODED A/B IN CODEPAGE <cp1>  TO  A/B
        MOVE ENCODED A/B IN CODEPAGE <cp1>  TO  A/B IN CODEPAGE <cp2>
        MOVE ENCODED U                      TO  A/B IN CODEPAGE <cp2>
        MOVE ENCODED A/B                    TO  A/B IN CODEPAGE <cp2>
        MOVE ENCODED U                      TO  A/B
        MOVE ENCODED A/B                    TO  U
    Action
    Correct error in program.

#### NAT0480: Incorrect usage of field attribute SB.

    Text
    Incorrect usage of field attribute SB.
    Explanation
    A selection-box clause (SB=..) may only be used for alphanumeric fields.
    Moreover,
    - the parameter fields specified have to be alphanumeric as well,
    - the number of parameter fields must not exceed 20.
    A selection-box clause (SB=..) must NOT be used for
    - fields defined as named constants (see CONST clause in DEFINE DATA),
    - system variables (e.g. *PROGRAM, *COM),
    - multiple-value fields (e.g. #ARRAY(1:10)).
    Action
    Check program and correct error.

#### NAT0481: Multiple usage of a SB= or RB= clause not permitted.

    Text
    Multiple usage of a SB= or RB= clause not permitted.
    Explanation
    You may not define more than one Selection-Box (SB=..) or
    Radio-Button (RB=..) clause for an INPUT field.
    Action
    Check program and correct error.

#### NAT0482: Length indicator cannot be referenced in UPDATE or STORE.

    Text
    Length indicator cannot be referenced in UPDATE or STORE.
    Explanation
    A length indicator field may be used to retrieve the length of an Adabas
    Long-Alpha or LOB field (LA/LOB) in a read (READ/FIND) operation.
    It must not be referenced in a view used in a STORE or UPDATE statement.
    Example: DEFINE DATA LOCAL
             1 V1 V1 VIEW OF MYFILE
               2  L@LA-FIELD (I4)         <-- Length indicator field
               2  LA-FIELD   (A) DYNAMIC
             END-DEFINE
             STORE V1
    If an LA or LOB field is part of the STORE/UPDATE field list,the
    corresponding length field information is automatically added by the
    Natural runtime system, based on the current length of the dynamic
    variable. To prevent a duplicate length setting for the same
    LA/LOB field, length fields are not allowed in the STORE/UPDATE fields.
    Action
    LA/LOB field, length fields are not allowed in the STORE/UPDATE fields.
    Remove length fields from data view used in UPDATE or STORE.

#### NAT0483: Index missing for sub-/super-descriptor field :1:.

    Text
    Index missing for sub-/super-descriptor field ....
    Explanation
    A sub-/super-descriptor field containing a periodic-group field (or
    parts thereof) was specified in a data view without index. This is not
    permitted by Adabas for database calls other than HISTOGRAM (L9). With
    a HISTOGRAM you cannot read more than a single field. This view
    definition consists of multiple fields and thus cannot be used for a
    HISTOGRAM. Furthermore, due to the missing index, it cannot be used for
    other database calls.
    What to do?
    1. Reduce the number of view fields to only the sub-/super-descriptor
       - without index to make the view usable for HISTOGRAM only;
       - with an index to make the view usable for all browsing statements.
    2. If multiple fields are defined in the view, supply an index or
       index-range for the sub-/super-descriptor to make it usable for all
       database browsing statements other than HISTOGRAM.
    Action
       database browsing statements other than HISTOGRAM.
    See description.

#### NAT0484: Field structure of view :1: only usable for HISTOGRAM.

    Text
    Field structure of view ... only usable for HISTOGRAM.
    Explanation
    The view referenced is only applicable to a HISTOGRAM statement, as
    it consists of only a single sub-/super-descriptor field containing a
    periodic-group field (or parts thereof) without an index specification.
    This is not permitted by Adabas and will cause Adabas errors when used
    with a database statement other than HISTOGRAM.
    Action
    Supply index or index-range for the sub-/super-descriptor field,
    or use the view only for HISTOGRAM statements.

#### NAT0485: Incorrect use of WITH SHARED HOLD MODE=C in :1: at line :2:.

    Text
    Incorrect use of WITH SHARED HOLD MODE=C in ... at line ....
    Explanation
    When a WITH SHARED HOLD MODE=C option is used in a READ/FIND, a record
    being read is only returned to the caller if it is not in exclusive
    hold status by another user at the time of the record fetch. The record
    is not put in hold status by this operation.
    This conflicts with the use of a DELETE/UPDATE statement which refers to
    the READ/FIND including the WITH SHARED HOLD MODE=C option, because the
    execution of a DELETE/UPDATE requires for the underlying record to be
    in hold status.
    Action
    Do not use WITH SHARED HOLD MODE=C option in a READ/FIND if the record
    received is updated or deleted.

#### NAT0486: Error in READLOB/UPDATELOB statement. Reason code :1:.

    Text
    Error in READLOB/UPDATELOB statement. Reason code ....
    Explanation
    Reason codes:
    01: No WITH ISN clause specified, but a default reference could not
        be found.
    02: Auto-referenced statement has no *ISN.
    03: Auto-referenced statement accesses different DBID/FNR.
    04: Incorrect view name specified.
    05: Specified view does not contain a field.
    06: View field is no LOB field.
    07: View field must be of format Alpha/Binary/Unicode with a fixed
        (non "dynamic") length.
    08: View field not unique in view.
    Action
    Check program and correct error.

#### NAT0487: END-READLOB missing for READLOB in line :1:.

    Text
    END-READLOB missing for READLOB in line ....
    Explanation
    In structured mode, a READLOB statement must be terminated by a
    corresponding END-READLOB statement.
    Example:
      READLOB ...
        DISPLAY
        COMPUTE ...
      END-READLOB
    Action
    Supply END-READLOB to close the READLOB loop.