Text |
Input upper limit > model upper limit. |
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 |
Conflicting duplication attribute options. |
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 |
Extension attribute option for singular attribute. |
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 |
Index attribute option for singular attribute. |
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 |
Conflicting index attribute options. |
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 |
Conflicting inversion attribute options. |
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 |
Duplication option entered for singular attribute. |
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 |
"OR" and "," mixed as separators in domain specification. |
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 open parenthesis. |
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 |
Domain specification started with "OR": no "," allowed. |
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 |
Illegal entry of category: only values allowed. |
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 entry of category: only occurrences allowed. |
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 |
Duplicate attribute/component/category/domain entered. |
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 |
Model attribute is automatic. |
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 |
"OMIT" entered for a mandatory attribute. |
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 |
Conflicting impacting options. |
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 |
Conflicting extension options. |
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 |
Model not group attr. category: comp. spec. not allowed. |
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 |
Model not entity category: attr. specification not allowed. |
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 |
Model not domain category: domain specification not allowed. |
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 |
Built-in ID 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 |
Domain specification 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 |
Input for global attributes did not match. |
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 |
Syntax-unit not name or ISN of a 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 as well, if a direct call with an incorrect search value buffer has been performed. |
Action |
Use the PRODUCT 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 |
Wanted record not found. |
Explanation |
In rare cases, it is possible that the database becomes inconsistent in the case of concurrent update. |
Action |
Contact your Entire DB administrator to delete the ERE with the invalid reference. |
Text |
Record type was not expected. |
Explanation |
In rare cases, it is possible that the database becomes inconsistent in case of concurrent update. |
Action |
Contact your Entire DB administrator to delete the ERE with the invalid reference. |
Text |
Read with timestamp not implemented. |
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 |
Premature end of sublist found in model for Global 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 |
Reference to extension record is illegal here. |
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 |
ERE option entered more than once. |
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 DDN 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 |
Alias name entered is not a valid ERE name. |
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 |
More than 15 alias names entered. |
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 |
ERE option entered is only valid for top-level category. |
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 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 |
Model is not entity category: occurrence not allowed. |
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 |
Record not in buffer. |
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 |
Root-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 |
Missing model attr/comp 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 |
Occurrence to be processed does not exist. |
Explanation |
Probably, the occurrence has been deleted in the meantime or a direct call with an invalid ISN in the control block has been issued. |
Action |
Check whether ERE to be processed still exists. If yes, check program and correct error. |
Text |
Occurrence is locked: UPDATE not allowed. |
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 |
Empty format buffer specified for STORE. |
Explanation |
At least the name of an entity or the relation elements of a relationship must be specified in a STORE statement. |
Action |
Correct error in program. |
Text |
Attribute sublist of occurrence not found. |
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 could not be processed in a STORE/UPDATE stmt. |
Explanation |
There are two possible situations which can cause this error: 1) An attribute is specified twice in a STORE/UPDATE statement. In particular, this occurs in connection with linkage attributes, where a linkage attribute has been specified both via its name and via its ISN. 2) An index > 1 has been used for an attribute which is not multiple. This may happen in a direct call or if an invalid DDM is used. |
Action |
Check program and correct error. |
Text |
No attribute reference in normal 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 |
No SLMO in model AD but no components 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 |
At end of command a slot is locked. |
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 |
At end of command a record is locked. |
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 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. |