Text |
Maximum number of categories defined. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Category ISN must be < 16384. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Missing category reference. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Missing reference in model node. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Missing component Sublist in attribute GLOBAL-ATTRIBUTES. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
First attribute in model is not GLOBAL-ATTRIBUTES. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Illegal sublist specification in occurrence. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
SLMO bit set but no ISN present in group attribute reference. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
No component sublist found in group attr. model, but no SLMO. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Loop limit exceeded when looking for comp.subl. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Occurrence has no component AX node where it should have one. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
No attribute ISN in model AD node. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Bad node found in model for UPDATE/STORE. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Bad subroutine CALL parameters. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Multiple attribute specified twice with same index. |
Explanation |
To begin with, this error may occur if the ISN and name of a linkage attribute are simultaneously specified. In the second place, it is encountered if a variable and a constant index are simultaneously used and the variable and the constant indices are equal. |
Action |
Check program and correct error. |
Text |
Bad node found in old occurrence. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Attribute in a periodic group specified twice with same index. |
Explanation |
To begin with, this error may occur if the ISN and name of a linkage attribute are simultaneously specified. In the second place, it is encountered if a variable and a constant index are simultaneously used and the variable and the constant indices are equal. |
Action |
Check program and correct error. |
Text |
Update of automatic attribute not allowed. |
Explanation |
If an automatic attribute occurs in an update view, no new value may be assigned to the automatic attribute after the FIND/GET statement. If an automatic attribute occurs in a STORE view, it must have the value "blank" or "0". |
Action |
Check program and correct error. |
Text |
Subtree attached in cat reference. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
No ISN in category reference. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Built-in check fail. |
Explanation |
An invalid value has been assigned to a descriptive attribute, i.e. a non-numeric value for a NUMERIC, or a LINE attribute contains a character < blank. |
Action |
Check program and correct error. |
Text |
Illegal ISN specified for linkage attribute. |
Explanation |
The value specified as ISN of a linkage attribute is not numeric. |
Action |
Check program and correct error. |
Text |
Illegal reference specified for linkage attribute. |
Explanation |
There are the following possibilities: 1) Only the name of a linkage attribute has been referenced but not the category, even though several categories are possible as domain. 2) A category that is not allowed as domain of the linkage attribute has been specified. 3) An ERE that is not library-independent has been specified as linkage attribute for a library-independent ERE. 4) The specified ISN is not the ISN of an occurrence of a category allowed as domain for the linkage attribute. |
Action |
Check program and correct error. |
Text |
No ISN in domain-reference. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Domain-reference with subtree but bad anchor. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Bad node found in domain sublist. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Illegal node encountered in model attribute/component Sublist. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Illegal node encountered. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Given category ISN does not exist. |
Explanation |
This error may occur after a DLOGON to a library in an environment which contains other categories than expected by the program. It may occur, also, if a direct call with an incorrect search value buffer has been performed. |
Action |
Use the Application clause of the DLOGON statement to prevent access to an environment with invalid categories. In case of an invalid direct call, check program and correct error. |
Text |
Occurrences not allowed to this category. |
Explanation |
This error may occur after a DLOGON to a library in an environment which contains other categories than expected by the program. It may occur, also, if a direct call with an incorrect search value buffer has been performed. |
Action |
Use the Application clause of the DLOGON statement to prevent access to an environment with invalid categories. In case of an invalid direct call, check program and correct error. |
Text |
Tried to DELETE/EXPORT/TRANSFER a category. |
Explanation |
It is not possible to delete/export a category via a DELETE or EXPORT statement. The TRANSFER statement may only be used for occurrences of multiple version categories. |
Action |
Use the Entire DB Utilities to delete/export a category. |
Text |
Component sublist entered for occurrence. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
Bad response code from FREEBUFF. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
More than one level of extension records specified. |
Explanation |
This error should occur only in internal Entire DB statements used in Entire DB ONLINE SERVICES and in Entire DB utilities. |
Action |
If this error occurs in a "normal" statement, contact Software AG. |
Text |
C*attribute has no numeric value in a STORE/UPDATE statement. |
Explanation |
Probably there is a redefinition with another format of C*attribute. |
Action |
Check program and correct error. |
Text |
Not even one group fits into extension record. |
Explanation |
Probably a periodic group contains a multiple attribute with too many values. A possible solution may be not to define the "extensions allowed" option for the periodic group itself, but to define it for a multiple attribute within the periodic group. |
Action |
Contact your Entire DB administrator to reorganize the Entire DB database. |
Text |
ERE overflow. |
Explanation |
Probably there are too many values for multiple attributes or periodic groups which have been defined without "extensions allowed". |
Action |
Contact your Entire DB administrator to define one of the multiple attributes or periodic groups as "extensions allowed". |
Text |
Synchronization failure when reading extension record. |
Explanation |
Due to a concurrent UPDATE on an ERE, a synchronization problem may arise between the timestamps of the old primary record and the new extension record. As a result, the Entire DB statement being processed cannot be terminated correctly. The ERE may be inconsistent until the UPDATE transaction is completed. |
Action |
Retry later. If the error still occurs after the maximum transaction time, finish your Natural session and contact Product Support. |
Text |
C*attribute specified more than once. |
Explanation |
This error may occur, if C*attribute is used simultaneously with a variable and a constant periodic group index, and the variable and the constant indices are equal. Apart from that, this error may occur in a direct call. |
Action |
Check program and correct error. |
Text |
Not even one node fits in EXTENSION RECORD. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Requested format conversion is not implemented. |
Explanation |
For each descriptive attribute only specific formats are allowed. This error may occur in case of an erroneous definition of descriptive attributes or if an illegal format has been specified in the format buffer for a direct call. |
Action |
Contact your Entire DB administrator. |
Text |
DV-node expected. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |
Text |
Directory belongs to other top level library. |
Explanation |
The Entire DB nucleus detected an unexpected situation, that probably resulted from an error in the Entire DB nucleus. |
Action |
To continue work with Entire DB terminate Natural session and begin a new one. Try to reproduce the error with DU=ON to get a dump and contact Software AG. |