Text |
Error in reference for GET SAME statement. |
Explanation |
The GET SAME statement refers by default to the last active access to the database; a reference to another specific database access may be explicitly specified. If an explicit reference is used, the database access must still be active. |
Action |
Correct the error in the GET SAME reference. |
Text |
Error in field reference in GET statement. |
Explanation |
One of the following errors was detected in a GET statement: - A field referenced is not contained in the specified file. - An invalid index notation for a database array was used. |
Action |
Check program and correct error. |
Text |
Invalid ISN value specified in GET or READ statement. |
Explanation |
The ISN value in a GET or READ statement must be specified as an integer numeric constant, a user-defined variable, or via the Natural system variable *ISN. If you use *ISN, you must specify the statement label or source-code line number (r) of the database statement that was used to originally read the record with that ISN. |
Action |
Correct error in program. |
Text |
No more than one WRITE TITLE/TRAILER allowed per report. |
Explanation |
Only one WRITE TITLE statement and one WRITE TRAILER statement may be specified per report. |
Action |
Check the report references of the WRITE TITLE/TRAILER statements. |
Text |
Error in entry for Natural system function. |
Explanation |
A Natural system function is indicated by an asterisk (*). The name of a valid Natural system function must follow the asterisk. Example: MOVE *MAX (SALARY) TO RICHPERSON |
Action |
Check program and correct error. |
Text |
Error in argument variable for Natural system function. |
Explanation |
The argument entry for a Natural system function may be a previously defined user-defined variable, or a database field. |
Action |
Check program and correct error. |
Text |
SORT statement used incorrectly. |
Explanation |
The SORT statement may only be used within an active processing loop. A SORT statement may not be placed within a processing loop that was initiated by another SORT statement. If a program contains multiple SORT statements, all must include a USING clause. |
Action |
Correct error. |
Text |
Invalid number specified in WITH LIMIT clause. |
Explanation |
The number representing the limit of records selected for further processing was specified incorrectly. It may be specified either as a numeric constant or as the content of a numeric variable that has been previously defined; for example: WITH LIMIT (123) or WITH LIMIT (#LMT) |
Action |
Correct error in program. |
Text |
Number of records to be processed not specified correctly. |
Explanation |
The number of records to be processed in a processing loop initiated by FIND, READ or HISTOGRAM statement may be limited. The limit is specified as (n) where n is either a numeric constant or the name of a previously defined numeric variable. |
Action |
Correct error. |
Text |
Incorrect field specification in WHERE clause. |
Explanation |
Probable causes of this message are: - an error in the specified name; - a reference to a Natural system function which has not yet been evaluated; - a new variable has been defined where not allowed. |
Action |
Correct error. |
Text |
Incorrect variable specification in logical criteria. |
Explanation |
The left portion of a relational expression was specified incorrectly. This error may be caused by misspelling a variable name or keyword in a statement that follows the relational expression. |
Action |
Check program and correct error. |
Text |
Error in GIVING value of ADD/MULTIPLY/SUBTRACT/DIVIDE. |
Explanation |
After the word "GIVING" in an ADD, MULTIPLY, SUBTRACT or DIVIDE statement, a valid notation for a variable reference must be specified. A user-defined variable or a database field may be used. |
Action |
Correct error. |
Text |
Invalid receiving field in MOVE statement. |
Explanation |
A valid notation for a variable reference must be specified after the word "TO" in a MOVE statement. A user-defined variable or a database field may be used. MOVE LEFT/RIGHT JUSTIFIED is not allowed if the receiving field is a system variable. For MOVE .. with SUBSTR(..) operand(s) the following applies: - The SUBSTR argument field must be alphanumeric or binary. - Move of numeric field (type N) to binary SUBSTR(..) not allowed. - Parameter "(PM=I)" not allowed if the receiving field is binary. - Move of SUBSTR(..) to receiving field other than type A/B not allowed. - Use of option LEFT/RIGHT JUSTIFIED is not allowed. |
Action |
Correct the error. |
Text |
Error in the argument for a Natural system function. |
Explanation |
The argument for a system function in a WRITE or DISPLAY statement following an AT BREAK/END DATA condition was specified incorrectly. Either a user-defined variable or a database field may be used. If a user-defined variable is used, it must have been previously defined. If a database field is used, it must be available within an active processing loop. For a database field which is contained within an array, a single index (one-dimensional array) or a range of indexes (two-dimensional array) may be used. |
Action |
Check program and correct error. |
Text |
Invalid parameter operand. |
Explanation |
- In a CALL or SEND METHOD statement an invalid operand was specified as parameter. - In a PROCESS GUI or PROCESS REPORTER statement the parameter operand violates the required parameter description of the appropriate action. - In a OPEN DIALOG or SEND EVENT statement the parameter operand does not match the parameter definition of the appropriate dialog. |
Action |
Check parameter operand. |
Text |
Group or periodic group referenced in VERT mode. |
Explanation |
Groups and periodic groups may only be referenced in a DISPLAY statement in HORIZONTAL mode because a group needs a layout of columns that requires multiple lines. Make sure that the display mode is set to "HORIZ" before referencing a group or periodic group. |
Action |
Check program and correct error. |
Text |
Error in constant specification for LIMIT statement. |
Explanation |
The value for the LIMIT statement may be specified as a numeric constant only. |
Action |
Check program and correct error. |
Text |
Error in control value specification of FOR statement. |
Explanation |
The control value must be numeric and may be specified as a constant, user-defined variable or database field. The TO value may be specified as a numeric constant, user-defined variable, or database field. Any database field used must be available via an active processing loop. |
Action |
Check program and correct error. |
Text |
Parameter error in GLOBALS or COMPOPT command. |
Explanation |
Parameters in the GLOBALS or COMPOPT command must be specified with a parameter identification and a valid argument for the parameter. See the Natural system commands and session parameters documentation for further information. |
Action |
Check parameter specified and correct error. |
Text |
Error in search criteria involving COUPLED clause. |
Explanation |
The COUPLED clause of a FIND statement may be used to specify a search which involves the Adabas coupling facility. A maximum of four COUPLED clauses may be used. See the Natural FIND statement documentation for further information. |
Action |
Check program and correct error. |
Text |
GIVE SYSTEM FUNCTIONS allowed only once per report. |
Explanation |
The GIVE SYSTEM FUNCTIONS clause, which is used to cause the evaluation of Natural system functions for subsequent use in an AT END OF PAGE condition, may only be used once for a given report. See the Natural DISPLAY statement documentation for further information. |
Action |
Check program and correct error. |
Text |
Invalid name defined. |
Explanation |
The name of a subroutine must conform to the same rules which apply to user-defined variables (as described in the Natural documentation under "User-Defined Variables"). The name of a class, a prototype or a function must also conform to these rules, except that it is allowed to use a period in a class/prototype name. |
Action |
Correct the name definition. |
Text |
A subroutine with the same name already exists. |
Explanation |
You have used one subroutine name for two subroutines. However, subroutine names within a program must be unique. Or, you have tried to pass a parameter to an internal subroutine. You can only pass parameters to external subroutines. |
Action |
Check names of defined subroutines. Check parameter passing. |
Text |
Sort field error; field has not previously been defined. |
Explanation |
The fields used as sort criteria in a SORT statement must be user-defined variables which have been previously defined, or database fields which are available within an active processing loop. The same field may not be referenced twice in the SORT key fields or the USING clause. See the Natural SORT statement documentation for further information. |
Action |
Check program and correct error. |
Text |
Incorrect specification of PERFORM SUBROUTINE statement. |
Explanation |
1) The name of the subroutine must not be enclosed in apostrophes. 2) If the PERFORM statement is used to invoke an inline subroutine, explicit parameters to be passed to the subroutine must not be specified with the statement. |
Action |
Check program and correct error. |
Text |
RETURN or END-SUBROUTINE misplaced. |
Explanation |
This error occurs under one of the following conditions: 1) A RETURN or END-SUBROUTINE was found, although there is no corresponding DEFINE SUBROUTINE. 2) A subroutine is empty, that is, there is no statement within the DEFINE SUBROUTINE statement block. |
Action |
Check program and correct error. |
Text |
The assigned work file (number) is incorrect. |
Explanation |
The work file number specified must be - a numeric constant in the value range (1:32), or - a numeric variable of type (B/N/P/I) defined with a CONST clause assigning a value in the range (1:32). |
Action |
Correct error in program. See the Natural documentation of the used statement for further information. |
Text |
Error in data field for READ/WRITE WORK FILE statement. |
Explanation |
Data fields may be specified as database fields or as user-defined variables. If the RECORD option is used, the variables must not have been previously defined and dynamic variables (if available) are not allowed. If the SELECT option is used, the variables may have been previously defined. Numeric constants may also be used with WRITE WORK FILE. |
Action |
Check program and correct error. |
Text |
Error in "FILLER nX" specification for READ WORK FILE. |
Explanation |
A filler may be specified in the definition of the data layout by using the notation "FILLER nX", where n is an integer number. |
Action |
Check program and correct error. |
Text |
Invalid specification of AT END OF FILE clause. |
Explanation |
The specification of the AT END OF FILE clause in a READ WORK FILE statement is only permitted if the ONCE option has also been specified. If the ONCE option is not specified, a normal processing loop is created with the end-of-file condition being handled as normal loop termination. |
Action |
Check program and correct error. |
Text |
Command / program name must start with a letter. |
Explanation |
The command - or the name of the program to be executed - you entered began with an invalid character. The first character of a system command or program name must be an alphabetical character, not a number or a special character. |
Action |
Enter a valid command or program name. |
Text |
Program name missing in READ command. |
Explanation |
The READ command reads a source object from the active Natural library (or optionally from the library specified with the command) into the editor work area appropriate for the object type. The correct syntax of the command is: READ object-name <library ID> library ID must not be specified if Natural Security is active. library ID must not begin with "SYS" (except SYSTEM). |
Action |
Enter READ command with a valid object name. |
Text |
Invalid command, or ... ... does not exist in library. |
Explanation |
One of the following has occurred: - You entered a value in the command line which is neither a Natural command nor the name of a Natural program contained in the active library or in a library defined as a steplib. - An object which is required during processing of a Natural executable is not contained in the active library or in a library defined as a steplib. - Your Natural session is currently applying system files other than those containing the object you specified. |
Action |
Enter a valid Natural command or the name of an existing Natural object. Use the command SYSPROF to check whether you are using the correct system file. |
Text |
SAVE or CATALOG command issued when work area empty. |
Explanation |
An object can only be SAVEd/CATALOGed from the editor work area. An object can be brought into the work area with a READ or EDIT command. (The command "RUN program-name" will also read the source of the program called "program-name" into the editor work area, before compiling and executing it.) |
Action |
Use READ or EDIT prior to using SAVE/CATALOG. |
Text |
Object name already exists; SAVE/CATALOG not executed. |
Explanation |
Natural requires that object names be unique. An object cannot be SAVEd or CATALOGed under a name which has already been given to another object. |
Action |
Either choose a different name for the object to be SAVEd/CATALOGed, or RENAME/PURGE/UNCATALOG/SCRATCH the existing object of that name before issuing the SAVE/CATALOG command. |
Text |
Invalid program name specified in SAVE/CATALOG command. |
Explanation |
A program name must begin with an alphabetical character and must not be longer than 8 characters. |
Action |
Enter a valid program name. |
Text |
READ WORK FILE ONCE not allowed in AT END OF FILE. |
Explanation |
A READ WORK FILE ONCE statement is not permitted within an AT END OF FILE clause. See the Natural READ WORK FILE statement documentation for more information. |
Action |
Correct error. |
Text |
Invalid parameters for USING in DEFINE DATA statement. |
Explanation |
The USING clause of the DEFINE DATA statement contains invalid parameters. |
Action |
Correct error. |
Text |
RUN command issued without program in work area. |
Explanation |
If there is a program in the editor work area, you can issue the RUN command without program name so as to compile and execute that program. If the editor work area is empty, you must specify a program name with the RUN command, so as to read a program into the work area, from where it is compiled and executed. |
Action |
Specify a program name with the RUN command, or read the source program into the work area with a READ or EDIT command before issuing RUN. |
Text |
CHECK command issued, but no program in work area. |
Explanation |
The CHECK command can only be used after a source program has been read into the source work area with an EDIT, READ, or RUN command. |
Action |
Use EDIT or READ to place program in source work area before issuing a CHECK command. |
Text |
Sub-/superdescriptor cannot be used in THRU clause. |
Explanation |
A subdescriptor or superdescriptor must not be used in a THRU clause. The REDEFINE statement may be used to create a variable which may be used in the THRU clause. A HISTOGRAM statement may be used to read the values of the sub- or superdescriptor in sequence, followed by a FIND statement using each value read to retrieve the records. |
Action |
Check program and correct error. |
Text |
Only "ON" or "OFF" allowed with UPDATE command. |
Explanation |
The UPDATE command may be used to disable or enable database updating: - "UPDATE ON" enables updating of the database. - "UPDATE OFF" disables updating of the database. Other command options are not allowed with the UPDATE command. |
Action |
Enter the command "UPDATE ON" or "UPDATE OFF". |
Text |
Invalid/missing block name in DEFINE DATA statement. |
Explanation |
One of the following errors was detected while processing the block name of a data block contained within a global data area: - An error in block naming conventions was detected. - The data block specified was not found in the current global data area. |
Action |
Check program and correct error. |
Text |
Invalid initial value definition in DEFINE DATA statement. |
Explanation |
The definition of initial values in the DEFINE DATA statement
is invalid. Note in particular that the Natural
session parameter DTFORM must correspond to the
value definition in the DEFINE DATA statement.
For example:
DTFORM=U and a D"YYYY-MM-DD" constant would cause an error.
Moreover, a numeric initial value must not have more precision or
scale digits than defined in the variable.
For example: 1 #FLD1 (N2.2) INIT <12.345> causes an error.
1 #FLD2 (N2.2) INIT <123.45> causes an error.
|
Action |
Correct error. |
Text |
Only alpha constant/field allowed for text in (RE)INPUT. |
Explanation |
The "text" in an INPUT or REINPUT statement can be specified with an alphanumeric constant, a previously defined alphanumeric variable, or an alphanumeric database field. |
Action |
Check that the variable used is defined as alphanumeric format or that the text constant is enclosed in apostrophes. |
Text |
Invalid use of GLOBAL in DEFINE DATA statement. |
Explanation |
"USING gda-name" is required after the keyword "GLOBAL" when referencing a global data area in a DEFINE DATA statement. |
Action |
Correct error. |
Text |
Invalid variable definition in REDEFINE statement. |
Explanation |
The variable definition is invalid for one or both of the following reasons: - invalid format specification; - invalid field length specification. |
Action |
Correct error. |
Text |
At least one field required for RESET statement. |
Explanation |
The RESET statement requires that at least one variable be specified after the keyword RESET (or after the keyword INITIAL, if this is used). |
Action |
Correct error. |
Text |
Field error in a COMPRESS statement. |
Explanation |
The COMPRESS statement compresses multiple field/literal values into another field. At least one value to be compressed must be specified. The value specified must be either a literal constant or an alphanumeric field. |
Action |
Correct error. |