Text |
Format buffer element is group attribute. (Not implemented). |
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 |
Attribute 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 |
Category 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 |
Error in format buffer. |
Explanation |
An error in the format buffer was detected for a direct call. |
Action |
Check program and correct error. |
Text |
Record buffer overflow. |
Explanation |
The record buffer length specified in the control block for a direct call is less than the length resulting from the format buffer. |
Action |
Check program and correct error. |
Text |
Category in Search Buffer is attribute 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 |
Syntax unit in Search Buffer not cat-ISN, cat-name or "DDE". |
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 |
Syntax unit in Search Buffer not beginning of a search criterion. |
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 |
Bad built-in ID. |
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 |
Syntax unit is not a 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 |
Stack overflow. |
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 FIND-group. |
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 |
No command ID available. |
Explanation |
A too complex FIND statement has been specified. |
Action |
Subdivide your FIND statement into two less complex FIND statements. |
Text |
For direct call, invalid command ID specified in control block. |
Explanation |
A valid command ID must not begin with H"FF" or the letter "D". This error also occurs, if a command requires that the command ID has already be defined, and the command ID does not exist, or if a command ID already exists, when it must not yet exist, or if a command ID is defined not in the way as it is expected by the current command, for example for another category. |
Action |
Check program and correct error. |
Text |
An invalid value of an attribute was found in the search value buffer. |
Explanation |
Probably an attribute with illegal format has been defined or an illegal built-in category has been specified. The error may arise, also, if the maximum length of 119 bytes for a descriptor is exceeded. |
Action |
Contact your Entire DB administrator to correct the category definitions. |
Text |
Not linkage attribute ISN or name in search value buffer. |
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 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 |
Error in record buffer: variable length = 0. |
Explanation |
In a direct call for an update, the length byte = 0 was specified for a field with variable length. |
Action |
Check program and correct error. |
Text |
Not end of text in Search Buffer. |
Explanation |
An invalid DLOGON statement (with Syntax 2) or an invalid FIND NATIVE statement has been issued or a direct call with an invalid search buffer has been specified. |
Action |
Check program and correct error. |
Text |
No compare operator after category name/ISN. |
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 |
Category name or directory name not in category table. |
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 |
Only ISN-linkage-attributes > 0 and <> 0 are implemented. |
Explanation |
It was attempted to perform a FIND WITH ISN-linkage-attribute > x or <> x, where x is a non-zero number. |
Action |
Check program and correct error. |