Text |
Format "C" or "L" not allowed with COMPRESS or MOVE ALL. |
Explanation |
- Multiple values may be compressed into one receiving field by use of a COMPRESS statement. The field whose values are compressed must not be of format "C" or "L". - One value may be moved more than once to a receiving field with a MOVE ALL statement. The value to be moved must be of alphanumeric (A) or unpacked numeric (N) format. |
Action |
Correct error. |
Text |
Error in reference to Natural system function in SORT. |
Explanation |
Only the system functions MAX, MIN, AVER, TOTAL may be evaluated. The values of these functions may be referenced after the sort operation in the form *FUNCTION(variable). Example: MOVE *TOTAL(SALARY) TO PAYROLL-TOTAL(N8) |
Action |
Correct error. |
Text |
Error in receiving field for COMPRESS statement. |
Explanation |
In a COMPRESS statement, the word "INTO" (or "TO") must be followed by a valid field name to indicate where the result is to be placed. The receiving field must be of alphanumeric (A) format. |
Action |
Correct error. |
Text |
Multiple loop-initiating statements in the same line. |
Explanation |
Only one loop-initiating statement may be specified in a single source code line. |
Action |
Enter each loop-initiating statement in a separate line. |
Text |
Database updating not permitted. |
Explanation |
The Natural administrator has disabled updating of the specified database. No programs with database-update functions can be created. |
Action |
Contact your Natural administrator. |
Text |
SAVE/CATALOG/STOW/PURGE/UNCATALOG/SCRATCH not available. |
Explanation |
Your Natural administrator has set the profile parameters ROSY and/or RECAT so that the system commands SAVE, CATALOG, STOW, PURGE, UNCATALOG, SCRATCH cannot be used. |
Action |
Contact your Natural administrator. |
Text |
No more than 2000 bytes may be specified for ET data. |
Explanation |
An END TRANSACTION statement was issued in which more than the maximum of 2000 bytes of user data were provided. |
Action |
Reduce the amount of ET data. |
Text |
Error in group reference in WRITE WORK FILE statement. |
Explanation |
An error was detected during the processing of individual fields that are referenced via a group name. |
Action |
Check group definition. |
Text |
Invalid reference in GET SAME or UPDATE statement. |
Explanation |
The GET SAME or UPDATE statement can only refer back to a database-access statement, such as FIND, READ or GET, which is currently active; that is, the processing loop for that database access must still be open. |
Action |
Correct error. |
Text |
No source text allowed after the END statement. |
Explanation |
The END statement indicates the end of the source of a Natural object. No other statements or comment lines are allowed after the END statement. A probable cause of this error is the misspelling of a name or the omission of "PAGE", "DATA", "TRANSACTION" from the statements AT END OF PAGE, AT END OF DATA, END TRANSACTION respectively; or a missing hyphen in END-DEFINE, END-FIND, END-IF etc. |
Action |
Correct error. |
Text |
Function only available with .... |
Explanation |
You have specified a function which is currently not available, because the required Software AG product or component is - not installed in your Natural FNAT system file or - not linked to your Natural nucleus or - not available for dynamic invoking. For example, the use of the system command MAIL would lead to this error if Natural Security is not installed. |
Action |
Contact your Natural administrator. |
Text |
Invalid use of group name. |
Explanation |
A group name must not be specified in this statement; specify elementary fields instead. |
Action |
Correct error in program. |
Text |
Error in SET KEY statement construction. |
Explanation |
See the Natural documentation for information on the valid syntax for the SET KEY statement. |
Action |
Correct error in program. |
Text |
Error in variable definition for GET TRANSACTION DATA. |
Explanation |
This error is usually the result of a misspelt variable name. In the GET TRANSACTION DATA statement, all types of variables of all formats are allowed. Variables may either be newly defined in the GET TRANSACTION DATA statement or may be referenced from a previous definition. |
Action |
Check program and correct error. |
Text |
Incorrect "/n/" specification in AT BREAK statement. |
Explanation |
The "/n/" notation in an AT BREAK statement or an IF BREAK condition was specified incorrectly. "n" must be specified as a numeric constant, with a value in the range 1-253, enclosed in slashes (/) without any leading or trailing blank characters. Example: AT BREAK OF POST-CODE /5/ . IF BREAK OF BIRTH /2/ |
Action |
Correct error. |
Text |
Word "IDENTICAL" missing in SUSPEND IDENTICAL SUPPRESS. |
Explanation |
The word "IDENTICAL" specifies the action to be taken for the suppress operation and is therefore required. |
Action |
Correct error. |
Text |
Value assigned to function key not format "A". |
Explanation |
The value to be assigned to a function key must be specified as a literal constant, or by a user-defined variable with format "A". |
Action |
Correct error. |
Text |
Invalid format for UNTIL value in MOVE ALL statement. |
Explanation |
The format of the value provided with the UNTIL option must be either - a positive integer constant value or - a variable of type "Integer" or - a variable of type "Numeric/Packed" without decimal digits. The usage of system-variables is not permitted. |
Action |
Correct error. |
Text |
This statement is not permitted in structured mode. |
Action |
Do not use this statement, or switch to reporting mode. |
Text |
Only format A, C or L allowed for fields in IF SELECTION. |
Explanation |
The IF SELECTION statement may only be used to check the content of alphanumeric, attribute control and logical fields for non-blank contents. Only operands of the same type can be checked. |
Action |
Correct error. |
Text |
Error in field specification for IF SELECTION statement. |
Explanation |
At least one field must be specified in the IF SELECTION statement. |
Action |
Correct error. |
Text |
Error in index notation for MOVE INDEXED statement. |
Explanation |
The index must be specified as a numeric constant or a user-defined variable defined with format "N". Examples: MOVE INDEXED #A <5> TO #B <2> MOVE INDEXED #A <#INDEX> TO #B <#INDEX> |
Action |
Correct error. |
Text |
No or invalid output element following DISPLAY/WRITE/INPUT. |
Explanation |
At least one element must be specified in a DISPLAY, WRITE or INPUT statement. A possible cause for the error is a misspelt variable name that conflicts with the name of a Natural statement. |
Action |
Check program and correct error. |
Text |
Error in qualification of variable. |
Explanation |
Only one level of qualification is allowed. |
Action |
Check program and correct error. |
Text |
The word "AS" is missing in FIND AND RETAIN AS. |
Explanation |
The word "AS" identifies that a RETAIN SET operation is to be performed and it must therefore be specified. |
Action |
Add the word "AS" to the RETAIN clause of the FIND statement. |
Text |
Value to be used to identify set must be of format "A". |
Explanation |
The value used in a RETAIN clause to identify a set of records may be specified either as an alphanumeric constant or the content of an alphanumeric variable. This error may also occur if the WITH clause of a FIND statement contains a non-descriptor. |
Action |
Check program and correct error. |
Text |
The specified set name is longer than 32 characters. |
Explanation |
The name for a set in a RETAIN AS clause may be specified as an alphanumeric constant or the content of an alphanumeric variable. The set name must not be longer than 32 characters. |
Action |
Check program and correct error. |
Text |
No "/" allowed immediately before keywords HORIZ or VERT. |
Explanation |
The keywords HORIZ(ONTALLY) and VERT(ICALLY) indicate the initiation of a new output column. As a new column cannot be placed underneath an already processed column, the character "/" - which indicates that the next element is to be placed under the previous one - cannot be used before the keywords HORIZ, VERT, HORIZONTALLY, VERTICALLY. |
Action |
Check program and correct error. |
Text |
GET TRANSACTION DATA needs at least one variable. |
Explanation |
The GET TRANSACTION DATA statement must contain at least one variable in which the transaction data can be placed. This error may be caused by a misspelt variable name or by an invalid character in a variable name. |
Action |
Check program and correct error. |
Text |
Operand not defined or not of alphanumeric/binary format. |
Explanation |
The variable that is examined in an EXAMINE statement must have been defined before, and it must be of alphanumeric or binary format. |
Action |
Check program and correct error. |
Text |
Error in NUMBER option of EXAMINE statement. |
Explanation |
The error may be caused by misspelling a variable name. The NUMBER variable must be of a numeric format ("N", "P" or "I"). The NUMBER variable must be an integer. See the Natural EXAMINE statement documentation for further information. |
Action |
Correct error in program. |
Text |
DELETE/REPLACE/GIVING clause missing in EXAMINE statement. |
Explanation |
The EXAMINE statement requires at least one of the following clauses: REPLACE DELETE GIVING NUMBER GIVING POSITION GIVING LENGTH GIVING INDEX See the Natural EXAMINE statement documentation for further information. |
Action |
Correct error in program. |
Text |
Error in EXAMINE TRANSLATE statement. |
Explanation |
In an EXAMINE TRANSLATE statement, the keyword "TRANSLATE" must be followed by "INTO UPPER", "INTO LOWER", or a USING clause. See the Natural documentation for further information on the EXAMINE TRANSLATE statement. |
Action |
Correct error in program. |
Text |
No object specified in RELEASE statement. |
Explanation |
Possible objects to be released are: STACK - release all data items from the stack. PARAMETERS - release all parameters built during the session. SETS - release all FIND sets. SET set name - release one specific FIND set. |
Action |
Check program and correct error. |
Text |
Identifier for FIND set must be alpha and <= 32 bytes. |
Explanation |
The identifier may be specified as an alphanumeric constant or the contents of an alphanumeric variable. The contents of the variable will be used to identify the FIND set. The alphanumeric value can only be up to 32 bytes long because this is the maximum length of a FIND set identification. |
Action |
Check program and correct error. |
Text |
At least 1 data item must be specified in STACK statement. |
Explanation |
Constants or variables of the formats "A", "N" or "B" may be used as data items in a STACK statement. At least one of these items must be present in a STACK statement. |
Action |
Check program and correct error. |
Text |
"NOT" is only possible after "AND" operation. |
Explanation |
Exclusion of a set can only be done when the set name is preceded by the logical operator "AND" and followed by the operator "NOT". The set will then be excluded from the number of records that were selected up to that point. |
Action |
Restructure the logical criteria to place the set to be excluded after an AND operation. |
Text |
Invalid keyword specified in SET GLOBALS statement. |
Explanation |
The valid keywords for the SET GLOBALS statement are described in the Natural documentation. |
Action |
Check program and correct error. |
Text |
Invalid value for keyword in SET GLOBALS statement. |
Explanation |
The value for a SET GLOBALS keywords can be supplied as a constant or as a variable. If a constant is supplied, it must be alphanumeric or numeric and have a correct value; for example: PS must be numeric and in the range from 0 to 250. If a variable is supplied, it must also be of the correct type. If it is numeric, it must be an integer. See the Natural documentation for further information on the SET GLOBALS statements. |
Action |
Check program and correct error. |
Text |
Invalid format for value in SET GLOBALS statement. |
Explanation |
The SET GLOBALS keyword in question requires an alphanumeric value. The alphanumeric value can be specified as a constant or as the content of an alphanumeric variable (format A). |
Action |
Check program and correct error. |
Text |
Invalid format for value in SET GLOBALS statement. |
Explanation |
See the Natural session parameters documentation to determine the possible values for the SET GLOBALS keywords. Valid formats are integer numeric for keywords whose values are numeric and alphanumeric for keywords whose possible values are "ON/OFF" or alphanumeric characters. The values "T/F" may be used as synonyms for "ON/OFF" respectively. For example: SET GLOBALS EJ=OFF has the same meaning as SET GLOBALS EJ=F |
Action |
Check program and correct error. |
Text |
Invalid syntax in SET GLOBALS statement. |
Explanation |
The syntax of the SET GLOBALS statement requires that each parameter be followed by the assignment character "=", which in turn is to be followed by the value for the parameter. |
Action |
Check program and correct error. |
Text |
No command supplied in STACK statement. |
Explanation |
The COMMAND option of the STACK statement was specified, but no command was provided. |
Action |
Check program and correct error. |
Text |
Invalid format for variable in TERMINATE statement. |
Explanation |
Only variables of format "N", "I" or "P" are permitted with the TERMINATE statement. The value must lie between 0 and 255. |
Action |
Check program and correct error. |
Text |
Format error in MOVE EDITED statement. |
Explanation |
A field used in a MOVE EDITED statement for which an edit mask has not been defined, must be defined with alphanumeric (A), binary (B) or Unicode (U) format. |
Action |
Check program and correct error. |