Text |
A library ... cannot be created. |
Explanation |
Either the name of the library is invalid, or a directory cannot be created for the library because there is no more space for directories. |
Action |
Check that the name of the library is valid in Natural and, if necessary, correct it. If this has no effect, delete any directories that are no longer needed. |
Text |
Either the path is invalid or the directory does not exist. |
Explanation |
Either you specified a path which is invalid in the operating system or no directory exists which matches your specification. |
Action |
Enter a valid path to a directory that exists. |
Text |
The database ... (...) cannot be closed. |
Explanation |
The database whose name and number appear in the error message cannot be closed, because another process is using it. |
Action |
End the other process. |
Text |
WARNING: A field was truncated when it was loaded. |
Explanation |
Not all information in the field was loaded. |
Action |
If you do not wish to lose information, choose or create a field in the database which is long enough to hold all the information, and load the information into that field. |
Text |
The fields are not compatible with the Natural CONNECTION file. |
Explanation |
The formats or lengths of the fields you specified do not match the fields in the Natural CONNECTION file. |
Action |
Specify the fields correctly. |
Text |
Function is not possible for the contents of the file. |
Explanation |
Examples: The format of a file which is to be loaded into a database may be wrong. Or fields were selected to be loaded into a file but their lengths do not match the contents of the file. |
Action |
Check the format of the file and the lengths of the fields. |
Text |
Either one parameter or the number of parameters is invalid. |
Explanation |
A valid name of a program has been entered with either an invalid parameter or an invalid number of parameters. |
Action |
Enter a valid number of valid parameters. |
Text |
A database file or DDM which is empty cannot be stored. |
Explanation |
An database file or DDM must have at least one field before it can be stored. |
Action |
Insert at least one field into the FDT or DDM. |
Text |
A file with the proposed name already exists. |
Explanation |
Two files cannot have the same name. |
Action |
Enter a different name for the new file. |
Text |
The length of a numeric field must be between 1 and 29 (15). |
Explanation |
A numeric field has a length outside this range with Natural mode (Adabas mode for packed fields). |
Action |
Enter a length within this range. |
Text |
No more memory is available. |
Explanation |
Either the operating system is not configured correctly or there is not enough space on the disc for the system swap file. Another possibility is that the internal Natural buffer sizes USIZE and SSIZE are too small. Check the configuration settings of the operating system and correct them if neccessary. Then check the available disk space for your system swap file. Additionally, check your USIZE and SSIZE settings within NATPARM and enlarge them if they seems to be too small. |
Action |
Please contact your system administrator for further help. |
Text |
A database with the proposed number already exists. |
Explanation |
Two databases cannot have the same number. |
Action |
Enter a different number for the new database. |
Text |
Please select all the elements of the group (one level higher). |
Explanation |
Normally, all elements of a group can be selected simply by marking the group. This group either contains a multiple field or is a periodic group. In either case, this group cannot be selected as a whole by marking it. Each element of the group must be marked individually. |
Action |
Mark all the elements of the group individually. |
Text |
The database must not be active when this function is executed. |
Explanation |
This function requires that the database is not active. |
Action |
Close the database. |
Text |
Number of digits after the decimal point must be between 0 and 7. |
Explanation |
For unpacked and packed numeric fields, the number of digits after the decimal point must be between 0 and 7. |
Action |
Enter a number within this range. |
Text |
The long name of part of a sub- or super- descriptor is invalid. |
Explanation |
A sub- or super- descriptor can only contain fields that have already been defined. |
Action |
Either define a field with this long name or remove this long name from the sub- or super- descriptor. |
Text |
The format type specified is not yet implemented. |
Explanation |
The following format types are currently not implemented: C, D, I, L, T. |
Action |
Specify a format type that is implemented. |
Text |
The total field length of a file description must not exceed 64K. |
Explanation |
The length of all fields defined in a Adabas file description must not exceed 64K. |
Action |
Decrease field length or number of fields in the database file description. |
Text |
The short name specified does not exist in the database file. |
Explanation |
The short name for the DDM field does not exist in the corresponding database file. |
Action |
Select a new DDM field with the insert command. |
Text |
The specified file cannot be printed in this environment. |
Explanation |
It is not possible to print the specified file, because you are not logged in a local drive. |
Action |
Logon to a local drive before starting Natural. |
Text |
No read/write access to this parameter file. |
Explanation |
You tried either to read another user's parameter file or to overwrite the default parameter file NATPARM. |
Action |
Logon with the correct user ID or contact your Natural administrator if changes in NATPARM are required. |
Text |
No descriptor allowed for multiple and periodic group fields. |
Explanation |
When a file contains data, it is not possible to define a descriptor for multiple and periodic group fields. |
Action |
No action is required. The editor automatically corrects this error. To change the database file, you must first unload the data from the file. |
Text |
Phonetic descriptors are not yet implemented. |
Explanation |
With the current PC-DBMS version, it is not possible to define phonetic descriptors. |
Action |
Select a valid descriptor option from the given choice list. |
Text |
Multiple field type not possible for normal database field. |
Explanation |
When a database field is defined as a normal field, you cannot define it as a multiple field within the DDM. If you do so, a format buffer error occurs, when you try to read the contents of this field. |
Action |
No action is required. The editor automatically corrects this error. |
Text |
The DDM cannot be checked against the database file description. |
Explanation |
When you check a DDM, first the syntax of all DDM fields is checked. Then the DDM fields are checked against the corresponding file description (DBID and FNR within the header). The second check can only be performed when the database is of type Adabas and is active. |
Action |
Save the DDM, start the corresponding database and edit the DDM again. |
Text |
The category ISN must be in the range from 0 to 65535. |
Explanation |
When you edit a DDM for Entire DB, the field name, file number and default sequence are represented by a category ISN, which must be in the range from 0 to 65535. |
Action |
Enter a number within this range. |
Text |
The DDM has a database type which cannot be processed. |
Explanation |
When you try to include a DDM as a template of a FDT, the database type of the DDM must be supported within the utility to process this DDM. For example, you try to include a DDM which is defined for Entire DB. This DDM cannot be included in the FDT editor, because the editor only processes Adabas FDTs. |
Action |
Specify a DDM with a supported database type. |
Text |
No further category ISNs can be generated. |
Explanation |
All category ISNs have been used in this database file. |
Action |
Delete fields which are no longer needed. |
Text |
One or more fields are missing within the DDM line. |
Explanation |
The editor detected missing fields within the DDM description. |
Action |
Complete the information within the DDM line. |
Text |
NO Adabas files are coupled with this DDM. |
Explanation |
When scanning the DDM source no coupled file information was found. |
Action |
See Adabas documentation for further information about physical file coupling. |
Text |
Generation of DDM failed due to internal SQL error ... |
Explanation |
The generation of a DDM from a SQL table was interrupted because an internal SQL error occurred. |
Action |
See your SQL documentation for further information about error codes. |
Text |
The DDM cannot be checked against the SQL table. |
Explanation |
When you check a DDM, all DDM fields are checked for syntactical correctness. However, NO check against the SQL table can be made within the DDM editor, because after the generation of the DDM, the connection to the SQL database is closed. |
Action |
See your SQL documentation for further information about possible modifications. |
Text |
When editing SQL DDMs, no verification tests are performed. |
Explanation |
When you edit a DDM, all DDM fields are read into the edit area. However, NO check against the SQL table can be made within the DDM editor, because NO connection to the SQL database will be established. |
Action |
See your SQL documentation for further information about possible modifications. |
Text |
SQL table lists are not provided for this database system. |
Explanation |
It is not possible to show the SQL table list, because Entire ACCESS does not provide catalog information for this database system. |
Action |
Enter the desired table owner and table name (no wildcards possible). |
Text |
No SQL tables found. |
Explanation |
You specified a table owner/name combination, where no SQL tables exist or the SQL tables are not accessible. |
Action |
Try to show all SQL tables, which you can access by specifying wildcards. |
Text |
LOGON to SQL database failed. |
Explanation |
You specified an invalid user name or password. |
Action |
Contact your database administrator. |
Text |
Function disallowed according to Predict definition. |
Explanation |
Within the Predict protection screen, the SYSDDM utility has been set to D (disallowed) or C (connected). |
Action |
See Predict Administration documentation for further information. |
Text |
The DDM could not be generated. Writing to a SPF session failed. |
Explanation |
When generating a DDM from a SQL table, the table data are buffered within a SPF data session. The write can fail if the internal editor buffer pool is full. |
Action |
Increase the number of logical files and/or buffer pool blocks within the editor profile. To make the settings active, terminate and restart Natural. |
Text |
SQL table name was invalid or an internal runtime error occurred. |
Explanation |
When generating a SQL based DDM, Natural callnats are executed. Within such a callnat, a Natural runtime error occurred. |
Action |
Try first to get a list of all available SQL tables and select one. If the problem persists, contact Software AG support. |
Text |
A work file name must not be longer than 253 characters. |
Explanation |
The path and the name of a work file must not be longer than 253 characters. This error occurs also if the name contains blanks only. The length of the variable/constant must not exceed 1024 bytes. |
Action |
Choose a shorter name, e.g., using environment variables. |
Text |
A work file type must not be longer than than 253 characters. |
Explanation |
The type of a work file must not be longer than 253 characters. This error occurs also if the name contains blanks only. All correct types are shorter. The length of the variable/constant may not exceed 1024 bytes. |
Action |
Choose a correct type. |
Text |
The work file type :1: is unknown. |
Explanation |
The specified work file type is unknown. This usually means that it is incorrect. This error occurs also if the name contains blanks only. |
Action |
Choose a correct work file type. |
Text |
Illegal work file name extension ".NCF" |
Explanation |
The specified work file name is illegal because it conflicts with Entire Connection's format file. The format file has the extension .NCF, and so the specified work file name must not use the extension .NCF. |
Action |
Choose a correct work file name. |
Text |
The DBMS type in the DDM header is not defined. |
Explanation |
Before a DDM is loaded into the editor and during CATALOG, it will be checked if the type of the DBID, which is defined in the global config file, matches the DBMS type in the DDM header. |
Action |
Define the correct DBMS type in the global config file, section 'DBMS assignments'. |
Text |
DDM generation failed due to wrong datatype combination. |
Explanation |
Natural does not support Oracle tables which contain both LONG or LONG RAW and BLOB or CLOB data types. |
Action |
Change the definition of the Oracle table so that it contains only column types LONG and LONG RAW, or BLOB and CLOB. |
Text |
The DDM source contains invalid field attribute(s). |
Explanation |
The DBMS for which the DDM has been defined does not support the extended field attribute(s) found in the DDM source. |
Action |
Load the DDM into the editor. The DDM editor skips the unknown field attribute(s) when loading the DDM. Afterwards you can stow the DDM. |
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. |