Version 4.2.6 for Mainframes
 —  Messages and Codes  —

Natural System Error Messages 3601-3650

NAT3601: Updating the distribution key of a master file is not allowed.

Text Updating the distribution key of a master file is not allowed.
Expl. If a distribution key is defined for a master file, it may
be contained in any view used to update the master file,
but the distribution key field itself may not be updated.
Actn. Use a sequence of DELETE and STORE statements instead of UPDATE
in the application programs to update the distribution key field.

NAT3602: Using more than one log file in a transaction not allowed.

Text Using more than one log file in a transaction not allowed.
Expl. The "Verify transaction consistency during logging" field is set
to "Y" (yes) and two or more master files that were updated
in the same transaction have different log files assigned.
Action: Either set the "Verify transaction consistency ..." field
to "N" using the MODIFY SYSPROF function or modify your master file
definitions so that all master files that are updated in a single
transaction have the same log file assigned.

NAT3603: Concurrent updates to more than one database are not allowed.

Text Concurrent updates to more than one database are not allowed.
Expl. It is not allowed to update master files that are contained in
different databases in the same transaction. Transaction
consistency cannot be guaranteed for such operations.
Actn. Change the application programs so that a transaction contains
only updates to a single database.

NAT3604: Length of format buffer or record buffer exceeds allowed maximum.

Text Length of format buffer or record buffer exceeds allowed maximum.
Expl. Format and record buffer for an update call logged by ETP
may not exceed a maximum value.
Actn. Split your Natural views or the format and record buffers
supplied by a 3GL program into smaller portions and issue
multiple Adabas calls.

NAT3605: Administration file is not defined.

Text Administration file is not defined.
Expl. To use ETP, an administration file has to be assigned to
logical file number 200 for Natural applications. For 3GL
applications, the administration file has to be specified
as a parameter for an initialization call to the ETP 3GL
interface.
ACTION: For a Natural application, use the Natural LFILE parameter
or the NTFILE macro to specify the ETP administration file.
Actn. or the NTFILE macro to specify the ETP administration file. For a 3GL application, specify the administration file
correctly in the ETP 3GL interface initialization call.

NAT3606: GETMAIN failed for ETPSIZE.

Text GETMAIN failed for ETPSIZE.
Expl. For an NTDB macro or for the Natural DB parameter, the ETP option
is specified for at least one database.
Entire Transaction Propagator (ETP) is not be able to run, because
the required storage could not be obtained.
Actn. Restart Natural in a larger environment:
Increase your region size or increase the size of your Natural thread
when running in a thread environment.

NAT3607: Error during start of asynchronous task after ET.

Text Error during start of asynchronous task after ET.
Expl. After an Adabas ET command, ETP tried to start an asynchronous
task because the definition of a master file that was updated
in the completed transaction requested so. The program that was
executed ended with an error.
Actn. Check the task name specified in the ETP system profile.
Verify that a transaction with that name is in a library
that is accessible from the current TP monitor session.

NAT3608: The ETP identification record is invalid or missing.

Text The ETP identification record is invalid or missing.
Expl. When invoked for the first time, the ETP maintenance utility
writes an identification record into the administration file,
which is never deleted by ETP.
If the error occurred during logging of transactions, the ETP
identification record has been deleted, but other information in
the administration file still exists.
If the error occurred when you invoked the ETP maintenance
utility, you attempted to access an ETP administration file
with an old version of the ETP maintenance utility after it
had been accessed with a newer version.
ACTION: If the error occurred during logging of transactions,
invoke the ETP maintenance utility and verify that all
information contained in the administration file is still correct.
Actn. information contained in the administration file is still correct. If the error occurred when you invoked the ETP maintenance utility,
use only the newer version of the maintenance utility to access
the administration file.

NAT3609: Invalid ISNQ value for S1 cmd on obtaining replicate ISN.

Text Invalid ISNQ value for S1 cmd on obtaining replicate ISN.
Expl. The file definition requested that the criterion used to replicate
records is the distribution key defined for the replicate"s master
file. The distribution key must be a unique descriptor. To replicate
the record, the ISN of the record in the replicate file is retrieved.
For N1 calls (STORE), no record with that key may be present. For
A1/E1 (UPDATE/DELETE), exactly one record with that key must be present.
As the record"s ISN was retrieved, ETP encountered an invalid ISNQ
value, meaning that for an N1 a record with the key already existed
or for an A1/E1 command either no or more than one record with that
key exists in the replicate file.
The reason for this error is usually that an application program
modified the replicate file (which is not allowed) or Adabas
utilities were used to modify the replicate file.
Actn. utilities were used to modify the replicate file. Re-initialize the replicate file from the master file as described
in the manual and, if necessary, correct your application programs.

NAT3610: Overflow of master file table.

Text Overflow of master file table.
Expl. The limit of 512 master files for a specific database was exceeded.
Actn. Contact your Entire Transaction Propagator administrator.

NAT3611: Overflow of log file table.

Text Overflow of log file table.
Expl. The limit of 512 log files for a specific database was exceeded.
Actn. Contact your Entire Transaction Propagator administrator.

NAT3625: No Natural MBCS handler available.

Text No Natural MBCS handler available.
Expl. The Natural MBCS handler is not available.
Possible reasons are:
- The MBCS handler module is not linked to Natural or cannot be loaded.
- An error occurred during the initialization of the Natural MBCS.
Actn. Depends on the reason of the error. If an initialization error has
occurred, check the session initialization error messages.

NAT3626: Invalid version of Natural nucleus.

Text Invalid version of Natural nucleus.
Expl. The version of the Natural nucleus module does not correspond to the
Natural MBCS handler.
Actn. Link the correct Natural nucleus; or specify a correct shared nucleus
name, using the profile parameter NUCNAME.

NAT3627: Unsupported operating system or version.

Text Unsupported operating system or version.
Expl. The current operating-system version is not supported by this
Natural MBCS handler.
Actn. See Natural documentation for supported operating system and version
for the Natural MBCS handler.

NAT3628: Outline editor requires delimiter class D defined in map.

Text Outline editor requires delimiter class D defined in map.
Expl. The definition of delimiter class D in a map (see map settings)
is a prerequisite for using the outline editor.
Actn. Run migration program or define delimiter class D in the map.

Top of page