| Text | NAT object STOWed for ... but executed under .... |
| Expl. | 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. |
| Actn. | The DBID used at stow time and at runtime must be assigned to the same database type. |
| Text | Unknown DB response code .... DB/FNR/Subcode .../.../.... |
| Expl. | An unknown response code was received from the Adabas interface. |
| Actn. | Check program and correct error. |
| Text | ADAMODE was changed from :1: to :2:. |
| Expl. | 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. |
| Actn. | Contact your Natural/Adabas administrator. |
| Text | No Natural ICU handler available. |
| Expl. | 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. |
| Actn. | Depends on the reason of the error. If an initialization error
has occurred, check the session initialization error messages. |
| Text | Code page ... not available. |
| Expl. | 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. |
| Actn. | Please contact Software AG support. |
| Text | Internal error from ICU: .... |
| Expl. | 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. |
| Actn. | Please contact Software AG support. |
| Text | Conversion error, at least one code point not translated. |
| Expl. | 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. |
| Actn. | Check the content of the input/target field of the conversion. |
| Text | Reserved for ICU. |
| Text | Conversion result is truncated. |
| Expl. | During Unicode conversion or the conversion from one code page to another, the result in the target field has been truncated. |
| Actn. | Check the length of the target field. |
| Text | Length/format of operand is incompatible with code page. |
| Expl. | 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. |
| Actn. | Check the lengths of the source and target operands. |
| Text | The used code page name is ambiguous in this context. |
| Expl. | 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. |
| Actn. | Instead of "UTF-16" and "UTF-32", specify
"UTF-16BE" or "UTF-16LE", and "UTF-32BE" or "UTF-32LE" respectively. |
