| Text | Intermediate result too large. |
| Expl. | The construct of the arithmetic expression generates an
intermediate result with too many digits. |
| Actn. | Separate the arithmetic expression into several statements with
defined lengths for intermediate results. |
| Text | Division by zero not permitted by parameter ZD=ON. |
| Expl. | The ZD session parameter is set to "ON". This causes an error when a division by zero is attempted. If a result of zero is desired when attempting a division by zero, change the setting of the ZD session parameter to "OFF". |
| Actn. | Set "ZD=OFF" if desired. |
| Text | Numeric truncation caused by adding/subtracting 1. |
| Expl. | In the evaluation of a relational expression, the operators GREATER and LESS THAN are evaluated by adding/subtracting "1" from the value. |
| Actn. | Increase length of field used in relational expression. |
| Text | Value has been rounded and does not fit into field. |
| Expl. | Rounding has caused the value to exceed the number of digits defined for the field. |
| Actn. | Increase length of field being rounded. |
| Text | Numeric value truncated in MOVE/ASSIGN operation. |
| Expl. | The receiving field in a MOVE/ASSIGN operation is not long enough to hold the result of the value. |
| Actn. | Increase the length of the receiving field. |
| Text | Error in STEP value in FOR statement. |
| Expl. | The end value cannot be reached by incrementing the start value because STEP value = 0 was detected. |
| Actn. | Check program and correct error. |
| Text | Resulting element address in MOVE INDEXED out of range. |
| Expl. | The target address of the MOVE INDEXED operation lies outside the Natural data area. |
| Actn. | Check index value or length of base field in MOVE INDEXED. |
| Text | Replace string does not fit into variable. |
| Expl. | In an EXAMINE statement, one of the strings to be examined and replaced resulted in a total string length that is larger than the variable length. A truncation of a value is not allowed in an EXAMINE statement. |
| Actn. | Adjust length of field in EXAMINE statement. |
| Text | Overflow in NUMBER variable of EXAMINE statement. |
| Expl. | The number of strings found in the source variable is too large to be represented in the NUMBER variable of the EXAMINE statement. |
| Actn. | Adjust the length of the NUMBER variable. |
| Text | RETRY statement not allowed for this error number. |
| Expl. | 1. A RETRY is only possible for database response code
"145". This response code indicates that a record which is to be read for update is currently in "hold" status for another user. NAT3145 can only occur when the global option WH=OFF (wait hold) is in effect. 2. NAT1310 can also occur under one of the following conditions if the response code is in fact "145": - The object module which was active when "145" was received does not contain an ON ERROR statement. - The RETRY statement executed in reaction to "145" is not contained in the same object module as was active when the response code was received. Response code "145" can only be handled by the object module which is active when the response code is received. When control is returned from that module, Natural automatically converts NAT3145 to NAT1310. |
| Actn. | that module, Natural automatically converts NAT3145 to NAT1310.
Check program and correct error. |
| Text | Index in MOVE INDEXED statement is zero or negative. |
| Expl. | The index in a MOVE INDEXED statement must be positive. |
| Actn. | Correct program. |
| Text | Number of elements too large for number field. |
| Expl. | The NUMBER clause was used in the SEPARATE statement, but the number of elements to be returned does not fit into the field specified. |
| Actn. | Increase the length of the field which is to contain the resulting number of elements. |
| Text | Not enough receiving fields available in SEPARATE. |
| Expl. | The source field contained so many delimiter characters that
there were not enough target fields available in the SEPARATE statement to receive all values. |
| Actn. | Check program and correct error. |
| Text | Target field too small for field portion. |
| Expl. | In a SEPARATE statement, a portion of a field to be transferred
is larger than the target field specified. |
| Actn. | Increase the length of the target field. |
| Text | Source field and target field in SEPARATE overlap. |
| Actn. | Avoid overlapping of source and target fields. |
| Text | Index not within array structure. |
| Expl. | The index specified for an array is not within the dimensions defined for the array. |
| Actn. | Check program and correct error. |
| Text | Array range operation on invalid ranges. |
| Expl. | An arithmetic operation may operate on array ranges with identical range structures, or on array ranges with single values (scalar values). Two or three ranges were defined for an arithmetic operation, which do not have identical range structures. |
| Actn. | Check program and correct error. |
| Text | Overlap during ASSIGN. |
| Expl. | During assignment of alphanumeric or binary operands, an invalid overlap was detected. This condition occurs when an attempt is made to move a byte which has already been moved during the execution of the statement. |
| Actn. | Check program and correct error. |
| Text | Invalid date operation. |
| Expl. | The result of an operation (date integer) is a negative date. |
| Actn. | Check program and correct error. |
| Text | Invalid operand for system function VAL. |
| Expl. | The operand of the VAL system function does not contain a valid alphanumeric representation of the resulting value. The VAL system function is similar to the INPUT statement: what is accepted by the INPUT statement is also accepted by the VAL system function. |
| Actn. | Check program and correct error. |
| Text | Invalid UNTIL parameter in MOVE ALL statement. |
| Expl. | This error may be caused by one of the following: - The UNTIL parameter contains a negative value. - The UNTIL parameter contains a value with more than 7 valid decimal digits or more than 31 valid binary digits. |
| Actn. | Correct error. |
| Text | Parameter ... missing (invoked at line ... by .../.../.../...). |
| Expl. | Natural tried to execute a statement which contained a reference
to parameter ... which was not supplied by the object .../.../.../... This occurs if the invoking statement at line ... has not supplied a parameter which was defined as optional by the invoked object (DEFINE DATA PARAMETER). |
| Actn. | Specify the missing parameter in the invoking statement. |
| Text | ACCEPT, REJECT, REINPUT not allowed in end-data condition. |
| Expl. | The statements ACCEPT and REJECT are not allowed in an
end-of-data condition (loop is already closed). The same restriction applies for a REINPUT statement if the corresponding INPUT statement is contained within a loop which has been closed. |
| Actn. | Check program and correct error. |
| Text | Loop must be active if this statement is used. |
| Expl. | An ESCAPE TOP, ESCAPE BOTTOM, ACCEPT, REJECT or PERFORM BREAK
PROCESSING statement cannot be executed, because - no loop is active for an ESCAPE TOP, ESCAPE BOTTOM or PERFORM BREAK PROCESSING statement; - no FIND, READ, HISTOGRAM, CALL FILE, SORT or READ WORK FILE loop is active for an ACCEPT or REJECT statement. |
| Actn. | Check program and correct error. |
| Text | Too many asterisks "*" found in pattern. |
| Expl. | A maximum of 10 asterisks "*" may be supplied in a
pattern. If more "*" are found in the pattern, a table overflow occurs and therefore the execution is stopped. However, "**" is recognized as "*". |
| Actn. | Decrease the number of asterisks "*" in the pattern. |
| Text | Range specified in SUBSTRING option is outside field. |
| Expl. | Error in the SUBSTRING option of an ASSIGN, EXAMINE, IF, MOVE or SEPARATE statement: - the starting position is not within the field; or - the value of the starting position is zero or negative; or - the specified length exceeds the length of the field; or - the length value is zero or negative. |
| Actn. | Check program and correct error. |
| Text | Data in numeric field is not numeric. |
| Expl. | The content of a numeric variable (type N, F or P) is not
numeric. For example, a field of the definition N4 contains the hexadecimal value H"404040F1" A possible reason is that the numeric field is a redefinition of an alphanumeric field. |
| Actn. | Correct error in program. |
| Text | No default code page available. |
| Expl. | The execution of the current statement requires that a default
code page is defined. |
| Actn. | Define a code page, using the CP parameter. |
