Natural System Error Messages 6100-6149

#### Search Results

Search

# Natural System Error Messages 6100-6149

#### NAT6100: Duplicate names check when deleting a version.

    Text
    Duplicate names check when deleting a version.
    Explanation
    The Entire DB nucleus detected an unexpected situation which
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB, terminate the Natural session
    and start a new one. Try to reproduce the error with DU=ON to get
    a dump and contact technical support.

#### NAT6102: Attempt to store library dependent occ. in GLOBAL-LIB.

    Text
    Attempted to store library-dependent occurrence in GLOBAL-LIBRARY.
    Explanation
    It is not possible to store library-dependent occurrences in the
    GLOBAL-LIBRARY. A DLOGON statement may be missing.
    Action
    Check program and correct error.

#### NAT6103: Attempt to TRANSFER a not validated version of an ERE.

    Text
    Attempted to TRANSFER a not validated version of an ERE.
    Explanation
    It is not validated, if there are mandatory attributes that
    have no values. In this case, TRANSFER is not allowed.
    Action
    Update entity to be transferred so that it is validated
    and retry.

#### NAT6104: Error when requesting/freeing memory.

    Text
    Error when requesting memory.
    Explanation
    "IMPORT", "EXPORT", and CATTAB generation each require additional
    memory. This memory was not available.
    Action
    Enlarge region size.

#### NAT6105: Extension record reference in model.

    Text
    Extension record reference in model.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6106: Workfile has not been allocated.

    Text
    Workfile has not been allocated.
    Explanation
    IMPORT and EXPORT require Workfile 1.
    Action
    Check and correct JCL and rerun job.

#### NAT6107: Security code in internal format is too long.

    Text
    Security code in internal format is too long.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6108: Category for UPDATE/STORE not validated.

    Text
    Category for UPDATE/STORE not validated.
    Explanation
    The category is not validated, unless all definitions required
    for the attributes of this category are made.
    Action
    Contact your Entire DB administrator.

#### NAT6109: I/O error during workfile access.

    Text
    I/O error during workfile access for EXPORT/IMPORT.
    Explanation
    The physical damage of the file is a possible reason.
    Action
    Contact your Entire DB administrator.

#### NAT6111: Domain sublist in domain sublist.

    Text
    Domain sublist in domain sublist.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6113: No ")" or continuation of display-list.

    Text
    No ")" or continuation of display-list.
    Explanation
    A direct call or a FIND NATIVE was issued with a syntax error
    in the Search Buffer.
    Action
    Check program and correct error.

#### NAT6117: Universal linkage attribute in domain sublist.

    Text
    Universal linkage attribute in domain sublist.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6118: Category is not validated.

    Text
    Category is not validated.
    Explanation
    Response code of LF command for a category that is not validated.
    The category is not validated, unless all definitions required
    for the attributes of this category are made.
    Action
    Make the missing definitions.

#### NAT6119: Unmatching category and ERE references.

    Text
    Unmatching category and ERE references.
    Explanation
    In a STORE/UPDATE statement, either the category reference of a
    linkage attribute exists but no ERE reference, or the indices for
    category and ERE reference do not match.
    Action
    Check program and correct error.

#### NAT6120: No reference, value or subtree in CAT-REF.

    Text
    No reference, value or subtree in CAT-REF.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6122: Record to be deleted is locked.

    Text
    Record to be deleted is locked.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6123: Category specified for linkage attribute does not exist.

    Text
    Category specified for linkage attribute does not exist.
    Explanation
    In STORE/UPDATE statements, the category specified for a linkage
    attribute does not exist.
    Action
    Check program and correct error.

#### NAT6124: Category specified for linkage attribute is not allowed.

    Text
    Category specified for linkage attribute does not exist.
    Explanation
    Category specified for a linkage attribute does not match
    those categories defined as domain for the linkage attribute.
    Action
    Check program and correct error.

#### NAT6125: No domain reference in AD node in attr.

    Text
    No domain reference in AD node in attr.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6126: DV- or AD-node expected.

    Text
    DV- or AD-node expected.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6127: Domain is not defined.

    Text
    Domain is not defined.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6128: No reference to new model category.

    Text
    No reference to new model category.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6129: Restrictions not allowed (model has not been validated).

    Text
    Restrictions not allowed (model has not been validated).
    Explanation
    This error should occur only in internal Entire DB statements
    used in Entire DB ONLINE SERVICES and in Entire DB utilities.
    Action
    If this error occurs in a "normal" statement, contact technical support.

#### NAT6130: Version has no library node.

    Text
    Version has no library node.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6131: Expected node not found.

    Text
    Expected node not found.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6132: RESTORE not allowed in Top-Level-Library.

    Text
    RESTORE not allowed in Top-Level-Library.
    Explanation
    Probably, DLOGON for the correct library is missing.
    Action
    Check program and correct error.

#### NAT6133: ERE could not be validated.

    Text
    ERE could not be validated.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6134: No category specified for universal attribute.

    Text
    No category specified for universal linkage attribute.
    Explanation
    For universal linkage attributes, references to EREs of
    all entity categories are allowed. If only the name of the
    EREs is specified, Entire DB cannot decide to which
    category the referenced ERE belongs.
    Action
    Check program and correct error.

#### NAT6135: Missing CHANGED-BY node.

    Text
    Missing CHANGED-BY node.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a dump
    and contact technical support.

#### NAT6136: "REFERENCED" or "REFERENCING" without "RECURSIVELY" expe.

    Text
    "REFERENCED" or "REFERENCING" without "RECURSIVELY" expe.
    Explanation
    A direct call or a FIND NATIVE was issued with a syntax error
    in the Search Buffer.
    Action
    Check program and correct error.

#### NAT6137: "VERSIONS" not allowed here, will not be processed.

    Text
    "VERSIONS" not allowed here, will not be processed.
    Explanation
    A direct call or a FIND NATIVE was issued with a syntax error
    in the Search Buffer.
    Action
    Check program and correct error.

#### NAT6138: Syntax-unit is not number or ")".

    Text
    Syntax-unit is not number or ")".
    Explanation
    A direct call or a FIND NATIVE was issued with a syntax error
    in the Search Buffer.
    Action
    Check program and correct error.

#### NAT6139: Syntax-unit is name or ISN of a group attribute.

    Text
    Syntax unit in Search Buffer is name or ISN of a group attribute.
    Explanation
    This error may occur after a DLOGON to a library in an
    environment which contains other categories than expected by
    the program. It may occur as well, if a direct call with an
    incorrect search value buffer has been performed.
    Action
    Use the PRODUCT clause of the DLOGON statement to prevent access
    to an environment with invalid categories. In case of an invalid
    direct call, check program and correct error.

#### NAT6140: Too many relation elements entered for relation.

    Text
    Too many relation elements entered for relation.
    Explanation
    This error should occur only in internal Entire DB statements
    used in Entire DB ONLINE SERVICES and in Entire DB utilities.
    Action
    If this error occurs in a "normal" statement, contact technical support.

#### NAT6141: Missing component sublist in category RELATION-ELEMENTS.

    Text
    Missing component sublist in category RELATION-ELEMENTS.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6142: Illegal node in component sublist of cat RELATION-ELEMENTS.

    Text
    Illegal node in component sublist of cat RELATION-ELEMENTS.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6143: Attribute input for relation did not match.

    Text
    Attribute input for relation did not match.
    Explanation
    This error should occur only in internal Entire DB statements
    used in Entire DB ONLINE SERVICES and in Entire DB utilities.
    Action
    If this error occurs in a "normal" statement, contact technical support.

#### NAT6144: Not enough room left for creation of perm ERE.

    Text
    Not enough room left for creation of perm ERE.
    Explanation
    This error should occur only in internal Entire DB statements
    used in Entire DB ONLINE SERVICES and in Entire DB utilities.
    Action
    If this error occurs in a "normal" statement, contact technical support.

#### NAT6145: Illegal number of sublists in temporary AD-node.

    Text
    Illegal number of sublists in temporary AD-node.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6146: Category sublist expected in model but not found.

    Text
    Category sublist expected in model but not found.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6147: Domain sublist expected in model but not found.

    Text
    Domain sublist expected in model but not found.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6148: Incompatible offsets (model and temporary node).

    Text
    Incompatible offsets (model and temporary node).
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.

#### NAT6149: Premature end of sublist in model.

    Text
    Premature end of sublist in model.
    Explanation
    The Entire DB nucleus detected an unexpected situation, that
    probably resulted from an error in the Entire DB nucleus.
    Action
    To continue work with Entire DB terminate Natural session
    and begin a new one. Try to reproduce the error with DU=ON to get a
    dump and contact technical support.