| Text | Invalid map name in INPUT statement. |
| Expl. |
The name of a map to be used in an INPUT statement can be specified as a literal constant or the content of an alphanumeric variable. If a variable is used, it must have been previously defined. |
| Actn. |
Check program and correct error. |
| Text | Invalid map format in INPUT statement. |
| Expl. |
The name of a map to be used in an INPUT statement may be specified as a literal alphanumeric constant or the content of an alphanumeric variable. If a variable is used, it must have been previously defined. |
| Actn. |
Check program and correct error. |
| Text | Format definition not allowed for a group name. |
| Expl. |
A group name is used to refer to a collection of fields as a single structure. Since this structure is defined by the formats of these fields, the group name need not have a format definition. If a field of one format is to be redefined as fields of differing formats, the REDEFINE statement should be used. Another possible cause of this error is that the level number of the next variable definition is higher than that of the variable marked, although both variables should probably be at the same level. |
| Actn. |
Remove the format definition at the group name level, or make sure that the level numbers are correct. |
| Text | Map name must not be longer than 7 characters. |
| Expl. |
A map name can be specified as a literal constant or the content of an alphanumeric variable. The maximum length of a map name is 7 characters. |
| Actn. |
Check program and correct error. |
| Text | Invalid group specification in MOVE BY NAME statement. |
| Expl. |
The operands to be specified in a MOVE BY NAME statement must be valid and existing group names. They may also be user views. Individual field names cannot be specified. If a user view is used, it must not be qualified with a statement label or source-code line number. |
| Actn. |
Check program and correct error. |
| Text | Fields in MOVE BY NAME or MOVE BY POSITION do not match. |
| Expl. |
For MOVE BY NAME no matching names were found. At least one field with the same name must exist in both groups. For MOVE BY POSITION the number of fields in the referenced groups do no match. |
| Actn. |
Check program and correct error. |
| Text | Invalid descriptor in READ LOGICAL statement. |
| Expl. |
Descriptors that are multiple-valued are not permitted in the THRU or ENDING AT clause of a READ statement. Phonetic descriptors must not be used in a READ statement. A field contained in a PE-group may not be used as search-field in a READ statement. |
| Actn. |
Check program and correct error. |
| Text | ROUNDED clause not allowed with DIVIDE REMAINDER. |
| Expl. |
In a DIVIDE statement, you can use either the ROUNDED option to have the result of the division rounded, or the REMAINDER option to have the remainder of the division placed into a separate field. As there can be no remainder with a rounded result, it obviously makes no sense to use both options at the same time and is therefore not permitted. |
| Actn. |
Use ROUNDED option or REMAINDER option, but not both. |
| Text | Floating format not allowed for DIVIDE REMAINDER. |
| Expl. |
When you use the REMAINDER option in a DIVIDE statement, the format of the divisor and the dividend must not be "F" (floating point). |
| Actn. |
Check program and correct error. |
| Text | Specification of level missing in DEFINE DATA statement. |
| Expl. |
In a DEFINE DATA statement, there must be an integer level number before each variable, group, view, REDEFINE definition. |
| Actn. |
Check program and correct error. |
| Text | Illegal syntax for variable name. |
| Expl. |
- In a DEFINE DATA statement, the level specification must be followed by a valid name of a variable, group or view. - In a DEFINE DATA INDEPENDENT statement, - a variable name has to start with a "+" character (AIV variable); - the name of a field resulting from the redefinition of an AIV variable must not start with a "+" character. - A variable name starting with "+" (AIV) cannot be used in a PARAMETER, OBJECT, LOCAL or CONTEXT clause of a DEFINE DATA statement. See Natural Statements / Statement Usage Related Topics / User-Defined Variables / Naming Conventions and DEFINE DATA statement, for rules on naming variables. |
| Actn. |
Correct error in program. |
| Text | Inconsistency in data structure of variable definition. |
| Expl. |
An inconsistency in the data structure of a statement has been detected. This error may occur in the following statements: - DEFINE DATA - DEFINE FUNCTION (RETURNS clause) - DEFINE PROTOTYPE (RETURNS clause) |
| Actn. |
Check the specifications of levels and variable definitions. |
| Text | Invalid variable definition in DEFINE DATA statement. |
| Expl. |
An invalid definition of the DEFINE DATA statement has been detected. |
| Actn. |
Check and correct variable definition. |
| Text | Duplicate specification of a view name detected. |
| Expl. |
View names in the data structure of a program must be unique. |
| Actn. |
Check view names of each GLOBAL, PARAMETER and LOCAL data structure. |
| Text | INTO constant not allowed in DIVIDE without GIVING clause. |
| Expl. |
If your DIVIDE statement does not have a GIVING clause, the result will be place into the operand after keyword "INTO"; in this case, the INTO operand cannot be a constant. If you require the INTO operand to be a constant, use a GIVING clause to specify a result field. |
| Actn. |
Check program and correct error. |
| Text | Error in format/length or in EM, HD, PM definition. |
| Expl. |
One of the following is invalid for a field definition in the DEFINE DATA statement: - format (valid formats are A,U,B,C,D,F,I,L,N,P,T) - specified length, - combination of format and length (valid lengths for formats A and B are 1-1073741824; for format U is 1-536870912; for format F is 4 or 8; for format I is 1, 2 or 4; no length value may be specified for formats C, D, L, T) - number of positions before or after the decimal point for formats N,P (in the notation Nnn.m or Pnn.m, valid values for nn are 0-29, valid values for m are 0-7, and the sum nn+m must be in the range 1-29) Or one of the parameters EM (edit mask), HD (header), or PM (presentation mode) has not been specified correctly. See the Natural DEFINE DATA statement documentation for details. |
| Actn. |
See the Natural DEFINE DATA statement documentation for details.
Check program and correct error. |
| Text | A variable must be specified in INTO clause of SEPARATE. |
| Expl. |
A variable, not a constant, must be specified with the INTO clause of the SEPARATE statement. |
| Actn. |
Check program and correct error. |
| Text | The INTO clause is missing in a SEPARATE statement. |
| Expl. |
The keyword "INTO", followed by one or more operands, is required in a SEPARATE statement. |
| Actn. |
Check program and correct error. |
| Text | The keyword "NUMBER" is missing in a GIVING clause. |
| Expl. |
If "GIVING" is used, the keyword "NUMBER" is also required. |
| Actn. |
Check program and correct error. |
| Text | The field after NUMBER must be a numeric integer (N,I,P). |
| Expl. |
The field specified in the GIVING NUMBER clause of a SEPARATE statement must be a numeric integer; that is, its format must be one of the following: I N (without decimal digits) P (without decimal digits) |
| Actn. |
Check program and correct error. |
| Text | Source field and at least one target field are required. |
| Expl. |
The source field in a SEPARATE statement may be an alphanumeric constant or variable. At least one target field, which must be an alphanumeric variable, must be specified. |
| Actn. |
Check program and correct error. |
| Text | Error in POSITION field of EXAMINE statement. |
| Expl. |
The error may be caused by misspelling a variable name used as a reference to the POSITION variable. The variable must be of numeric format (N, I or P), and it must also be an integer (no decimal digits). |
| Actn. |
Check program and correct error. |
| Text | Error in LENGTH field of EXAMINE statement. |
| Expl. |
The error may be caused by misspelling a variable name used as reference to the LENGTH variable. This variable must be of numeric format (N,I,B or P), and it must be an integer (no decimal digits). |
| Actn. |
Check program and correct error. |
| Text | Error in INDEX field of EXAMINE statement. |
| Expl. |
The error may be caused by misspelling a variable name used as reference to an INDEX variable. The variables must be of numeric format (N,I,B or P), and they must be integers (no decimal digits). The number of INDEX variables must equal the number of dimensions contained in the examined array. |
| Actn. |
Check program and correct error. |
| Text | Invalid keyword in GIVING clause of EXAMINE statement. |
| Expl. |
The following keywords are valid after GIVING: NUMBER POSITION LENGTH INDEX If more than one keyword is specified, they must be specified in the order indicated above. |
| Actn. |
Check program and correct error. |
| Text | Word "TEXT" missing after "WITH" in INPUT statement. |
| Expl. |
The word "TEXT" is a required part of the WITH TEXT clause. |
| Actn. |
Check program and correct error. |
| Text | Error in specification of a variable in WITH TEXT clause. |
| Expl. |
See the Natural documentation, INPUT or REINPUT statement, for details. |
| Actn. |
Correct error in program. |
| Text | Invalid parameter list for WITH TEXT clause. |
| Expl. |
See the Natural documentation, INPUT or REINPUT statement, for details. |
| Actn. |
Correct error in program. |
| Text | No more than 9 parameters allowed in WITH TEXT clause. |
| Actn. |
Check program and correct error. |
| Text | Specification error in variable of MARK clause. |
| Expl. |
The variable must be a numeric integer and must have been previously defined. |
| Actn. |
Check program and correct error. |
| Text | Keyword "ALARM" is required after "AND" or "SOUND". |
| Expl. |
The keyword "ALARM" is a required keyword to identify the ALARM option; the keywords "AND" and "SOUND" may be omitted. |
| Actn. |
Check program and correct error. |
| Text | Keywords DO and DOEND not permitted in structured mode. |
| Expl. |
You wanted to use a DO/DOEND statement group in structured mode; however, DO/DOEND statement groups are only permitted in reporting mode. In structured mode, explicit END-... statements are used to indicate the end of a statement block; for example: AT BREAK DO...DOEND becomes AT BREAK...END-BREAK AT END OF DATA DO...DOEND becomes AT END OF DATA...END-ENDDATA AT END OF PAGE DO...DOEND becomes AT END OF PAGE...END-ENDPAGE AT START OF DATA DO...DOEND becomes AT START OF DATA...END-START AT TOP OF PAGE DO...DOEND becomes AT TOP OF PAGE...END-TOPPAGE IF...DO..DOEND ELSE DO...DOEND becomes IF...THEN...ELSE...END-IF ON ERROR DO...DOEND becomes ON ERROR...END-ERROR BEFORE BREAK DO...DOEND becomes BEFORE BREAK...END-BEFORE PERFORM BREAK DO...DOEND becomes PERFORM BREAK...END-BREAK |
| Actn. |
Select reporting mode or use the correct syntax. |
| Text | The LOOP statement is not permitted in structured mode. |
| Expl. |
You wanted to use the statement LOOP in structured mode; however, the LOOP statement is only permitted in reporting mode. In structure mode, a loop is not closed with a LOOP statement but with an explicit loop-closing END-... statement; for example: Reporting Mode: FIND ... LOOP Structured Mode: FIND ... END-FIND |
| Actn. |
Select reporting mode or use structured mode syntax. |
| Text | SORT without END-ALL is not permitted in structured mode. |
| Expl. |
In structured mode, a processing loop initiated with a SORT statement must be closed with an END-ALL statement. |
| Actn. |
Check program and correct error. |
| Text | END-ALL must be followed by SORT in structured mode. |
| Actn. |
Check program and correct error. |
| Text | Invalid placement of UNTIL or WHILE clause. |
| Expl. |
An UNTIL or WHILE clause must be specified either immediately after the keyword "REPEAT" or immediately before the "END-REPEAT". Examples: 1. REPEAT UNTIL logical-condition statements END-REPEAT 2. REPEAT statements UNTIL logical-condition END-REPEAT |
| Actn. |
Check program and correct error. |
| Text | Loop-ending statement missing after UNTIL/WHILE. |
| Expl. |
In structured mode, a REPEAT ... UNTIL/WHILE processing loop must be closed with "END-REPEAT". In reporting mode, it must be closed with "LOOP". |
| Actn. |
Check program and correct error. |
| Text | Destination missing in ESCAPE statement. |
| Expl. |
The ESCAPE statement requires extra keywords to specify the destination: - ESCAPE TOP - ESCAPE BOTTOM or ESCAPE BOTTOM IMMEDIATE - ESCAPE ROUTINE or ESCAPE ROUTINE IMMEDIATE See the Natural documentation for more information. |
| Actn. |
Correct error in program. |
| Text | Keyword "ON" or "FOR" missing in DECIDE statement. |
| Expl. |
The keyword "DECIDE" must be followed either by "ON" or by "FOR". |
| Actn. |
Check program and correct error. |
| Text | Invalid syntax in DECIDE FOR statement. |
| Expl. |
See the Natural documentation for information on the correct syntax of the DECIDE FOR statement. |
| Actn. |
Correct error in program. |
| Text | Specified field must not be an array range. |
| Actn. |
Check program and correct error. |
| Text | GIVING INDEX is only allowed for indexable variables. |
| Actn. |
Check program and correct error. |
| Text | Variable format not permitted in this statement. |
| Expl. |
1. A variable of format "C" is not permitted in a DISPLAY, WRITE, INPUT, PRINT, STACK, RUN and FETCH statement. 2. A variable of format HANDLE OF OBJECT can not be used in this statement. |
| Actn. |
Check program and correct error. |
| Text | No more than 128 parameters allowed in CALL statement. |
| Expl. |
The maximum number of parameters in a CALL statement is 128. |
| Actn. |
Check program and correct error. |
| Text | Label defined twice or same as view/level-1-variable name. |
| Expl. |
Within a Natural module, a label must not be equal to another label, a view name or a variable name defined on level 1. |
| Actn. |
Check program and correct error. |
| Text | Error in INCLUDE source lines. |
| Expl. |
See Natural INCLUDE statement documentation for more information. |
| Actn. |
Check program and correct error. |
