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 .../....
Actn.	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 .../....

Expl.

The specified Adabas password does not allow you to access/update
the desired Adabas secured file.
Adabas backs out any open transaction.

Actn.

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 .../....

Expl.

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.

Actn.

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 .../....
Expl.	The password supplied is already in use.
Actn.	A password name cannot be changed to an existing one.

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

Text	Logon phase 1 completed for Adabas ESI interface. DB/FNR .../....
Expl.	The Adabas ESI interface completed phase 1 of logon and requested phase 2.
Actn.	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 .../....

Expl.

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

Actn.

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 .../....
Expl.	A receive buffer was lost in NETRDI.
Actn.	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 .../....
Expl.	A remote utility cannot be executed because OPTIONS=REMOTE̲UTILITIES is set for the database.
Actn.	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 .../....
Expl.	Function not implemented in the target architecture.
Actn.	Execute the utility on the target node.

NAT3213: ID table not found; SVC not properly installed. DB/FNR :1:/:2:.

Text	ID table not found; SVC not properly installed. DB/FNR .../....
Expl.	The Adabas installation procedure was not properly executed.
Actn.	Inform 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 .../....
Actn.	Contact your database administrator.

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

Text	Adabas version inconsistency. DB/FNR .../....
Expl.	SVC 04/16 call received from Adabas Version 4 ADALINK, with Adabas Version 5 user buffer or AMODE=31.
Actn.	Contact your database administrator.

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

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

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

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

NAT3218: Not enough memory to allocate user buffer. DB/FNR :1:/:2:.

Text	Not enough memory to allocate user buffer. DB/FNR .../....
Expl.	The program/utility has to be run again in a larger region/partition.
Actn.	Contact your database administrator.

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

Text

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

Expl.

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

Actn.

Check program and correct error.

NAT3220: Receiving/relay node unable to allocate buffer. DB/FNR :1:/:2:.

Text

Receiving/relay node unable to allocate buffer. DB/FNR .../....

Expl.

The receiving/relay node was unable to allocate a buffer to read
the command.
If this response is recurrent, the size of the receiving/relay node"s
Attached Buffer pool should be increased (see the execution parameter
NAB in the NET-WORK CTCS documentation).

Actn.

Contact your database administrator.

NAT3221: Receiving node intercepted abend at SVC 4-call. DB/FNR :1:/:2:.

Text

Receiving node intercepted abend at SVC 4-call. DB/FNR .../....

Expl.

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

Actn.

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 .../....

Expl.

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

Actn.

Contact your database administrator.

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

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

Expl.

The Adabas command has been timed out by the receiving/relay node.

Actn.

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

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

Text

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

Expl.

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.

Actn.

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.
Expl.	Response code from Entire Net-Work.
Actn.	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.
Expl.	Response code from Entire Net-Work.
Actn.	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 .../.../....

Expl.

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").

Actn.

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

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

Text	Command queue element ignored, user already active.DB/FNR .../....
Actn.	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 .../....

Expl.

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.

Actn.

Follow the XA specification.

NAT3231: Response code from Adabas user exit.

Text

Response code from Adabas user exit.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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.

Expl.

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.

Actn.

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 .../.../....

Expl.

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.

Actn.

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. .../.../....

Expl.

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.

Actn.

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: Double allocation error. DB/FNR :1:/:2:.

Text

Double allocation error. DB/FNR .../....

Expl.

A double allocation has been detected between two or more files
or a file and the free space table.

Actn.

Run ADAVFY without any options to find out which parts of which
files are affected. Contact your nearest support centre 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 .../....
Expl.	An invalid FCB extent has been detected for a file.
Actn.	Contact your nearest support centre.

NAT3244: Overflow in checkpoint block (CPB). DB/FNR :1:/:2:.

Text	Overflow in checkpoint block (CPB). DB/FNR .../....
Expl.	Overflow in checkpoint block (CPB).
Actn.	Start the nucleus to process the entries in the checkpoint block.

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

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

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

Text

Utility communicaton block (UCB) overflow. DB/FNR .../....

Expl.

Utility communication block (UCB) overflow.

Actn.

Execute the RESET function of ADADBM to remove unused entries
from the utility communication block.

NAT3247: Correct ID not found in UCB. DB/FNR :1:/:2:.

Text

Correct ID not found in UCB. DB/FNR .../....

Expl.

Correct ID not found in the utility communication block.

Actn.

The utility cannot be restarted. Delete the utility
communication block entry and re-run the utility.

NAT3248: User PID not found in user queue. DB/FNR :1:/:2:.

Text	User PID not found in user queue. DB/FNR .../....
Expl.	User PID not found in the user queue.
Actn.	Supply the correct PID.

NAT3249: User TID not found in user queue. DB/FNR :1:/:2:.

Text	User TID not found in user queue. DB/FNR .../....
Expl.	User TID not found in the user queue.
Actn.	Supply the correct TID.

NAT3250: Function not yet implemented. DB/FNR :1:/:2:.

Text	Function not yet implemented. DB/FNR .../....
Expl.	Function not yet implemented.
Actn.	Wait for a later version of Adabas.