Natural System Error Messages 3400-3449

NAT3400: No :1: database handler available.

Text
No ... database handler available.
Explanation
A specific database handler is assigned to handle the database.
However, the database handler requested is not available.
Possible reason are:
- the database handler module isn"t linked to Natural
- the session profile parameter for the buffer size of the database
  handler is zero
- an error occurred during initialization of the database handler
- the wrong database handler has been specified for the database,
  either by macro NTDB in the parameter module or by the DB parameter
Action
Depends on the reason of the error. If an initialization error had
occurred, check the session initialization error messages.

NAT3401: NAT object STOWed for :1: but executed under :2:.

Text
NAT object STOWed for ... but executed under ....
Explanation
The DBID used when stowing the Natural object is assigned
to database type .1. but at runtime this DBID is assigned
to database type .2.
Action
The DBID used at stow time and at runtime must be assigned to
the same database type.

NAT3402: Unknown DB response code :4:. DB/FNR/Subcode :1:/:2:/:3:.

Text
Unknown DB response code .... DB/FNR/Subcode .../.../....
Explanation
An unknown response code was received from the Adabas interface.
Action
Check program and correct error.

NAT3403: ADAMODE was changed from :1: to :2:.

Text
ADAMODE was changed from :1: to :2:.
Explanation
Natural was started with ADAMODE=:1:.
This mode is not supported by the database, or Natural could not
allocate the resources required to execute in this mode.
Natural has switched automatically to ADAMODE=:2:.
The original error message, the technical reason, was issued prior to
this message, and can be viewed with the LASTMSG command.
Action
Contact your Natural/Adabas administrator.

NAT3410: No Natural ICU handler available.

Text
No Natural ICU handler available.
Explanation
The Natural ICU handler is not available.
Possible reasons are:
- The ICU handler module is not linked to Natural or cannot be loaded.
- The session profile parameter CFICU is set to OFF.
- An error occurred during the initialization of the Natural ICU.
Action
Depends on the reason of the error. If an initialization error has
occurred, check the session initialization error messages.

NAT3411: Code page :1: not available.

Text
Code page ... not available.
Explanation
ICU (International Components for Unicode) is the engine to support
code pages and Unicode in Natural.
Code pages are defined in ICU in a data file that is linked to the
nucleus or loaded dynamically. If the code page is not available,
it is not part of the data file used.
Action
Please contact Software AG support.

NAT3412: Internal error from ICU: :1:.

Text
Internal error from ICU: ....
Explanation
ICU (International Components for Unicode) is the engine to support
code pages and Unicode in Natural.
Possible reasons for internal errors of ICU are:
- memory allocation errors,
- internal program errors,
- corrupted definition files of converters,
- missing resources in data files.
Action
Please contact Software AG support.

NAT3413: Conversion error, at least 1 code point not translated. H":1:"

Text
Conversion error, at least 1 code point not translated. H".."
Explanation
If, during Unicode conversion or the conversion from one code page
to another, a code point or character cannot be converted to the
desired destination code page, a code-page-specific substitution
character is used instead.
The generation of this message depends on the CPCVERR=ON/OFF option
in the SET GLOBALS statement.
The first failed code point of the source string is displayed in
hexadecimal format at the end of the message.
Action
Check the content of the input/target field of the conversion.

NAT3414: ICU STEPLIB DSN :1: cannot be loaded.

Text
SAGICU STEPLIB DSN ... cannot be loaded.
Explanation
The value of the STEPLIB parameter gives the name of the load dataset
that contains the SAGICU data items. This dataset will be loaded
dynamically at session start.
Possible reasons:
- The dataset to be loaded dynamically does not exist.
- Validation of the dataset name has failed.
  The dataset naming rules by IBM state the following:
  A dataset name consists of one or more parts connected by periods.
  Each part is called a qualifier. Each qualifier must begin with an
  alphabetic character (A to Z) or the special character @, #, or $.
  The remaining characters in each qualifier can be alphabetic, special,
  or numeric (0 to 9) characters. Each qualifier must be 1-8 characters
  in length. The maximum length of a complete dataset name is 44
  characters, including the periods.
Action
  characters, including the periods.
The dataset specified by CFICU=(STEPLIB=xxx) contains the data items
(dataset members) for SAGICU - code pages, brake iterators, etc.
See the Natural documentation for the parameter CFICU.

NAT3415: Conversion result is truncated.

Text
Conversion result is truncated.
Explanation
During Unicode conversion or the conversion from one code page to
another, the result in the target field has been truncated.
Action
Check the length of the target field.

NAT3416: Length/format of operand is incompatible with code page.

Text
Length/format of operand is incompatible with code page.
Explanation
For a Unicode conversion, or a conversion from one code page to
another, the format and length of source/target fields must
be compatible with the corresponding code page.
Example 1: The source/target field is defined as (Bn), but the value
of <minimum bytes per code point> of the relevant code page is > n;
this means that not even one code point could be stored in the
field.
Example 2: For many code points, the minimum and maximum bytes per
code point are identical.
Before the conversion, it is checked whether the code points
fit into the defined length. If they do not, this message is issued.
This is to avoid the truncation of code point values.
Action
Check the lengths of the source and target operands.

NAT3417: The used code page name is ambiguous in this context.

Text
The used code page name is ambiguous in this context.
Explanation
The target code page specified in MOVE ENCODED statement must be
unambiguous. However, specifying "UTF-16" or "UTF-32" does not uniquely
identify a target code page.
Action
Instead of "UTF-16" and "UTF-32", specify "UTF-16BE" or "UTF-16LE",
and "UTF-32BE" or "UTF-32LE" respectively.

NAT3418: ICU Data Library :1: cannot be loaded (:2:).

Text
ICU Data Library ... cannot be loaded (...).
Explanation
The data library is treated like an external program.
The specified external data library could be neither loaded dynamically
nor located statically. See the supplied operating-system/TP-monitor
return code of the failing LOAD request for details.
Possible reasons:
- The data library to be loaded dynamically is not contained in the
  load libraries currently defined to Natural.
- Under CICS: The data library is not defined to CICS.
- There was not enough storage available to load the data library
  dynamically (under Com-plete: the Com-plete thread was too small).
- The CDYNAM limit for dynamically loaded programs was exceeded.
- The DATFILE version is not compatible with SAGICU (reason 80).
- For static data library: The data library is not defined in NATPARM
  with the CSTATIC parameter or not linked to the NATPARM module.
Action
  with the CSTATIC parameter or not linked to the NATPARM module.
Make sure that the data library is contained in a library available
to or linked to Natural. Contact your Natural administrator concerning
the setting of the Natural profile parameters CDYNAM and CSTATIC.

NAT3419: Local ICU buffer pool cannot be used. RC=:1:

Text
Local ICU buffer pool cannot be used. RC=...
Explanation
The message is displayed at session start if the local ICU buffer pool
cannot be used. The reason code (RC) indicates the reason for this
message:
RC=1 - Local ICU buffer pool is not available.
RC=2 - Local ICU buffer pool is too small.
RC=3 - Local ICU buffer pool is already used by a different ICU nucleus.
If CFICU subparameter BPONLY=ON, the message leads to a termination of
the ICU initialization with the consequence that no ICU handler is
available for the current Natural session.
If CFICU subparameter BPONLY=OFF, the required buffers are allocated
in the Natural thread.
Action
Make the local ICU buffer pool available, or increase its size.

NAT3423: Maximum line length exceeded in line :1:.

Text
Maximum line length exceeded in line ....
Explanation
The source area has Unicode UTF-16 format. When you save a source,
it is converted from UTF-16 to the source encoding, which can change
the size (in code points) of a character.
This error occurs because the current source contains a line which,
after the conversion, exceeds the maximum line length.
Action
Either split the line or choose another encoding for saving the source.