Text |
Attempted to store library-dependent occurrence in GLOBAL-LIBRARY. |
Explanation |
It is not possible to store library-dependent occurrences in the GLOBAL-LIBRARY. A DLOGON statement may be missing. |
Action |
Check program and correct error. |
Text |
Attempted to TRANSFER a not validated version of an ERE. |
Explanation |
It is not validated, if there are mandatory attributes that have no values. In this case, TRANSFER is not allowed. |
Action |
Update entity to be transferred so that it is validated and retry. |
Text |
Error when requesting memory. |
Explanation |
'IMPORT', 'EXPORT', and CATTAB generation each require additional memory. This memory was not available. |
Action |
Enlarge region size. |
Text |
Extension record reference in model. |
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 |
Workfile has not been allocated. |
Explanation |
IMPORT and EXPORT require Workfile 1. |
Action |
Check and correct JCL and rerun job. |
Text |
Security code in internal format is too long. |
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 |
Category for UPDATE/STORE not validated. |
Explanation |
The category is not validated, unless all definitions required for the attributes of this category are made. |
Action |
Contact your Entire DB administrator. |
Text |
I/O error during workfile access for EXPORT/IMPORT. |
Explanation |
The physical damage of the file is a possible reason. |
Action |
Contact your Entire DB administrator. |
Text |
Domain sublist 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 |
No ')' or continuation of display-list. |
Explanation |
A direct call or a FIND NATIVE was issued with a syntax error in the Search Buffer. |
Action |
Check program and correct error. |
Text |
Universal linkage attribute 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 |
Category is not validated. |
Explanation |
Response code of LF command for a category that is not validated. The category is not validated, unless all definitions required for the attributes of this category are made. |
Action |
Make the missing definitions. |
Text |
Unmatching category and ERE references. |
Explanation |
In a STORE/UPDATE statement, either the category reference of a linkage attribute exists but no ERE reference, or the indices for category and ERE reference do not match. |
Action |
Check program and correct error. |
Text |
No reference, value or subtree in CAT-REF. |
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 |
Record to be deleted 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 |
Category specified for linkage attribute does not exist. |
Explanation |
In STORE/UPDATE statements, the category specified for a linkage attribute does not exist. |
Action |
Check program and correct error. |
Text |
Category specified for linkage attribute does not exist. |
Explanation |
Category specified for a linkage attribute does not match those categories defined as domain for the linkage attribute. |
Action |
Check program and correct error. |
Text |
No domain reference in AD node in attr. |
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 |
DV- or AD-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 |
Domain is not defined. |
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 reference to new model category. |
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 |
Restrictions not allowed (model has not been validated). |
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 |
Version has no library 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 |
Expected node 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 |
RESTORE not allowed in Top-Level-Library. |
Explanation |
Probably, DLOGON for the correct library is missing. |
Action |
Check program and correct error. |
Text |
ERE could not be validated. |
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 category specified for universal linkage attribute. |
Explanation |
For universal linkage attributes, references to EREs of all entity categories are allowed. If only the name of the EREs is specified, Entire DB cannot decide to which category the referenced ERE belongs. |
Action |
Check program and correct error. |
Text |
Missing CHANGED-BY 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 |
'REFERENCED' or 'REFERENCING' without 'RECURSIVELY' expe. |
Explanation |
A direct call or a FIND NATIVE was issued with a syntax error in the Search Buffer. |
Action |
Check program and correct error. |
Text |
'VERSIONS' not allowed here, will not be processed. |
Explanation |
A direct call or a FIND NATIVE was issued with a syntax error in the Search Buffer. |
Action |
Check program and correct error. |
Text |
Syntax-unit is not number or ')'. |
Explanation |
A direct call or a FIND NATIVE was issued with a syntax error in the Search Buffer. |
Action |
Check program and correct error. |
Text |
Syntax unit in Search Buffer is name or ISN of a group attribute. |
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 |
Too many relation elements entered for relation. |
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 component sublist in category RELATION-ELEMENTS. |
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 in component sublist of cat RELATION-ELEMENTS. |
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 input for relation 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 |
Not enough room left for creation of perm ERE. |
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 number of sublists in temporary 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 |
Category sublist expected in model but 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 |
Domain sublist expected in model but 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 |
Incompatible offsets (model and temporary 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 |
Premature end of sublist in model. |
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 |
Neither name nor ISN present in 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. |