Natural System Error Messages 3201-3250

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.

NAT3203: User not authorized to access secured file. DB/FNR :1:/:2:.

Text

User not authorized to access secured file. DB/FNR .../....

Explanation

The file to be accessed is protected by Adabas Security.
To delete a record from that file, you must provide the correct
Adabas password.
Adabas backs out any open transaction.

Action

Check program and correct error, or contact your database administrator.

NAT3204: The password pool has overflowed. DB/FNR :1:/:2:.

Text	The password pool has overflowed. DB/FNR .../....
Action	Contact your database administrator.

NAT3207: Logon phase 1 completed for Adabas ESI interface. DB/FNR :1:/:2:.

Text	Logon phase 1 completed for Adabas ESI interface. DB/FNR .../....
Explanation	The Adabas ESI interface completed phase 1 of logon and requested phase 2.
Action	Send a phase-2 logon request to ADAESI.

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

Text

Execute a phase 1 logon. DB/FNR .../....

Explanation

As an ESI remote user, you should execute a phase 1
logon. The logon ID and your password will be sent
to ADAESI.

Action

Platform does not have the correct Adabas link routine
installed. Response code is intercepted by workstation
Adabas link routine and phase 1 logon is performed.

NAT3209: Adabas External-Security-Interface detects an expired password.

Text

Adabas External-Security-Interface detects an expired password.

Explanation

Adabas ESI (External Security Interface) detects an expired password
on the server.

Action

Refer to "Adabas Nucleus Messages and Codes" for more information.
Contact your database administrator.

NAT3210: Internal error. DB/FNR/Net-Work ID :1:/:2:/:3:.

Text

Internal error. DB/FNR/Net-Work ID .../.../....

Explanation

The logical ID is greater than 255.









For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.

Action

Contact your database administrator.

NAT3211: Internal error. DB/FNR/Net-Work ID :1:/:2:/:3:.

Text

Internal error. DB/FNR/Net-Work ID .../.../....

Explanation

An invalid ID table index was detected in the user buffer.









For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.

Action

Contact your database administrator.

NAT3212: Invalid I/O buffer for internal Adabas command. DB/FNR :1:/:2:.

Text

Invalid I/O buffer for internal Adabas command. DB/FNR .../....

Explanation

For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.

Action

Contact your database administrator.

NAT3213: ID table not found. DB/FNR/Subc/NW-ID :1:/:2:/:3:/:4:.

Text

ID table not found. DB/FNR/Subc/NW-ID .../.../.../....

Explanation

The Adabas installation procedure was not properly executed,
especially the Adabas SVC.
The subcode describes the reason of the error.
If you were running with Entire Net-Work, NW-ID contains the ID of
the Entire Net-Work node that issued this response code.

Action

Contact your database administrator.

NAT3214: Internal command issued from ADA V4 ADALINK. DB/FNR :1:/:2:.

Text	Internal command issued from ADA V4 ADALINK. DB/FNR .../....
Action	Contact your database administrator.

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. DB/FNR :1:/:2: Net-Work ID :3:.

Text	Command rejected. DB/FNR .../... Net-Work ID ....
Explanation	The command has been rejected by the Adabas user exit.
Action	Contact your database administrator.

NAT3217: Command rejected. DB/FNR :1:/:2: Net-Work ID :3:.

Text	Command rejected. DB/FNR .../... Net-Work ID ....
Explanation	The command has been rejected by the Adabas user exit.
Action	Contact your database administrator.

NAT3218: Response code from Link Routine. DB/FNR/Subc :1:/:2:/:3:.

Text

Response code from Link Routine. DB/FNR/Subc .../.../....

Explanation

Response code from the Link Routine. DB/FNR/Subc .../.../....

For the detailed reason, see the subcode.

Action

Contact your database administrator.

NAT3219: Response code from ATM. DB/FNR/Subcode :1:/:2:/:3:.

Text

Response code from ATM. DB/FNR/Subcode .../.../....

Explanation

This response code should only occur when Adabas Transaction Manager
is being used.
2 The global transaction does not have the status that allows the call.
3 No transaction ID (XID) entries exist.
4 The 'R' and 'J' options are not supported; or this is not a global
  transaction. The transaction ID (XID) either does not exist or cannot
  be found (for example, when the given XID does not belong to the UQE).
5 The record or value buffer definition may be invalid
  (for example, the length size may be invalid);
  or the value buffer content may be invalid
  (for example, it may not contain a valid transaction ID (XID)).
6 The user is not an update or ET user or is already involved in a
  global transaction.
For further subcodes, see the Adabas documentation

Action

Check program and correct error.

NAT3220: Request rejected by Entire Net-Work. DB/FNR/NW :1:/:2:/:3:.

Text

Request was rejected by Entire Net-Work. DB/FNR/NW .../.../....

Explanation

The request was rejected by Entire Net-Work due to a shortage of short
term buffers.
DB/FNR/Net-Work ID .../.../....

Action

For z/OS and z/VSE, increase the region size.
For BS2000, check the address space limit.

NAT3221: Receiving node intercepted ABEND during SVC 4-call.DB/FNR :1:/:2:

Text

Receiving node intercepted ABEND during SVC 4-call.DB/FNR .../....

Explanation

The receiving node intercepted an abnormal termination during the
Adabas SVC 4-call for the command.

Action

Contact your database administrator.

NAT3222: No CQE could be allocated on a relay node. DB/FNR :1:/:2:.

Text

No CQE could be allocated on a relay node. DB/FNR .../....

Explanation

No CQE could be allocated on a relay node
(same as Natural error NAT3151 on a receiving node).

Action

Contact your database administrator.

NAT3223: CTCS response code: node loop. DB/FNR :1:/:2:.

Text	CTCS response code: node loop. 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.

NAT3225: Response code from Server. DB/FNR/Subcode :1:/:2:/:3:.

Text

Response code from Server. DB/FNR/Subcode .../.../....

Explanation

A command was issued from a server, such as an Adabas nucleus, to
another server, such as Entire Net-Work.
DB/FNR/Subcode .../.../....
The command did not complete within the prescribed time period.
The issuer proceeds and no longer expects a response to the command.

Action

See the Entire Net-Work documentation for more
information on these response codes.

NAT3226: Response code from Entire Net-Work.

Text	Response code from Entire Net-Work.
Explanation	Response code from Entire Net-Work.
Action	See the Entire Net-Work documentation for more information on the meanings and use of these response codes.

NAT3227: Response code from Entire Net-Work.

Text	Response code from Entire Net-Work.
Explanation	Response code from Entire Net-Work.
Action	See the Entire Net-Work documentation for more information on the meanings and use of these response codes.

NAT3228: SVC or database not UES-enabled. DB/FNR/Subcode :1:/:2:/:3:.

Text

SVC or database not UES-enabled. DB/FNR/Subcode .../.../....

Explanation

ADALCO is UES-enabled, but
 - the SVC is not UES-enabled (the subcode in Additions 2
   is x'01'), or
 - the target database is not UES-enabled (the subcode in
   Additions 2 is x'02').

Action

Make sure that Adabas and the SVC are at the V712 level and
that the database is UES-enabled.

NAT3229: This response code is reserved for Entire Net-Work.

Text

This response code is reserved for Entire Net-Work.

Explanation

This response code is reserved for Entire Net-Work.

Action

See the Entire Net-Work documentation for further
information on this response code.

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.

NAT3240: ATM encountered error :3:. DB/FNR/Subcode :1:/:2:/:4:.

Text

ATM encountered error .... DB/FNR/Subcode .../.../....

Explanation

ATM encountered an error. The error code can be found in the
Additions 2 field of the Adabas control block. The response code
may be in the first two bytes of the Additions 2 field.

Action

Check the meaning of the error code. If the cause of the problem
is not apparent, contact your Software AG technical support
representative.

NAT3241: ATM received response code :3:. DB/FNR/Subc. :1:/:2:/:4:.

Text

ATM received response code .... DB/FNR/Subc. .../.../....

Explanation

ATM received an unexpected Adabas response code. The
subcode and response code can be found, in that order,
in the Additions 2 field of the Adabas control block.
If a negative value appears in the Additions 2 field,
take its complement: this is the response code
returned to the proxy by ATM.

For non-mainframe systems, see the Adabas documentation for
response codes.

Action

Check the meaning of the Adabas response code and subcode.
If the cause of the problem is not apparent, contact your
Software AG technical support representative.

NAT3242: ATM transaction status error :3:. DB/FNR/Subcode :1:/:2:/:4:.

Text

ATM transaction status error .... DB/FNR/Subcode .../.../....

Explanation

ATM or the TM proxy was unable to determine the status of
the caller's transaction. There might be an ATM error
code in the Additions 2 field of the Adabas control block,
in the low-order (rightmost) two bytes.

For non-mainframe systems, see the Adabas documentation for
response codes.

Action

Check the meaning of the error code, if present. Otherwise,
determine the status of the transaction using online services.
If the action required is not apparent, contact Software AG support.

NAT3243: ATM unsolicited syncpoint request. DB/FNR/Subc. :1:/:2:/:3:.

Text

ATM unsolicited syncpoint request. DB/FNR/Subc. .../.../....

Explanation

ATM or the TM proxy received an unsolicited syncpoint
request. The action taken or the status of the global
transaction that was open is indicated by a subcode in
the Additions 2 field of the Adabas control block, in
the low-order (rightmost) two bytes.

For non-mainframe systems, see the Adabas documentation for
response codes.

Action

Review the TMSYNCMGR and TRNCTL parameters in the ATM
parameter module.

NAT3244: Response code returned by Adabas Transaction Manager.

Text	Response code returned by Adabas Transaction Manager.
Explanation	Response code returned by Adabas Transaction Manager.
Action	See the Adabas Transaction Manager documentation for more information.

NAT3245: Response code from COR. DB/FNR/Subcode :1:/:2:/:3:.

Text

Response code from COR. DB/FNR/Subcode .../.../....

Explanation

This response code is issued for communication problems between add-on
products that use the system coordinator (COR) interface to Adabas; that
is, Adabas Fastpath, Adabas Vista, Adabas SAF Security, and Adabas
Transaction Manager. Subcodes:
1 - Internal error.
2 - A required module could not be loaded. This is probably an
    installation error.



For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.

Action

For subcode 1, contact your Software AG technical support
representative. For subcode 2, consult the installation instructions
for the add-on product.

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	Contact your database administrator.

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	Contact your database administrator.

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

Text

Data-archiving error. DB/FNR/Sub .../.../....

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 :1:/:2: Subcode :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.

NAT3250: The ACBX validation failed. DB/FNR/Subcode :1:/:2:/:3:.

Text

The ACBX validation failed. DB/FNR/Subcode .../.../....

Explanation

The ACBX validation failed.

Possible subcodes:

Subcode Description
   1    Unsupported ACBX version.
   2    ADACBX provided without UBE.
   3    ACBX file number > 65,535.
   4    Reserved field not zero.
   5    ACBX length incorrect.

For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.

Action

Contact your database administrator.