Text |
Illegal combination of PROCESS quantifier and access type. |
Explanation |
The PROCESS quantifier can be ALL, (qty) or missing. Action type can be explicitly given by TYPE attribute. If the TYPE attribute is missing, the action type is implicitly given for the standard actions SELECT, STORE, UPDATE, DELETE. Otherwise the action type defaults to 'X'. Only the following combinations are valid: ! Action Type ! Quantifier ! Program Type !--------------------------------------------------------! !X ! missing ! DEFINE SERVER/DEFINE VIEW ! !A ! ALL, (Qty) ! DEFINE VIEW ! !M,O ! missing ! DEFINE VIEW ! |
Action |
Check and correct program. |
Text |
Invalid TYPE/DEST specification. |
Explanation |
The TYPE/DEST specification is incorrect because: - the given TYPE is not one of A (Access), M (Modify), O (Output) X (eXchange); or - the given DEST is not one of LOCAL, NET, DEBUG; or - neither TYPE nor DEST is given inside the brackets of the TYPE/DEST specification; or - DEST is given in front of TYPE; or - TYPE or DEST not followed by '='; or - the closing bracket is missing. |
Action |
Correct TYPE/DEST specification. |
Text |
WHERE/ORDER BY clause only allowed for action type Access |
Explanation |
The WHERE clause and the ORDER BY clause of a PROCESS statement accessing an Active View require action type Access. This may be implicitly given by the standared action SELECT or explicitly given by the type specification TYPE=A. |
Action |
Check and correct program. |
Text |
Invalid search variable specified in WHERE clause. |
Explanation |
A search variable denoted in the WHERE clause of a PROCESS statement is not defined in the view referred to by the PROCESS statement, or the search variable is used in combination with a local block field that has been mapped to another view field via a JOIN VALUE clause. |
Action |
Check and correct program. |
Text |
Nested PROCESS loops refer to the same view. |
Explanation |
There are two nested PROCESS loops in the program which refer to the same Natural view. This is not possible because each view corresponds to an instance of an Active View and each instance can only maintain one loop context. |
Action |
Use a copy of the view for the innermost loop. |
Text |
Illegal PROCESS statement against a native database. |
Explanation |
PROCESS with action type M, O or X refers to a native database view; or a program other than a View Program contains a PROCESS statement referring to a native database view; or a PROCESS statement referring to a native database view is closed by an END-PROCESS. |
Action |
Check and correct program. |
Text |
PROCESS with action type Modify without surrounding Access loop. |
Explanation |
An update against an Active View via PROCESS needs a surrounding loop much like the Natural statement UPDATE does. The surrounding PROCESS loop must refer to the same Natural view as the PROCESS statement for update. |
Action |
Make sure there is a surrounding loop. |
Text |
Error in ORDER BY clause. |
Explanation |
The ORDER BY clause is invalid because: - it appears in front of the WHERE clause; or - the given sort field is not a field of the view referred to by the PROCESS statement; or - there are more than three sort fields. |
Action |
Check and correct program. |
Text |
Handle/dynamic variables and X-arrays cannot be redefined. |
Explanation |
A variable declared DEFINE DATA LOCAL
- with type HANDLE, -> 1 #H HANDLE OF OBJECT
- as an alphan. or binary field -> 1 #AD (A) DYNAMIC
with a dynamic length,
- as an array with a variable -> 1 #VA (A10/1:*)
number of occurrences END-DEFINE
cannot be redefined, and it must not result from a redefinition.
If a group contains one of these fields in the first position, the
group cannot be redefined. |
Action |
Check and correct the variable definitions. |
Text |
UPDATE/DELETE table mismatch with SELECT statement. |
Explanation |
The table referenced in an UPDATE table WHERE CURRENT CURSOR or DELETE FROM table WHERE CURRENT CURSOR statement is not the table specified in the corresponding SELECT statement. |
Action |
Check and correct syntax. |
Text |
Incorrect alphanumeric constant specified in <<...>>. |
Explanation |
The constant specified in <<...>> does not adhere to the rules for Natural constants. For example, alpha constants must be enclosed in apostrophes. |
Action |
Check and correct syntax. |
Text |
Variable reference in <<...>> cannot be resolved. |
Explanation |
1) The token directly following the variable indicator (:) does not adhere to the rules for variable names. 2) The variable specified is not defined in the program. |
Action |
Check and correct syntax. |
Text |
No valid table reference found in FROM clause. |
Explanation |
The FROM clause contains no valid table name. Either specify a table name or a subquery of a joined table expression. |
Action |
Correct the FROM clause by specifying a valid table name. |
Text |
Program cannot be executed. |
Explanation |
While loading the Natural program, an internal, non-recoverable error has occurred. The program could not be loaded into the Natural buffer pool. |
Action |
Check program and/or contact your Natural administrator. |
Text |
Buffer pool full. |
Explanation |
The Natural buffer pool is full. To execute a Natural object, it must be loaded into the Natural buffer pool. If not enough space is available in the Natural buffer pool, the Natural object cannot be executed. |
Action |
Contact your Natural administrator. |
Text |
Program not ready for execution. |
Explanation |
The program to be executed is in the process of being cataloged by another user. When loading this program into the Natural buffer pool, Natural can not guarantee that the program code is in a correct and executable state. |
Action |
Execute the program at a later point in time. |
Text |
Program cannot be executed. |
Explanation |
This message appears if Natural has tried unsuccessfully 32 times to load the program into the Natural buffer pool. |
Action |
Contact your Natural administrator. |
Text |
Internal Natural DB2 error. |
Action |
Provide the Natural source and object program and contact Software AG support. |
Text |
No fields were selected by a FIND or READ statement. |
Explanation |
A FIND or READ statement does not retrieve any fields (empty view), but is directed to access an SQL database (e.g. DB2). This will result in the generation of an SQL SELECT statement with an empty column list. However, this is not permitted. |
Action |
Retrieve at least one field in the FIND or READ statement. |
Text |
Invalid Natural statement for DB2 access. |
Explanation |
The following Natural statements are not supported when accessing a DB2 database: - GET - STORE USING NUMBER (ISN) |
Action |
Check program and correct error. |
Text |
Insufficient space for SQL ... generation. |
Explanation |
During the generation, the corresponding buffer has overflowed. Either provide a greater thread/partition/region, or split the program's SQL parts and put them into different programs. The message relates either to the buffer containing the SQL statements or to the buffer containing the SQL XREF data. |
Action |
Start Natural in greater thread/partition/region, or reduce the number or size of SQL statements. |
Text |
Internal Natural DB2 error. |
Action |
Provide the Natural source and object program, and contact Software AG support. |
Text |
No fields assigned for an UPDATE statement. |
Explanation |
Natural DB2: An UPDATE statement is present, but no database fields are specified for the view. |
Action |
Assign a value to a DB2 column. |
Text |
A read-only field may not be modified. |
Explanation |
Natural DB2: Read-only fields were specified in an UPDATE statement. This is not allowed, because these fields may not be modified. |
Action |
Check program and correct error. |
Text |
UPDATE/DELETE must not be used in conj. with FIND SORTED. |
Explanation |
UPDATE/DELETE must not be used in conjunction with READ BY, FIND ... ORDER BY, SELECT ... ORDER BY or READ RESULT SET according to DB2 processing logic. |
Action |
Correct error in program. |
Text |
Field in SORTED BY clause is not referenced. |
Explanation |
Natural DB2: A field referenced in the SORTED BY clause is not referenced anywhere in the program. |
Action |
Check program and correct error. |
Text |
No primary key in an IMS access. |
Explanation |
Natural DB2 needs a primary key for UPDATE or DELETE if the loop contains a terminal statement. |
Action |
Change program according the Natural DB2 file-server logic. |
Text |
Data type not supported. |
Explanation |
The search criterion contains a Natural variable or constant
of a format that is not supported by the DB2 database manager.
Unsupported formats are:
N (numeric unpacked)
I1 (integer with length of 1)
L (logical)
D (date)
T (time) |
Action |
Do not use the above formats in a program that accesses a DB2 database. |
Text |
Null or length referenced without the master field. |
Explanation |
When referencing a length-indicator or null-indicator field, the corresponding master field to which the length or null indicator applies must also be referenced. |
Action |
Correct program. |
Text |
Null or length indicator cannot be used as descriptor. |
Explanation |
A null indicator or length indicator cannot be used as a descriptor, only master fields can be used as search criteria. |
Action |
Change search criterion in Natural program. |
Text |
SELECT FOR UDPATE, but UPDATE not allowed. |
Explanation |
This message also appears with the statement SELECT SINGLE FOR UPDATE where UPDATE is not allowed. |
Action |
Check and correct program. |
Text |
Invalid use of set name in search criterion. |
Explanation |
A set name has been specified in the basic search criterion of a FIND statement; however - the file to be accessed is not an Adabas file, or - the search criterion belongs to a COUPLED criterion. In either case, a set name must not be used. See the Natural documentation, FIND statement, for information on the use of a set name. |
Action |
Change the search criterion in your program. |
Text |
Invalid common table expression. |
Explanation |
The specified common table expression is invalid. A common table expression has to follow the keyword WITH̲CTE and has the syntax: cte-name (colname,...) AS (fullselect). Most likely, parentheses, the keyword AS or commas are missing or specified too often. |
Action |
Correct the common table expression. |
Text |
Scalar fullselect has to consist of a single column value. |
Explanation |
Scalar fullselect can be used as scalar values in expressions. Scalar fullselect is a fullselect enclosed in parentheses which returns a single row consisting of a single column value. The specified fullselect result set consists of more than one column. |
Action |
Specify only one column in the selection list of the fullselect. |
Text |
Logon failed after ... consecutive errors. |
Explanation |
The Natural session has been terminated as a result of too many unsuccessful logon attempts. |
Action |
Start a new Natural session after verifying your user ID and/or password. |