Natural System Error Messages 3200-3249

#### Search Results

Search

# Natural System Error Messages 3200-3249

#### NAT3200: Security violation. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Security violation. DB/FNR/Subcode .../.../....
    Explanation
    Security violation detected.
    The following subcodes may be indicated:
     0 Security violation detected.
    31 Authentication check in external security system failed.
    Action
    Supply the correct password and valid credentials for authentication.

#### NAT3201: The specified password was not found. DB/FNR :1:/:2:.

    Text
    The specified password was not found. DB/FNR .../....
    Action
    Check program and correct error, or contact your database administrator.

#### NAT3202: Incorrect Adabas password for secured file. DB/FNR :1:/:2:.

    Text
    Incorrect Adabas password for secured file. DB/FNR .../....
    Explanation
    The specified Adabas password does not allow you to access/update
    the desired Adabas-secured file.
    Adabas backs out any open transaction.
    Action
    Check program and correct error, or contact your database administrator.

#### NAT3204: Password already in use. DB/FNR :1:/:2:.

    Text
    Password already in use. DB/FNR .../....
    Explanation
    The password supplied is already in use.
    Action
    A password name cannot be changed to an existing one.

#### NAT3208: Execute a phase 1 logon. DB/FNR :1:/:2:.

    Text
    Execute a phase 1 logon. DB/FNR .../....
    Explanation
    As an Adabas SAF Security remote user, you should execute a phase 1
    logon. The logon ID and your password are sent to Adabas SAF Security.
    This response indicates that two-phase logon can continue.
    Action
    The platform does not have the correct Adabas link routine
    installed. The response code is intercepted by the workstation
    Adabas link routine and phase 1 logon is performed.

#### NAT3210: Receive buffer lost in NETRDI. DB/FNR :1:/:2:.

    Text
    Receive buffer lost in NETRDI. DB/FNR .../....
    Explanation
    A receive buffer was lost in NETRDI.
    Action
    The DBA may increase the value of the NAB or NC parameter in
    the NETRDI in the target node.

#### NAT3211: Only local utility usage allowed. DB/FNR :1:/:2:.

    Text
    Only local utility usage allowed. DB/FNR .../....
    Explanation
    A remote utility cannot be executed because
    OPTIONS=REMOTE̲UTILITIES is set for the database.
    Action
    Contact the DBA of the remote database.

#### NAT3212: Function not implemented in target architecture. DB/FNR :1:/:2:.

    Text
    Function not implemented in target architecture. DB/FNR .../....
    Explanation
    Function not implemented in the target architecture.
    Action
    Execute the utility on the target node.

#### NAT3215: Adabas version inconsistency. DB/FNR :1:/:2:.

    Text
    Adabas version inconsistency. DB/FNR .../....
    Explanation
    The Adabas interface used by the application program, or the Entire
    Net-Work version used is not supported by the Adabas nucleus.
    Action
    Contact your database administrator.

#### NAT3216: Command rejected by Adabas user exit. DB/FNR :1:/:2:.

    Text
    Command rejected by Adabas user exit. DB/FNR .../....
    Action
    Contact your database administrator.

#### NAT3224: Adabas command timed out by receiving/relay node. DB/FNR :1:/:2:.

    Text
    Adabas command timed out by receiving/relay node. DB/FNR .../....
    Explanation
    The Adabas command has been timed out by the receiving/relay node.
    The request waited for a reply for a longer time period than
    specified by the REPLYTIM= parameter in either the NODE statement
    or the SET operator command. The reply may be delayed or lost due
    to a target malfunction or a connecting link failure.
    Only the setting ADAMODE=0 of the Natural profile parameter ADAMODE
    is supported by Entire Net-Work.
    Action
    Check all connections and correct error, check setting of Natural
    profile parameter ADAMODE, or contact your database administrator.

#### NAT3229: Command queue element ignored, user already active.DB/FNR :1:/:2:

    Text
    Command queue element ignored, user already active.DB/FNR .../....
    Action
    Try again later or cancel the current user.

#### NAT3230: Protocol violation of X/Open XA specification. DB/FNR :1:/:2:.

    Text
    Protocol violation of X/Open XA specification. DB/FNR .../....
    Explanation
    The protocol defined by the X/Open XA specification has
    been violated. This happens, for example, if a user tries
    to issue an ET call for an XA transaction.
    Action
    Follow the XA specification.

#### NAT3231: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3232: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3233: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3234: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3235: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3236: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3237: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3238: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3239: Response code from Adabas user exit.

    Text
    Response code from Adabas user exit.
    Explanation
    This response code is assigned in an Adabas user exit, and its meaning
    is defined by the user.
    One example is the response code in the ADALOG log data field issued by
    user exit 4.
    Action
    Refer to the description of user exits in the Adabas User Exits
    documentation for more information.

#### NAT3241: User exit :3: cannot be loaded. DB/FNR/Error :1:/:2:/:4:.

    Text
    User exit ... cannot be loaded. DB/FNR/Error .../.../....
    Explanation
    The system cannot load the specified user exit, shared library or
    dynamic load library, or the specified function does not exist in this
    shared library or dynamic load library.
    The number of the ADALNK user exit and the system"s error number are
    given in the message.
    Action
    Make sure that you use the correct environment variable for the user
    exit.

#### NAT3242: Double allocation error. DB/FNR :1:/:2:.

    Text
    Double allocation error. DB/FNR .../....
    Explanation
    A double allocation has been detected between two or more files
    or a file and the free space table.
    Action
    Run ADAVFY without any options to find out which parts of which
    files are affected. Contact Software AG support with
    the output from ADAVFY.

#### NAT3243: Invalid FCB extent detected for file. DB/FNR :1:/:2:.

    Text
    Invalid FCB extent detected for file. DB/FNR .../....
    Explanation
    An invalid FCB extent has been detected for a file.
    Action
    Contact your Software AG technical support representative.

#### NAT3245: Pending utility entries in UCB. DB/FNR :1:/:2:.

    Text
    Pending utility entries in UCB. DB/FNR .../....
    Explanation
    Pending utility entries in UCB.
    Action
    Delete the entries with RESET = UCB before executing RECOVER.

#### NAT3246: Utility communication block (UCB) overflow. DB/FNR :1:/:2:.

    Text
    Utility communication block (UCB) overflow. DB/FNR .../....
    Explanation
    Utility communication block (UCB) overflow.
    Action
    Execute the RESET function of ADADBM to remove unused entries
    from the utility communication block.

#### NAT3247: Correct ID not found in communication block. DB/FNR :1:/:2:.

    Text
    Correct ID not found in communication block. DB/FNR .../....
    Explanation
    Correct ID not found in the utility communication block.
    Action
    The utility cannot be restarted. Delete the utility
    communication block entry and re-run the utility.

#### NAT3248: Data-archiving error. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Data-archiving error. DB/FNR/Subcode .../.../....
    Explanation
    This response code is returned by Adabas data-archiving processing.
    See the Adabas data-archiving documentation for more information.
    Action
    Check program and correct error.

#### NAT3249: Response code from Adabas Vista. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Response code from Adabas Vista. DB/FNR/Subcode .../.../....
    Explanation
    See the product documentation for more information.
    Action
    Proceed as indicated in the documentation.