Natural System Error Messages 2650-2699

#### Search Results

Search

# Natural System Error Messages 2650-2699

#### NAT2650: Comment lines range between 0 and 16.

    Text
    Comment lines range between 0 and 16.
    Explanation
    No more than 16 comment lines are supported by Predict. The mimimum
    is zero.
    Action
    Enter a value between zero and 16.

#### NAT2651: If gen. FB = "Y", DSECT = "N" and DS/DC = "DC" must entered.

    Text
    If gen. FB = "Y", DSECT = "N" and DS/DC = "DC" must entered.
    Explanation
    If a format buffer should be generated, then DSECT="N" must be declared
    and the DS/DC option must set to "DC".
    Action
    Enter "N" for DSECT option and "DC" for "DS/DC" option.

#### NAT2652: Format buffer only for file-type "A" or "U".

    Text
    Format buffer only for file-type "A" or "U".
    Explanation
    Format buffers can only be generated for Adabas files or Userviews.
    Action
    Enter "N" for format buffer.

#### NAT2653: File not found.

    Text
    File not found.
    Explanation
    To generate copy code, a valid file name must be entered.
    Action
    Enter a valid file name.

#### NAT2654: Key not allowed for VSAM "RRDS" files.

    Text
    Key not allowed for VSAM "RRDS" files.
    Explanation
    The specification of a descriptor type for a VSAM "RRDS" file is not
    allowed.
    Action
    Use another file organization or delete the specified key.

#### NAT2655: Date is invalid.

    Text
    Date is invalid.
    Explanation
    The entered date has wrong format or values. The date must be
    specified in the following format : JJ-MM-DD.
    Action
    Enter a valid date.

#### NAT2656: Enter "DS" or "DC".

    Text
    Enter "DS" or "DC".
    Explanation
    In the assembler generation, either the "DC" or the "DS" statements are
    used to define storage. Select the desired statement.
    Action
    Enter "DS" or "DC".

#### NAT2657: Enter "Y" or "N".

    Text
    Enter "Y" or "N".
    Explanation
    Only "Y" or "N" allowed for this Input-field.
    Action
    Correct error.

#### NAT2658: Generated code saved.

    Text
    Generated code saved.
    Explanation
    The generated code has been saved as member in the specified library.

#### NAT2659: Code generated in source area.

    Text
    Code generated in source area.
    Explanation
    The generated code is stored in the source area for further editing.
    The GENERATION function terminates successfully.

#### NAT2660: Generation terminated abnormally.

    Text
    Generation terminated abnormally.
    Explanation
    An error occurred during the generation either of COBOL copy code,
    of PL/1 include code, of assembler copy code, or of Data Definition
    Modules. The error has been displayed on the screen preceding
    this message.
    Action
    Correct the error and restart the generation.

#### NAT2661: Duplicate names found.

    Text
    Duplicate names found.
    Explanation
    Duplicate names were found during generation of copy code.
    For example, field names are truncated when they are too long.
    Action
    Correct field names in the file.

#### NAT2662: Copycode generation for conceptual and standard files impossible.

    Text
    Copycode generation for conceptual and standard files impossible.
    Explanation
    An attempt was made to generate copy code for a conceptual or a standard
    file. This is not possible since copy code can be generated only for
    real file types, i.e., Adabas files, Userviews, VSAM, etc.
    Action
    Do not generate copy code for conceptual or standard files.

#### NAT2663: Level increment is a number from 1 to 40.

    Text
    Level increment is a number from 1 to 40.
    Explanation
    The specified level increment must be in the value range 1 thru 40.
    Action
    Correct the value of the level increment.

#### NAT2664: Start level is a number from 1 to 40.

    Text
    Start level is a number from 1 to 40.
    Explanation
    Enter a start level greater than zero.

#### NAT2665: More than one primary key found.

    Text
    More than one primary key found.
    Explanation
    Only one element can be specified as primary key.
    Action
    Modify the primary key definition.

#### NAT2666: No primary key found.

    Text
    No primary key found.
    Explanation
    One primary key must defined for this VSAM file.
    Action
    Specify one primary key.

#### NAT2667: Generated code replaced.

    Text
    Generated code replaced.
    Explanation
    At generation time Predict checks whether the target library / member
    where the generated code is to be stored, exists or not. As you told
    Predict to replace the old code by the recently generated one and
    Predict found an old code, it has been replaced.

#### NAT2668: No files need to be regenerated.

    Text
    No files need to be regenerated.
    Explanation
    No file modified after generation.

#### NAT2669: Format may not be alpha for counter field.

    Text
    Format may not be alpha for counter field.
    Explanation
    A counter field is a numeric field.
    The format must be "N", "P", "U", "B" or "I".
    Action
    Change the format to numeric.

#### NAT2670: Input file is not an USER VIEW or SEQ. file.

    Text
    Input file is not an USER VIEW or SEQ. file.
    Explanation
    In Adabas V5.1 the input data of the ADACMP utility can be described
    as USER VIEW of the Adabas file or as file of type "S" (sequentiell).
    Action
    Enter correct file name.

#### NAT2671: DDM already exists.

    Text
    DDM already exists.
    Explanation
    This message is a warning. It has been issued because REPLACE
    option = "N" has been entered and an older Data Definition Module
    was found. The existing DDM has not been replaced.
    Action
    Enter REPLACE option = "Y".

#### NAT2672: No keys allowed for "PE" or "MU".

    Text
    No keys allowed for "PE" or "MU".
    Explanation
    No key definition for periodic groups and multiple fields in vsam files
    are allowed.
    Action
    Enter blank in the key field.

#### NAT2673: Field is not connected to a standard file.

    Text
    Field is not connected to a standard file.
    Explanation
    If you mark a field as non-standard and the field is not connected
    to a standard file this message will be sent.
    Action
    Delete the non-standard flag.

#### NAT2674: Database number invalid.

    Text
    Database number invalid.
    Explanation
    The Adabas database number must not exceed 254. Database number 255
    are reserved for internal use. In Natural V1.2 the database number 254
    is reserved for the VSAM database.
    Action
    Enter a valid database number.

#### NAT2675: File number (FNR) invalid.

    Text
    File number (FNR) invalid.
    Explanation
    Adabas supports only 255 different files.
    Action
    Enter a number less than 256.

#### NAT2676: Primary sequence field not in file.

    Text
    Primary sequence field not in file.
    Explanation
    The primary sequence field specifies the default descriptor with which
    the file should be read. This field must belong to the file.
    Action
    Correct the primary sequence field.

#### NAT2677: Target database not active.

    Text
    Target database not active.
    Explanation
    The target database must be active if Data Definition Modules are
    generated for it.
    Action
    Initiate the target database.

#### NAT2678: Input file is not a USER VIEW of the Adabas file.

    Text
    Input file is not a USER VIEW of the Adabas file.
    Explanation
    In Adabas V5.1 the input data of the ADACMP utility can be described
    as corresponding USER VIEW of the entered Adabas file.
    Action
    Enter correct INPUT File ID or define input data as USER VIEW of the
    Adabas file or as sequentiell file.

#### NAT2679: File ID must be entered.

    Text
    File ID must be entered.
    Explanation
    The File ID is a mandatory parameter for this function.
    Action
    Enter a valid File ID.

#### NAT2680: Database has no number.

    Text
    Database has no number.
    Explanation
    At GENERATION DDM from a file, the specified database-id
    must have a number, because the DDM depends on the database number.
    If no database-id is entered, database number 0 is set in the DDM.
    In this case the database number will be taken at runtime out of the
    parameter facilities (ADAPARM module, dynam. Natural parameter,..).
    Action
    Enter a database with a valid number or set database-id to BLANK.

#### NAT2681: Primary sequence field is not a descriptor.

    Text
    Primary sequence field is not a descriptor.
    Explanation
    The primary sequence field defines the default descriptor by which
    the file should be read. If the primary sequence field is not a
    descriptor, no valid READ statement results for the default. The
    Data Definition Module was not generated for this reason.
    Action
    Enter a valid primary sequence field, i.e., a descriptor.

#### NAT2682: An Adabas error occurred.

    Text
    An Adabas error occurred.
    Explanation
    The listed Adabas response code occurred.
    Action
    See the DBA.

#### NAT2683: Enter program name or "*".

    Text
    Enter program name or "*".
    Explanation
    If you want to delete the xref data of a program you have to
    specify the program name or "*". The asterisk should be entered
    if preprocessor abends data should be deleted.
    Action
    Enter program name or "*".

#### NAT2684: Missing command.

    Text
    Missing command.
    Explanation
    The conversion for Predict Version 1 data to Predict Version 2 data
    was invoked in batch mode. As no command was supplied the
    command processor isssues this message.
    Action
    Restart the batch session and supply some valid commands.

#### NAT2685: The DDM to be incorporated is not a VSAM DDM.

    Text
    The DDM to be incorporated is not a VSAM DDM.
    Explanation
    You have tried to incorporate a DDM which is not of type VSAM.
    Action
    Check type of DDM.

#### NAT2686: File is not security protected.

    Text
    File is not security protected.
    Explanation
    The file is not security protected. Therefore, no security definitions
    can be generated.
    Action
    Do not generate security definitions for unprotected files.

#### NAT2687: Source field for sub-/super-descriptor not in DDM.

    Text
    Source field for sub-/super-descriptor not in DDM.
    Explanation
    The field specified in the sub-/super-descriptor definition is not
    defined as field in the DDM. The sub-/super-descriptor is only
    allowed to refer fields defined in the DDM.
    Action
    Check source field names of the sub-/super-descriptor.

#### NAT2688: File is of wrong type.

    Text
    File is of wrong type.
    Explanation
    Data Definition Modules can only be generated for Adabas files
    and Userviews of the Adabas file or VSAM files and their Userviews.
    Action
    (only files of type "A","U","V","R","L" or "W" allowed)
    Enter a valid file.

#### NAT2689: Max. 90 sub-/super-descriptors can be incorporated.

    Text
    Max. 90 sub-/super-descriptors can be incorporated.
    Explanation
    The incorporated VSAM DDM contains more than 90 sub-/super-descriptors.
    Only 90 descriptors can be incorporated.

#### NAT2690: File is not an Adabas file.

    Text
    File is not an Adabas file.
    Explanation
    The generation of ADAWAN/ADACMP or Adabas security definitions
    can only be executed for Adabas files.
    Action
    Check file type.

#### NAT2691: Only F, FB, V, VB, U or blank allowed.

    Text
    Only F, FB, V, VB, U or blank allowed.
    Explanation
    The RECORD FORMAT at GENERATION ADAWAN/ADACMP definitions must be:
        F---fixed
        FB--fixed blocked
        V---variable
        VB--variable blocked
        U---unblocked
       " "--not specified
    Action
    Correct error.

#### NAT2692: Duplicate file record found.

    Text
    Duplicate file record found.
    Explanation
    Predict does not allow duplicate names within the same object types
    This message is issued, if such an inconsistency is encountered.
    The duplicate records are deleted by the MIGRATE utility
    during the unload file process.
    Action
    Unload and load your file by the MIGRATE utility.

#### NAT2693: Security definition already exists.

    Text
    Security definition already exists.
    Explanation
    If you want to generate a DDM for which a security definition exists
    this message will be sent.
    Action
    Change security definiton if necessary.

#### NAT2694: Cipher-code must be entered.

    Text
    Cipher-code must be entered.
    Explanation
    The data should be loaded into the database in ciphered form.
    Action
    Enter cipher-code or contact your DBA.

#### NAT2695: The specified objects have been unloaded successfully.

    Text
    The specified objects have been unloaded successfully.
    Explanation
    The objects have been unloaded successfully to work file 1.

#### NAT2696: No object was found.

    Text
    No object was found.
    Explanation
    To perform an unload or a load, an Object ID and an object type must be
    entered. No objects that meet the conditions were found.

#### NAT2697: Cipher-code is not allowed.

    Text
    Cipher-code is not allowed.
    Explanation
    The data should not be laoded into the database in ciphered form.
    Action
    Reset cipher-code or contact your DBA.

#### NAT2698: Field length in VSAM file different to field length user view.

    Text
    Field length in VSAM file different to field length user view.
    Explanation
    Generally no format overwrite is allowed when using VSAM files. However,
    you may define an alphanumeric field in a user view  which is shorter
    than the original field, but never a longer one. Numeric fields must
    have the same attributes as the master field.
    Action
    Correct error.

#### NAT2699: Format defined in VSAM file is of a different type.

    Text
    Format defined in VSAM file is of a different type.
    Explanation
    When defining a VSAM user view the format of the field can"t be
    changed, it has to be the same as the format of the field in the master
    file.
    Action
    Do not change the format of a field in a user view of a VSAM file.