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 technical support. |
Text |
Illegal or missing model 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 technical support. |
Text |
Illegal first node in model sublist (not = GLAT). |
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 technical support. |
Text |
AS-command: command option 2 must be "1". |
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 technical support. |
Text |
Missing category qualification for non unique 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 technical support. |
Text |
Category entered as domain reference 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 technical support. |
Text |
Illegal input after "BY" in UPDATE command. |
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 technical support. |
Text |
Internal CID has not been released at end of command. |
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 technical support. |
Text |
Data record to be written is not primary, extn. or directory. |
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 technical support. |
Text |
Attr/Comp/Dom not part of category to be updated. |
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 technical support. |
Text |
More than one ERE with same name/category found. |
Explanation |
This situation normally should not occur. Under certain circumstances, it is possible that in some rare cases of parallel update more than one ERE is defined with equal name and category. |
Action |
Contact your Entire DB administrator to rename one of the EREs. |
Text |
Free format update only implemented for categories. |
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 technical support. |
Text |
Invalid syntax of UPDATE command. |
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 technical support. |
Text |
Not enough room left in work area. |
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 technical support. |
Text |
Syntax-unit is not ")", "DDE" or entity 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 |
"RECURSIVELY" and "REFERENCED" are not allowed after "FIND VERSIONS". |
Explanation |
The "FIND RECURSIVELY" and "FIND REFERENCED" statements search for EREs, but not for a special version of EREs. |
Action |
Check program and correct error. |
Text |
Category reference in occurrence must be a value. |
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 technical support. |
Text |
Missing model node while generating category 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 technical support. |
Text |
Cat update only allowed for top-level categories. |
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 technical support. |
Text |
A set retained in "FIND VERSIONS" only allowed after "FIND VERSIONS". |
Explanation |
The set used in a FIND statement was retained in a "FIND VERSIONS" statement. This set may only be used after "FIND VERSIONS". |
Action |
Check program and correct error. |
Text |
Missing attribute sublist in basic 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 technical support. |
Text |
Retained set contains occurrences of other category. |
Explanation |
Set contains occurrences of other categories than indicated in the FIND statement. |
Action |
Check program and correct error. |
Text |
Buffer overflow: No RHD available. |
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 technical support. |
Text |
Buffer overflow: no directory overflow bucket available. |
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 technical support. |
Text |
Buffer overflow: no buffer slot available. |
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 technical support. |
Text |
Missing 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 technical support. |
Text |
Bad names 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 technical support. |
Text |
Category to be updated is not a domain 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 technical support. |
Text |
Category to be updated is not an entity 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 technical support. |
Text |
Category to be updated is not a group 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 technical support. |
Text |
Illegal input after "ADD". |
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 technical support. |
Text |
DEFINE/UPDATE category only after DLOGON for GLOBAL-LIBRARY. |
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 technical support. |
Text |
Bad history 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 technical support. |
Text |
Bad 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 technical support. |
Text |
Number of allocated slots < minimum number of slots required. |
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 technical support. |
Text |
Length of allocated work area < minimum length required. |
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 technical support. |
Text |
Security violation. |
Explanation |
The Entire DB user has no authorization for the desired action. |
Action |
Contact your Entire DB administrator. |
Text |
Group attributes without components. |
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 technical support. |
Text |
Syntax-unit is not number. |
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 |
Node in attr/comp Sublist of category has no attr-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 technical support. |
Text |
No user specified in DLOGON statement. |
Explanation |
A blank is specified as user name or no Entire DB user exists with the specified name. |
Action |
Retry DLOGON statement with correct user name. |
Text |
User is not authorized to DLOGON for this library. |
Explanation |
Specified user is not authorized to DLOGON for this library. |
Action |
Contact your Entire DB administrator. |
Text |
Invalid password in DLOGON statement. |
Explanation |
Either the DLOGON user has a password and no password was specified, or the password specified was invalid. |
Action |
Retry DLOGON statement with correct password. |
Text |
Component category 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 technical support. |
Text |
Missing component 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 technical support. |
Text |
DV- or SKIP-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 technical support. |
Text |
Invalid library password. |
Explanation |
In a DLOGON statement (syntax 2) the password of the library was missing or incorrect. |
Action |
Repeat DLOGON with correct library password. |
Text |
Specified library name is not name of a library. |
Explanation |
Specified library name in DLOGON statement is not name of a library. |
Action |
Retry DLOGON with correct library name. |
Text |
No default library. Library must be specifiedin DLOGON statement. |
Explanation |
DLOGON user has no default library. Library must be specified in DLOGON statement. |
Action |
Retry DLOGON statement with correct library name. |