| Text | File/DDM not defined for PROCESS statement. |
| Actn. |
Check program and correct error. |
| Text | Library must not be specified in security environment. |
| Expl. |
In an environment which is protected by Natural Security, the specification of a library is not possible. |
| Actn. |
Do not specify a library. |
| Text | Statement not allowed for DB2 access. |
| Expl. |
The following statements and constructions are not supported by DB2: 1. FIND UNIQUE 2. FIND COUPLED 3. FIND FIRST 4. FIND ... RETAIN AS 5. GET 6. any reference to *ISN 7. END TRANSACTION within an open database loop 8. BACKOUT TRANSACTION within an open database loop |
| Actn. |
Correct error in program. |
| Text | Receiving field of VAL function has invalid format. |
| Expl. |
The format and length must be the same as that of the target. This mathematical function extracts the numeric value from an alphanumeric field. The content of the alphanumeric field must be the character representation of a numeric value. Leading or trailing blanks are permitted. Decimal point and leading sign character will be processed. |
| Actn. |
Do not use formats A (alphanumeric) or B (binary). |
| Text | General syntax error detected in program. |
| Expl. |
A general syntax error was detected while syntax checking a source program. This message is output for various miscellaneous syntax errors for which Natural does not provide specific error messages. |
| Actn. |
Check program and correct error. |
| Text | Invalid entry in command line. |
| Expl. |
The structure of the command does not require the parameters that have been specified in the command line. Natural checks that the parameter specification agrees with the parameter structure expected by the individual command. Another reason for this error is that ADHOC is missing in batch mode. |
| Actn. |
Check command structure and resubmit. |
| Text | Only operators "EQUAL", "NOTEQUAL" valid with MASK/SCAN. |
| Expl. |
It is not possible to evaluate the operators GREATER or LESS THAN for a value when only certain positions are included in the comparison. Therefore, the only logical operator that are allowed with the special compare function MASK and SCAN are "EQUAL" and "NOTEQUAL". |
| Actn. |
Restructure the logical criteria to only use operators "EQUAL" or "NOTEQUAL" with the functions MASK and SCAN. |
| Text | Incorrect MASK argument construction. |
| Expl. |
The mask value must be enclosed in parentheses and may only contain the elements as described in the Natural documentation; see also extended error message NAT0017. |
| Actn. |
Check program and correct error. |
| Text | Invalid MASK construction for date check. |
| Expl. |
When a date check is to be performed, the specification for month/day/year must be 2 characters each (MM/DD/YY); for year, 4 characters (YYYY) may also be used. |
| Actn. |
Check program and correct error. |
| Text | Error in text list construction; contact administrator. |
| Expl. |
A discrepancy was detected in the number of alternative entries in the text list and the syntax list. The error is caused by an invalid modification of the text list. New entries can only be inserted in the text list by using the macro CSYN for synonym, not the macro CALT for alternative. |
| Actn. |
Retain the keyword on which the error has been detected and contact your Natural administrator. |
| Text | END statement missing. |
| Expl. |
The last statement of a Natural program must always be END. Alternatively, a period "." may be used. |
| Actn. |
Check program and correct error. |
| Text | Incorrect number of digits/value out of range. |
| Expl. |
For a field of format N or P, the overall maximum number of digits is 29, and the maximum number of digits after the decimal point is 7. For a field of format F the value specified must be in the range of values as described in the Natural documentation on floating-point constants. |
| Actn. |
Correct error in program. |
| Text | Invalid MASK construction for range check. |
| Expl. |
If a range check is to be performed, both values for the supplied range must have the same number of positions. Leading zeros must be supplied, as it is a check for positions in the value and the number of digits supplied in the range value. The number of positions to be included in the range check must also be specified. |
| Actn. |
Check program and correct error. |
| Text | Length of alphanumeric or unicode constant is zero. |
| Expl. |
The length of an alphanumeric or unicode constant must be greater than zero. |
| Actn. |
Check program and correct error. |
| Text | Error in hexadecimal constant: .... |
| Expl. |
1) Invalid hexadecimal character found. A hexadecimal constant may consist only of characters 0-9 or A-F. 2) Invalid number of characters specified. - The hexadecimal notation for constants of format A (H"..") requires 2 characters to represent one byte. Therefore, the number of hexadecimal characters supplied must be a multiple of 2. - The hexadecimal notation for constants of format U (UH"..") requires 4 characters to represent one Unicode code unit. Therefore, the number of hexadecimal characters supplied must be a multiple of 4. |
| Actn. |
Correct error. |
| Text | Number of bytes defined by hexadecimal constant > 80. |
| Expl. |
Hexadecimal constants are converted to internal byte representation in an intermediate buffer of 80 bytes. If literal constants of more than 80 bytes internal representation are to be defined, use the notation "XXXXXX"-"XXXXXX" to enter the value in multiple segments. |
| Actn. |
Check program and correct error. |
| Text | Invalid file specification in COUPLED clause. |
| Expl. |
The file specified in a COUPLED clause must be an Adabas file which has been physically coupled using the appropriate Adabas utility program. The file must not be a logical Natural system file. |
| Actn. |
Check program and correct error; or contact your Natural administrator about the file status. |
| Text | Invalid format/length for database count variable. |
| Expl. |
The format of the count variable for a periodic-group name or multiple-value field must be N or P. No decimal digits are permitted. |
| Actn. |
Check program and correct error. |
| Text | Invalid descriptor in SORTED BY clause. |
| Expl. |
The descriptor specified in the SORTED BY clause cannot be within a periodic group. If the descriptor is a multiple-value field, an index value must not be used. |
| Actn. |
Check program and correct error. |
| Text | Invalid use of variable index notation. |
| Expl. |
1. Variable index notation is not permitted with a search variable in the WITH clause of a FIND statement. 2. A variable array index (1:V) must not be used for redefine fields. |
| Actn. |
Check program and correct error. |
| Text | Page width (line size) exceeded in DISPLAY statement. |
| Expl. |
The total number of positions required for all columns resulting from a DISPLAY statement must not exceed the logical page size. |
| Actn. |
Reduce number of fields being displayed, or reduce spacing between columns, or increase the logical page size (where applicable), or place multiple values vertically in the same column. |
| Text | Invalid value format or incompatible field format. |
| Expl. |
In a SCAN condition, the - format of the value to be scanned for must be "A", "B" or "U"; - format of the field to be scanned must be "A", "N", "P" or "U"; - length of the value must be less than the length of the field. In a MASK condition, the - format of the field to be tested must be "A", "N", "P" or "U"; - format combination of first and second operand must be compatible; - first operand must not be smaller than the mask. |
| Actn. |
Check program and correct error. |
| Text | Error ... in line ... of data area ... processing .... |
| Expl. |
As indicated in the error message, an error has occurred in a specific line of a data area while processing a variable. |
| Actn. |
Correct error in data area. |
| Text | Error ... in line ... of copycode ... processing .... |
| Expl. |
As indicated in the error message, an error has occurred in a specific line of a copycode while processing a variable. |
| Actn. |
Correct error in copycode. |
| Text | RETRY statement only allowed in ON ERROR statement block. |
| Expl. |
The RETRY statement can only be used as a response to error NAT3145, which indicates that a record to be read for update is currently in "hold" status for another user. |
| Actn. |
Check program and correct error. |
| Text | Invalid reference to count of field in periodic group. |
| Expl. |
When referencing the count of the number of occurrences of an elementary field within a periodic group, the name of the periodic group must be used, not the name of the elementary field. |
| Actn. |
Check program and correct error. |
| Text | A global variable must not redefine another variable. |
| Expl. |
For reasons of addressability, parameter variables must not be defined by redefining an already existing variable. |
| Actn. |
Check program and correct error. |
| Text | Value to be used in SET CONTROL must be format "A". |
| Expl. |
The value (constant or variable) used to specify a terminal command with a SET CONTROL statement must be alphanumeric. |
| Actn. |
Check program and correct error. |
| Text | Count requested for a non-array field. |
| Expl. |
The count field only exists for database fields that are defined as multiple-value fields, periodic groups, or multiple-value fields within a periodic group. If the count of a multiple-value field within a periodic group is to be accessed, an index must be specified to indicate the occurrence of the multiple-value field in the periodic group for which the count is being requested. The field for which you have requested a count of occurrences is neither a multiple-value field nor a periodic group. |
| Actn. |
Check program and correct error. |
| Text | Index entry incorrectly specified for field. |
| Expl. |
An index was specified for a variable for which indexing is not permitted. Index specifications may only be used when defining/referencing an array. A database array can only be defined for a multiple-value field and for fields within a periodic group. If used as a search-variable in the WITH clause of a FIND statement, a multiple-value field must not be supplied with an index. When referencing an array, an index range specification was detected which exceeds the index range defined for one of its dimensions. |
| Actn. |
Check program and correct error. |
| Text | Index entry missing or invalid for an array. |
| Expl. |
When a multiple-value field or a field within a periodic group is referenced, an index must be specified to indicate the occurrence of the value to be selected. Default indices are created in WRITE or DISPLAY statements based on the setting of the session parameters MC and PC. A variable to be used as a variable index must have been previously defined before it can be used as an index notation. If a non-database field has been defined as an array, an index for each dimension must be specified when referencing the field. |
| Actn. |
Check program and correct error. |
| Text | Only one index/range specification allowed. |
| Expl. |
For multiple-value fields, or fields within a periodic group, only one index or range of indices may be specified. Two indices are only allowed for multiple-value fields within a periodic group. |
| Actn. |
Check program and correct error. |
| Text | Field or variable ... defined more than once. |
| Expl. |
If DEFINE DATA is used: A variable declared on level 1 must not be defined a second time, neither on level 1 nor on any other level. Without DEFINE DATA: A variable or database field can only be defined once using a format/length specification. When the variable is referenced in the program, no further format/length specification is possible. If the first field definition was made in a data area (LDA,GDA) which was included with a "DEFINE DATA .. USING .." statement, a further message (NAT0297) is put on the error stack, which indicates the data area name, the library and DB/FNR from which the field was included first. This message can be displayed with the system command LASTMSG. |
| Actn. |
Check program and correct error. |
| Text | Field reference error; reference invalid or missing. |
| Expl. |
Probable reasons for this error message: - You mistyped the variable name. - The variable name you specified has not yet been declared. - A specific database reference has been supplied, but the field is not present in the file referenced. - The value of a Natural system function has been referenced in the form *FUNCTION(FIELD), but no evaluation of the referenced system function has occurred for the field. |
| Actn. |
Check program and correct error. |
| Text | Invalid use of function, system function or sys. variable. |
| Expl. |
- Natural system functions and Natural system variables may only be used in a specific statement syntax within a Natural program. - The value of a system function or system variable may be assigned to a variable and then referenced. - In an INPUT statement, most system functions can only be used as output fields, but not as input fields. - The only system variable that can be used as an argument in the system function POS is *COM. - A Natural function call is not allowed in this context. For further information on Natural functions, Natural system functions or Natural system variables, see the Natural documentation. |
| Actn. |
Correct error in program. |
| Text | No access to database field; or REDEFINE variable exists. |
| Expl. |
Either the access to a database field is not possible at this point; or a variable to be used in a REDEFINE statement has previously been defined. A database field can only be referenced within an active processing loop. If the loop has been closed, a reference to fields from that database access is no longer possible. If you wish to use a value of a database field outside an active processing loop, assign the value to a user-defined variable. This error also occurs if a 4-digit array occurrence is incorrectly specified. 4-digit array occurrences must be preceded by a slash; for example, #ARRAY(/1000), not #ARRAY(1000). |
| Actn. |
Correct error in program. |
| Text | Index/format not permitted in Natural system function. |
| Expl. |
Format or length must not be specified for the reference to a Natural system function that had been previously evaluated nor for the reference to a Natural system variable. |
| Actn. |
Check program and correct error. |
| Text | Referenced field is not a descriptor. |
| Expl. |
The reference to a database field at this point requires that the field is a descriptor. Descriptors are required in the WITH clause of a FIND statement, as sequence fields in a READ LOGICAL statement, or when indicating the field for which values are to be provided in a HISTOGRAM statement. Under Adabas Version 5, this error also occurs if a field that is marked in the DDM as a "non-descriptor" is used as a search variable in a READ or HISTOGRAM statement. |
| Actn. |
Correct error in program. |
| Text | Sub/super/hyper/phonetic descriptor field improperly used. |
| Expl. |
A sub/superfield or sub/superdescriptor may be read from the database with an access statement (READ, FIND, HISTOGRAM, GET), but cannot be referenced in an update statement (STORE, UPDATE). The value for a hyper- and phonetic descriptor can only be used in a search criterion, but cannot be read from the database. |
| Actn. |
Correct error in program. |
| Text | Format for database field incompatible. |
| Expl. |
The format used for a database field is not compatible with the format of the field as defined in the data dictionary. |
| Actn. |
Check program and correct error. |
| Text | Requested field is not integer or has invalid length. |
| Expl. |
The operation requires the value of an integer field. This can be an integer constant, or a user-defined variable or database field of integer format. This error occurs if: - the field is of a format other than integer, or - the length of the field is not valid. |
| Actn. |
Use an integer format/length valid for the operand. |
| Text | Index range entry specified where not allowed. |
| Expl. |
A single index entry is required for this type of function; an index range is not permitted. Single index entries are required, for example, in the WITH clause of a FIND statement to indicate a specific occurrence of a periodic group field, or to specify the descriptor to be used for sequence control in a READ LOGICAL statement. |
| Actn. |
Check program and correct error. |
| Text | Intermediate storage overflow in arithmetic statement. |
| Expl. |
An overflow of an internal stack has occurred during the evaluation of an arithmetic expression. The internal stack is used to sequence the execution of arithmetic operations according to the parenthetical structure. |
| Actn. |
Reduce the number of operations to be performed within a single arithmetic operation. |
| Text | Operand in arithmetic statement is not numeric. |
| Expl. |
Only operands of format "N" (numeric unpacked) or "P" (packed numeric) are allowed in arithmetic expression. A numeric operand can be defined as a constant or as the content of a variable. |
| Actn. |
Check program and correct error. |
| Text | Invalid search criteria in FIND statement. |
| Expl. |
When evaluating complex search criteria, such as one with logical operator "OR", several separate database calls may be required. For a single FIND statement, a maximum of 64 database calls can be generated internally. |
| Actn. |
Reduce the number of search criteria. |
| Text | Field :1: previously defined in (:2:/:3:/:4:/:5:). |
| Expl. |
The variable :1: was declared twice. The first definition of the field was included via data area :2:, which was loaded from library :3:, database :4:, file number :5:. |
| Actn. |
Correct error in program. |
| Text | Incorrect parameters specified in SET KEY statement. |
| Expl. |
A push-button (PB=), menu (ME=), or bitmap (BM=) clause was detected in a SET KEY statement, but the corresponding parameters were incorrectly specified. |
| Actn. |
See the Natural documentation for detailed information. |
| Text | Total length of intermediate result exceeds 31 digits. |
| Expl. |
Natural supports operands up to a length of 31 digits. The length of intermediate results as operands is evaluated according to the rules for arithmetic operations. See the Natural documentation for details. |
| Actn. |
Check the digits of intermediate results according to the rules. Separate the arithmetic expression into several statements using explicit intermediate results. |
| Text | Operands are not data transfer compatible. |
| Expl. |
According to the format rules for data transfer, the source operand cannot be assigned to the destination field. For more information, see the Natural documentation, topic "Rules for Arithmetic Assignment". |
| Actn. |
Check program and correct error. |
