Text |
The parameter ... is not allowed in this context. |
Explanation |
The parameter named in the error message has no meaning in this context. |
Action |
Remove the parameter. If the parameters are correct and you are using Software AG"s DBMS-services, contact Software AG support because Natural has encountered an internal error. |
Text |
The value of parameter ... has an unpaired quotation mark. |
Explanation |
The value of the parameter named in the error message has one quotation mark. The value of a parameter must be enclosed by either two quotation marks or none. |
Action |
Insert or remove a quotation mark. If the syntax is correct and you are using Software AG"s DBMS services, contact Software AG support because Natural has encountered an internal error. |
Text |
The value or name of a parameter is missing before a delimiter. |
Explanation |
A delimiter should be preceded by either the name of a parameter or the value of a parameter. Either remove the delimiter, or insert the name or value of a parameter before it. |
Action |
If the syntax is correct and you are using Software AG"s DBMS-services, contact Software AG support because Natural has an internal error. |
Text |
The parameter ... is declared twice. |
Explanation |
The parameter named in the error message is declared twice. Two keywords may have been used which represent the same parameter. Alternatively, two database-numbers may have been used, although only one is allowed. |
Action |
Remove one of the parameters. If the parameters are correct and you are using Software AG"s DBMS-services, contact Software AG support because Natural has encountered an internal error. |
Text |
The equals sign is missing in the parameter ... |
Explanation |
The parameter named in the error message must have an equals sign. |
Action |
Insert an equals sign in the parameter. If the equals sign is present and you are using Software AG"s DBMS services, contact Software AG support, because an internal error occurred. |
Text |
The value of the parameter ... is missing. |
Explanation |
The parameter named in the error message must have a value. |
Action |
Insert the value of the parameter. If the value is present and you are using Software AG"s DBMS-services, contact Software AG support because Natural has encountered an internal error. |
Text |
The parameter ... requires a numeric value. |
Explanation |
The value of the parameter named in the error message must be numeric. |
Action |
Substitute a numeric value. If the value is numeric and you are using Software AG"s DBMS-services, contact Software AG support because Natural has encountered an internal error. |
Text |
This function requires the parameter ... |
Explanation |
A parameter required by this function is missing. The missing parameter is named in the error message. |
Action |
Add the missing parameter. If the parameters are correct and you are using Software AG"s DBMS-services, contact Software AG support because Natural has encountered an internal error. |
Text |
Two parameters are mutually exclusive. One is ... |
Explanation |
Two parameters are present which must not be used together. One of them is named in the error message. |
Action |
Remove one of the parameters. If the parameters are correct and you are using Software AG"s DBMS-services, contact Software AG support because Natural has encountered an internal error. |
Text |
A parameter, such as ..., is missing. |
Explanation |
A parameter is missing. It can be the parameter named in the error message. Add either the parameter named in the error message or another appropriate parameter. |
Action |
If the parameters are correct and you are using Software AG"s DBMS-services, contact Software AG support because Natural has encountered an internal error. |
Text |
The environment variable DBENV for this database is missing. |
Explanation |
The environment variable DBENV contains the path of the database. Access to the database is not possible without DBENV. |
Action |
Add this environment variable to your environment for the database. |
Text |
The parameter ... has an invalid value. |
Explanation |
The value of the parameter named in the error message is not valid. |
Action |
Substitute a valid value. If the value is valid and you are using Software AG"s DBMS services, contact Software AG support because an internal error occurred. |
Text |
The database you specified does not have a profile. |
Explanation |
A database must have a profile. |
Action |
Create a profile for the database. |
Text |
No database exists which has the number you specified. |
Explanation |
No database exists with the given number. |
Action |
Correct the number of the database. If the error occurs during automatic start via Natural check if the the database(s) specified in the parameter SDB exist(s). |
Text |
No database exists which has the name you specified. |
Explanation |
No database exist with the given name. |
Action |
Correct the name of the database. |
Text |
Left parenthesis missing in value of parameter ... |
Explanation |
The value of the parameter named in the error message should be preceded by a left (opening) parenthesis. |
Action |
Insert an opening parenthesis. If the syntax is correct and you are using Software AG"s DBMS services, contact Software AG support because an internal error occurred. |
Text |
Right parenthesis missing in value of parameter ... |
Explanation |
The value of the parameter named in the error message should be followed by a right (closing) parenthesis. |
Action |
Insert a closing parenthesis. If the syntax is correct and you are using Software AG"s DBMS-services, contact Software AG support because an internal error occurred. |
Text |
Right parenthesis or comma missing in value of parameter ... |
Explanation |
The parameter named in the error message is part of a list, so its value should be followed by either a comma or a right (closing) parenthesis. |
Action |
Insert either a closing parenthesis or a comma, as appropriate. If the syntax is correct and you are using Software AG"s DBMS services, contact Software AG support because an internal error occurred. |
Text |
This combination of parameters requires parameter ... |
Explanation |
The parameter named in the error message is required because another parameter is present. |
Action |
Add the required parameter. If the parameter is present and you are using Software AG"s DBMS services, contact Software AG support because an internal error occurred. |
Text |
File ... failed to open. |
Explanation |
The file named in the error message cannot be opened, either because it does not exist, or because it is already open. |
Action |
Check that the file exists. If it does exist, check that it is closed. If the file is already open, close it. |
Text |
Option ... is not yet implemented. |
Explanation |
The option named in the error message is not available in the current version of Natural. |
Action |
Either remove the option and circumvent the problem, or wait for a later version of the software. |
Text |
The format buffer has an error at position ... |
Explanation |
The FORMAT-BUFFER or FB parameter is wrong. |
Action |
Check the FORMAT-BUFFER parameter and correct the error. If the parameter is correct, and you are using Software AG"s DBMS services, contact Software AG support because an internal error occurred. |
Text |
... and another parameter have inconsistent values. |
Explanation |
The values of two parameters are inconsistent. One of these parameters is named in the error message. |
Action |
Check the parameters and correct the error. If the values are consistent, and you are using Software AG"s DBMS services, contact Software AG support because an internal error occurred. |
Text |
All fields already selected. |
Explanation |
You cannot select more fields than there are. |
Action |
Do not select any more fields. |
Text |
Errors occurred during a general database report by Adabas. |
Explanation |
One or more errors occurred while a general database report by Adabas was being executed. The next message explains why. |
Action |
Press the ENTER key to display the explanation. |
Text |
A report on database ... (...) has errors. |
Explanation |
One or more errors occurred while an Adabas report was being executed on the database whose name and number appear in the error message. The next message explains why. |
Action |
Press the ENTER key to display the explanation. |
Text |
A report on file ... (...) has errors. |
Explanation |
One or more errors occurred while an Adabas report was being executed on the file whose name and number appear in the error message. The next message explains why. |
Action |
Press the ENTER key to display the explanation. |
Text |
One or more errors occurred while Adabas was executing a report. |
Explanation |
The next message explains why. |
Action |
Press the ENTER key to display the explanation. |
Text |
The paths to the database are inconsistent. |
Explanation |
The path in the profile of the database is different from the path where the database is stored. This can happen if the COPY command of the operating system is used to move a database. |
Action |
To copy a database, only use Software AG"s DBMS-services. |
Text |
A path must not be longer than 64 characters. |
Explanation |
A path was specified with more than 64 characters. |
Action |
Do not use more than 64 characters to specify the path. |
Text |
One or more database files are missing. |
Explanation |
Files may have been deleted inadvertently. Unless the message appears during a backup, each missing file has the extension .DD, .CRI or .PRF. |
Action |
Restore the missing files. |
Text |
No command files exist. |
Explanation |
Before the menu item "Start DBMS Cmd-File" can be used, command files must exist. Command files are generated after an ADAREP, ADALOAD or ADAUNLOAD command. |
Action |
Issue an ADAREP, ADALOAD or ADAUNLOAD command, then specify a command file. |
Text |
Subdescriptors and superdescriptors cannot be loaded or unloaded. |
Explanation |
Subdescriptors and superdescriptors cannot be loaded or unloaded. |
Action |
Do not try to load or unload subdescriptors or superdescriptors. |
Text |
The specified format is incompatible with the existing format. |
Explanation |
Only compatible formats can be specified when data is loaded or unloaded. The following formats are compatible: SPECIFIED FORMAT EXISTING FORMAT A (alphanumeric) with A, B B (binary) with A, B, P, U G (floating point) with A, B, G P (packed decimal) with A, B. P, U U (unpacked decimal) with A, B, P, U |
Action |
Specify a format that is compatible with the existing format. |
Text |
The number of occurrences is incompatible with the format-buffer. |
Explanation |
The number of occurrences of the next Natural CONNECTION data file must be less than or equal to the number of occurrences of the selected field. |
Action |
Correct the Natural CONNECTION data file. |
Text |
The parameter NOT all databases is not allowed with ALL files. |
Explanation |
The parameter combination all databases = NO and all files = YES is not allowed by ADAREP. |
Action |
Choose another combination of parameters. |
Text |
One or more characters of the file name are invalid. |
Explanation |
The file name contains one or more characters that are invalid in the operating system. |
Action |
Specify a file name that does not contain invalid characters. |
Text |
Either the file cannot be opened or the file is empty. |
Explanation |
Either the file does not exist or the file is empty. |
Action |
Specify another file. |
Text |
The number of occurrences is invalid. |
Explanation |
The number of occurrences must be between 1 and 199 for a multiple field and between 1 and 99 for a periodic group. |
Action |
Check the number of occurrences and correct the error. |
Text |
The database number must be in the range 1 - 254. |
Explanation |
A database must have a ID between 1 and 254. The database ID is outside this range. |
Action |
Enter a database number between 1 and 254. |
Text |
Database (...) already exists. |
Explanation |
A database with the number or name already exists. Two databases cannot have the same number or name. |
Action |
Enter a different name or number for the database. |
Text |
No database (...) exists. |
Explanation |
No database exists which has the number or name you specified. |
Action |
Enter the correct name or number of the database. |
Text |
DB-file (...) already exists. |
Explanation |
A database file with the number or name already exists. Two database files cannot have the same number or name. |
Action |
Enter a different name or number for the database file. |
Text |
No DB-file (...) exists. |
Explanation |
No database file exists which has the number or name you specified. |
Action |
Enter the correct name or number of the database file. |
Text |
There is not enough space available on disk. |
Explanation |
The function could not be executed successfully because there is not enough space available on disk / diskette. |
Action |
Increase free space on disk. |
Text |
The Natural extension buffer has an error at position ... |
Explanation |
The buffer in which additional specifications for the fields in Natural format are made is erroneous. |
Action |
If the function was called from DBMS Services, contact Software AG, else check the contents of Natural extension buffer. |
Text |
Number of digits after a decimal point must be between 0 and :1:. |
Explanation |
For unpacked and packed numeric fields, the number of digits after the decimal point must be between 0 and the minimum of 7 or the length of the numeric field. |
Action |
Check the number of digits after the decimal point and correct the error. |
Text |
Overflow of floating point field occurs. |
Explanation |
Overflow of floating point field occurs. |
Action |
On the PC, the maximum value for a floating-point field is bigger than on the Mainframe. This error occurs, when such a field is unloaded in Natural-CONNECTION format. |
Text |
Startup configuration of database erroneous. |
Explanation |
The database mode (standalone, fileserver) and location do not match. In order to start a database in fileserver mode, the database must not be on the local PC. Drives equal / lower than "E" are expected to be local. |
Action |
Correct the startup configuration via the profile-function or copy the database to a location which belongs to the mode of the database. |
Text |
Source path and target path must be different. |
Explanation |
In this function it is not allowed to use the same path for source and target. |
Action |
Use different source and target paths. |