Text |
The suppression option for a group must be blank. |
Explanation |
A group can have only a level and a long-name. |
Action |
No action is required. The editor automatically corrects this error. |
Text |
A sub- or super-descriptor has an incorrect begin, end or length. |
Explanation |
A subdescriptor or superdescriptor must begin at a position greater than zero and less than the position at which it ends. The position at which it ends must not be greater than the length of the field on which it is based. The length of a superdescriptor must not be greater than 253. |
Action |
Enter values within the above ranges. |
Text |
A periodic group must be on Level 1. |
Explanation |
Periodic groups must not be defined within groups or within other periodic groups; they must always be on Level 1. |
Action |
No action is required. The editor automatically corrects this error. |
Text |
The suppression option of a numeric field cannot be fixed format. |
Explanation |
A field with format N (Natural) or U (Adabas) cannot have a fixed length. Its suppression option must be N or blank. |
Action |
Enter a valid suppression option. |
Text |
Periodic group descriptors cannot have fixed-format suppression. |
Explanation |
A descriptor in a periodic group cannot have a fixed length. Its suppression option must be N or blank. |
Action |
Enter a valid suppression option. |
Text |
A floating-point number must have fixed-format suppression. |
Explanation |
If the format of a field is G (Adabas) or F (Natural), its suppression option must be F. |
Action |
No action is required. The editor automatically corrects this error. |
Text |
Two fields of a database file have the same Adabas short name. |
Explanation |
The short name of a field must have two characters and must begin with an alphabetic character. It must not be in the range from E0 to E9 and it must not be the same as the short name of any other field in the same file. |
Action |
Enter a different short name for one of the two fields. |
Text |
The level of a field in a database file must not be changed. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
The format of a field in a database file must not be changed. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
The type of a field in a database file must not be changed. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
The long name of a field in a database file must not be changed. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
Short name of database file field must not be changed or deleted. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
The length of a field in a database file must not be changed. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
An area number must be between 1 and 30. |
Explanation |
The area where a database file is created must have a number between 1 and 30. |
Action |
Enter an area number between 1 and 30. |
Text |
Sub- / super-descriptors must be at the end of the database-file. |
Explanation |
Fields that have descriptor S must be at the end of the database-file- description. |
Action |
Move all subdescriptors and superdescriptors to the end of the database- file. |
Text |
A field must have a level between 1 and 7. No level was entered. |
Explanation |
You have not entered a level for the field. |
Action |
Enter a level between 1 and 7. |
Text |
This field must have a format. No format was entered. |
Explanation |
A format must be entered for every field that is neither a group nor a periodic group. |
Action |
Enter a format for this field. |
Text |
You specified an invalid editing mask. |
Explanation |
Valid forms of editing mask are described in the Natural Reference documentation. |
Action |
Correct the editing mask. |
Text |
The length of a field with fixed-format suppression must be 4. |
Explanation |
A field with the suppression option F has a length other than 4. |
Action |
Either change the length of the field to 4 or change the suppression option. |
Text |
Size of the internal Adabas buffer must be between 50K and 9999K. |
Explanation |
A size outside this range was entered in the profile of a database. |
Action |
Enter a size between 50K and 9999K. |
Text |
A database with the proposed name already exists. |
Explanation |
Two databases cannot have the same name. |
Action |
Enter a different name for the new database. |
Text |
Subdescriptors and superdescriptors must be on Level 1. |
Explanation |
Subdescriptors and superdescriptors must not be defined within groups. |
Action |
No action is required. The editor automatically corrects this error. |
Text |
Level numbers of adjacent fields must not differ by more than 1. |
Explanation |
Adjacent fields should either be on the same level or, if one of them is a group, their levels should differ by one. |
Action |
Correct the level of at least one field. |
Text |
A group must contain at least one field. |
Explanation |
Every definition of a group must be followed by the definition of at least one field that belongs to the group. The level of the field or fields must be one greater than the level of the group. |
Action |
Insert after the group a definition of each field that belongs to the group. |
Text |
Two fields of a file have the same long name. |
Explanation |
All fields of a file must have different long names. |
Action |
Enter a different long-name for one of the two fields. |
Text |
A field must have a long name. No long name was entered. |
Explanation |
You have not entered a long name for the field. |
Action |
Enter a long name for the field. |
Text |
The file had one or more blank lines. They have been deleted. |
Explanation |
A file description must not have blank lines. |
Action |
No action is required. The editor automatically corrects this error. |
Text |
No database file ... exists. |
Explanation |
Either the database file has never been created or it has been deleted. |
Action |
Use the Adabas-utilities to create the database file, then edit it to define your DDM-file. |
Text |
No file ... exists. |
Explanation |
The file named in the error message does not exist. Enter the correct name of the file. If the file name starts with D00nnn check if the correct DBID is entered. Check the directory specified in the environment variable DBENV or the directory which was specified as Adabas Utility parameter. |
Action |
see explanation |
Text |
An error occurred while file ... was being read or written. |
Explanation |
Internal error. |
Action |
Contact Software AG support. |
Text |
Adabas short name cannot be generated. |
Explanation |
All possible Adabas short names have been used in this database file so the editor cannot generate another one. |
Action |
Delete any fields that are no longer needed. |
Text |
Either a PF key has 2 functions, or one function has 2 PF keys. |
Explanation |
Either two functions are assigned to the same PF key, or the same function is assigned to two PF keys. |
Action |
Assign each function to a separate PF key and do not assign more than one function to any PF key. |
Text |
A Field used in a sub- or superdescriptor cannot be changed. |
Explanation |
A field cannot be changed if it is used in any subdescriptor or super- descriptor. |
Action |
Remove the field from every subdescriptor or superdescriptor that uses it. |
Text |
Number of field occurrences in a database file must not change. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
A subdescriptor or superdescriptor must use one or more fields. |
Explanation |
A subdescriptor must use part of one field and a superdescriptor must use at least part of two or more fields. |
Action |
Enter the fields that are used by the subdescriptor or superdescriptor. |
Text |
No userviews are defined for this database file. |
Action |
No action is required. |
Text |
Specified file name does not exist in specified database. |
Action |
Specify the correct database and file. |
Text |
You must specify the database in which files are to be listed. |
Explanation |
You did not specify a database so the files of a database could not be listed. |
Action |
Specify a database. |
Text |
Internal editor buffer overflow. |
Explanation |
When there are more than 1000 lines in your edit area, an internal editor buffer overflow occurs. |
Action |
Reduce the number of lines in the edit area. |
Text |
A DDM with that name exists already for DBID ... with FNR ... |
Explanation |
DDM with the specified file number and database number cannot be generated, because a DDM with that name already exists. |
Action |
Choose a different DDM name. |
Text |
Suppression option of a field in a database file must not change. |
Explanation |
When a file contains data, the database file must not be changed. |
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 |
No long names in the database file (upgrade active databases). |
Explanation |
This is the first time that an FDT has been edited since version 1.0.3 of the Adabas utilities was installed. In version 1.0.2, long names were stored in the database file. In version 1.0.3, they are stored in the database. |
Action |
Use the upgrade utility for active databases to copy the long names into the database. |
Text |
Some fields in the database do not have long-names. |
Explanation |
An error occurred when the file was stored. |
Action |
Edit the file, add the missing long names and save the file. If this has no effect, contact Software AG support because the DBMS could have an internal error. |
Text |
The format of a DDM field must be numeric or alphanumeric. |
Explanation |
An alphanumeric database file format can be changed to numeric, and numeric format can be changed to alphanumeric. No other change of format is allowed. |
Action |
No action is required. The editor automatically corrects this error. |
Text |
Size of Adabas communication area must be between 3K and 64K. |
Explanation |
The profile of a database has an invalid size for the Adabas communication area. |
Action |
Enter a size between 3K and 64K. |
Text |
Number of log commands must be: 0 if no log file; >=0 otherwise. |
Explanation |
The number of commands to be logged must be zero if there is no log file and must greater than or equal to zero if there is a log file. |
Action |
Enter a valid number of commands to be logged. |
Text |
The page size of an Adabas database must be 1K, 2K, 4K, or 8K. |
Explanation |
An invalid page size was entered when creating an Adabas database. |
Action |
Enter a valid page size. |
Text |
The file ... failed to close. |
Explanation |
Natural has encountered an internal error. |
Action |
Contact Software AG support. |
Text |
The file ... failed to execute. |
Explanation |
Internal error. |
Action |
Contact Software AG support. |
Text |
You have not specified a library. You must log on to a library. |
Explanation |
Before you can start working, you must log on to the library in which you wish to work. |
Action |
Log on to a library. |