This appendix lists messages that may appear in Repository, along with explanations of the problems that may have caused the error. If you receive messages that are not listed in this appendix, contact Synergy/DE Developer Support.
|
Unloading a repository to schema and then reloading it into a new repository oftentimes resolves unusual repository errors of unknown origin. |
Filename is not a version 7 or version 10 repository.
Repository version 10 can only open repository files that are in version 7 format or version 10 format. (Version 7 format was used by Repository versions 7, 8, and 9; it can be converted to version 10 format by the version 10 Repository.) It is likely that the specified repository predates version 7 and therefore can be neither opened nor converted by version 10. If this is the case, you must use the repository conversion program to convert it. Refer to the Repository release notes (REL_RPS.TXT) for instructions.
Filename is not a version 10 repository.
The specified repository is not in version 10 format. To convert it to version 10 format, open it for modification in Repository and select Yes when prompted to convert. Once a repository has been converted, it cannot be accessed by pre-version 10 Repository programs and tools.
Filename is not a version 10 repository. Do you want to convert it?
The repository being opened for modification is not in version 10 format. Select Yes to convert it. Once a repository has been converted, it cannot be accessed by pre-version 10 Repository programs and tools. Select No to leave the repository in its current format and return to the menu or input window.
A field or group with the same name already exists.
While adding or copying a field, you’ve specified the name of an existing field or group. Field names must be unique within the current structure or group.
A file with the same name already exists.
While adding or copying a file, you’ve specified the name of an existing file. Filenames must be unique within the repository.
A format with the same name already exists.
While adding or copying a format, you’ve specified the name of an existing format. Structure-specific format names must be unique within the current structure, and global format names must be unique within the repository.
A key with the same name already exists.
While adding or copying a key, you’ve specified the name of an existing key. Key names must be unique within the current structure.
A member with the same name already exists.
While adding an enumeration member, you’ve specified the name of an existing member. Member names must be unique within the current enumeration.
A relation with the same name already exists.
While adding or copying a relation, you’ve specified the name of an existing relation. Relation names must be unique within the current structure.
A structure with the same name already exists.
While adding or copying a structure, you’ve specified the name of an existing structure. Structure names must be unique within the repository.
A tag with the same name already exists.
While adding or copying a tag, you’ve specified the name of an existing tag. Tag names must be unique within the current structure.
A template with the same name already exists.
While adding or copying a template, you’ve specified the name of an existing template. Template names must be unique within the repository.
Access keys are defined for this structure. File type cannot be modified.
You cannot change a file type to Relative if access keys already exist for the structure, because relative structures can only have one access key (the record number). If the original file type is relative and the record number key has not been deleted, the only file type to which you can change is User defined.
Access keys cannot contain external segments.
You’ve specified the External segment type for an access key. Access keys define true keys in the data file and therefore cannot contain external segments.
Access keys cannot contain literal segments.
You’ve specified the Literal segment type for an access key. Access keys define true keys in the data file and therefore cannot contain literal segments.
Alias cannot be deleted. Field reference exists.
You cannot delete the current alias because it is referenced within one or more struct type field definitions. Use the Print Repository Definitions utility to see where it is referenced.
An access key already exists for this relative file type.
Only one access key, the record number, is allowed for a relative file. If you have modified the record number segment, reselect Access as the key type.
An alias with the same name already exists.
While adding an alias structure, you’ve specified an existing alias or structure name. Alias names must be unique within the repository not only among alias names, but among structure names as well.
An enumeration with the same name already exists.
While adding or copying an enumeration, you’ve specified the name of an existing enumeration. Enumeration names must be unique within the repository.
At least one field must be defined for the structure you are trying to assign.
The structure you’re attempting to assign to a file doesn’t contain any field definitions.
At least one field must be defined for the structure you are trying to reference.
The structure you’re attempting to reference as an implicit group or Struct type field doesn’t contain any field definitions.
Cannot open main repository file filename.
Repository can’t find the repository main file specified either by the RPSMFIL logical or the RPSDAT logical or in the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.
Cannot open Repository cross-reference file filename.
Repository can’t find the repository cross-reference file specified by either the RPSXFIL logical, the RPSDAT logical, or the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.
Cannot open Repository message file filename.
Repository can’t find the message file in either the RPSDAT logical or the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.
Cannot open repository text file filename.
Repository can’t find the repository text file specified either by the RPSTFIL logical or the RPSDAT logical or in the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.
Cannot open Repository window library filename.
Repository can’t find its window library file in either the directory specified by the RPS logical or the current directory. Another possible explanation is that you don’t have the necessary system privileges to access this file.
Creation specifications are incomplete.
You have not entered all the required information. To create a new repository, you must enter both repository main and text filenames.
Cross-reference specifications are incomplete.
You have not entered all the required information. To generate a cross-reference file, you must specify the repository filenames and the name of the cross-reference file into which to generate the information.
Definition specifications are incomplete.
You have not entered all the required information. To generate a definition file, you must specify both the structure name and the name of the .INCLUDE file into which your definition is to be generated. If you’ve designated that you want your definition to include a global data section, you must specify the global data section name.
Deleting the current field will invalidate overlay field field name.
You cannot delete the current field, because to do so would invalidate one or more overlay fields that are defined after it. For example, if your structure contains the following two fields:
FIELD_ONE ,A20 FIELD_TWO ,A15 @FIELD_ONE
and you try to delete FIELD_ONE, Repository won’t allow the deletion because it would cause FIELD_TWO to be an invalid overlay definition.
Enumeration cannot be deleted. Field reference exists.
You cannot delete the current enumeration because it is referenced within one or more field definitions. Use the Print Repository Definitions utility to see where it is referenced.
Enumeration cannot be deleted. Template reference exists.
You cannot delete the current enumeration because it is referenced within one or more template definitions. Use the Print Repository Definitions utility to see where it is referenced.
Enumeration no longer exists.
The enumeration you tried to select was deleted by another user between the time it was displayed in a list and the time you selected it.
External segment structure cannot be the current structure.
The structure name you specified in an external segment definition is the current structure. Because external segments define fields in other structures, you are not allowed to specify the current structure.
Field field name is a group. Deleting it will delete all group members as well. Do you want to continue?
The field you are deleting is defined as a group. To delete it will delete all its members, and all their members, and so forth. If you don’t want to delete the group, select No.
Field field name is a group. Clearing the “Group” field will delete all group members. Do you want to continue?
Saving the current group field definition will delete all group members, and all their members, and so forth. If you don’t want to delete the group, select No.
Field cannot be deleted. It is defined as a key.
The field you’re trying to delete is used as a key segment in the current structure. Before you can delete the field, you must delete all keys that reference it.
Field cannot be deleted. It is defined as a tag field.
The field you’re trying to delete is a tag field for the current structure. Before you can delete the field, you must remove it as a structure tag.
Field cannot be deleted. It is defined as an external key segment.
The field you’re trying to delete is used in an external key segment that is defined by another structure. Before you can delete the field, you must delete all references to it in any external structures.
Field data type modification will invalidate key key name.
You have modified the data type of a field that is referenced within a key definition, and whose data type is overridden within that key. The modified data type is invalid for the key’s overridden data type.
Field definition is incomplete.
You have not entered all the required information. When you define a field, you must specify the field name, data type, and size. Size is optional if you are defining a group field.
Field modifications will invalidate overlay field field name.
The field modifications you’re trying to make would cause one or more overlay field definitions to become invalid. For example, if your structure contains the following two fields:
FIELD_ONE ,A20 FIELD_TWO ,A15 @FIELD_ONE
and you’re trying to modify FIELD_ONE to be an A10 field, the modification would make FIELD_TWO’s overlay information invalid because it would attempt to overlay itself. You cannot change the size of FIELD_ONE unless you first modify FIELD_TWO appropriately.
File definition is incomplete.
You haven’t entered all the required information. When you define a file, you must specify the name, file type, description, and open filename.
File no longer exists.
The file you attempted to select was deleted by another user between the time it was displayed in a list and the time you selected it.
File type of specified structure does not match that of the file definition.
The file type of the structure you’re attempting to assign to a file doesn’t match the file type of the file definition.
Foreign keys cannot contain record number segments.
You’ve modified the key type of a record number key from access to foreign. You must now change the record number segment to be a field, literal, or external segment.
Format format name referenced by field field name no longer exists.
The global format that was assigned to this field has since been deleted. You can select another format, or you can press the “Abandon” shortcut to abandon your changes and then create a new format with the same name.
Format cannot be deleted. It is assigned to a field.
One or more fields use the structure-specific format you’re trying to delete.
Format definition is incomplete.
You have not entered all the required information. When you define a format, you must specify the format name, format type, and format string.
Format no longer exists.
The format you attempted to select was deleted by another user between the time it was displayed in a list and the time you selected it.
Internal reference buffer is full. Please exit to save changes.
Repository maintains many types of references so that it can preserve the integrity of your data base. It maintains a temporary reference buffer when you’re working with a structure, and then the temporary buffer becomes permanent when you save your changes. If this temporary buffer becomes full while you’re working with a structure, you will get this message. You must save your changes at this point by pressing the “Exit” shortcut. Once you’ve saved your changes, you can further modify the structure.
Invalid autokey specification.
Autokeys (sequence, timestamp, and create timestamp) must be a single segment consisting of an 8-byte field. They cannot be null, modifiable, or allow duplicates.
Invalid display format selected for given Date storage type.
Either the storage format for this date field is a period format (for example, YYYYPP) and you’re trying to assign a non-period display format to it, or the storage format is non-period (for example, YYMMDD) and you’re trying to assign a period display format to it.
Invalid group size specified. Group size must be equal to or larger than the size of its members.
In your group field definition, you’ve specified an explicit size, but the total size of the group members exceeds it. Edit the group members and adjust their total size, or increase the size of the group field.
Invalid key segment type.
In your key definition, you’ve specified a segment data type that is invalid for the data type of the field defined in that segment. When the field type is alpha, valid segment types are A (alpha) and N (nocase alpha). When the field type is integer, valid segment types are I (integer), S (sequence), T (timestamp), C (create timestamp), and U (unsigned integer). D (decimal) is the only valid segment type for decimal fields.
Invalid overlay field specified.
In your field definition, you’ve specified an invalid field name as the optional field to overlay. Press the “List Selections” shortcut to display a list of valid overlay fields.
Invalid parent template specified. Recursive references not allowed.
In your template definition, you’ve specified a parent template that is the descendant of the template you are currently editing. Attempting to reference this template creates a recursive reference.
Invalid precision specified.
For implied-decimal fields, the precision value must be less than or equal to the field size.
Invalid structure name specified. Recursive reference not allowed.
In your implicit group or Struct type field definition, you’ve specified a structure that contains a reference to the structure you are currently editing. Attempting to reference this structure creates a recursive reference.
Invalid tag comparison connector.
In your tag criteria, you’ve specified an invalid comparison connector.
Invalid tag comparison operator.
In your tag criteria, you’ve specified an invalid comparison operator.
Invalid value.
In your tag criteria, you’ve attempted to compare a numeric field with an alphanumeric literal.
Key cannot be deleted. It is defined as a “FROM” KEY in a relation.
You cannot delete the current key because it is used in a relation defined by the current structure.
Key cannot be deleted. Key reference exists.
You cannot delete the current key because it is used as a “to” key in a relation defined by another structure.
Key definition is incomplete.
You have not entered all the required information. When you define a key, you must specify the key name, the key type, and at least one segment definition.
Key type cannot be foreign. It is defined as a “TO” KEY in a relation.
You’ve attempted to change the type of the current key to Foreign. Repository won’t allow this, because the key is defined as a “to” key in a relation, and only access keys can be “to” keys. Access keys are used to specify relationships between files and are true keys in the data file.
Line line number too long (len=line length, max=150)... Truncated.
A line in the definition record that is being loaded from your .INCLUDE file exceeds the maximum allowed. It was truncated.
Load fields information is incomplete.
You haven’t entered all the required information. When you load fields, you must specify the .INCLUDE file and the record number.
Maximum field size (99999) has been exceeded.
The current field specification is larger than the maximum field size of 99,999. (If the field is arrayed, this is the maximum for each array element.)
Maximum implied-decimal field size (28) has been exceeded.
The current implied-decimal field specification is larger than the maximum implied-decimal field size of 28.
Maximum key size (255) has been exceeded. Data beyond 255 will be ignored.
The current key specification is larger than the maximum key size of 255. ReportWriter will use only the first 99 bytes of the key.
Maximum number of alias structures (999) has been defined.
You attempted to define more than 999 aliases. You cannot add any more alias definitions to the repository until you delete one or more.
Maximum number of enumerations (9999) has been defined.
You attempted to define more than 9,999 enumerations. You cannot add any more enumeration definitions to the repository until you delete one or more.
Maximum number of field references (6000) has been defined for template template name.
A field reference documents each time a template is used by a field. The maximum number of field references per template is 6,000. You cannot assign this template to any more fields until you remove it from one or more other fields.
Maximum number of fields (999) has been defined.
You attempted to define more than 999 fields. You cannot add any more field definitions to the current structure until you delete one or more.
Maximum number of fields (999) has been loaded.
Your .INCLUDE file contains more than 999 fields to load. The remaining fields have been ignored.
Maximum number of file references (200) has been defined for structure structure name.
You attempted to assign the specified structure to more than 200 files. You cannot assign the current structure to any more files until you disassociate it from one or more files.
Maximum number of files (9999) has been defined.
You attempted to define more than 9,999 files. You cannot add any more file definitions to the repository until you delete one or more.
Maximum number of formats (9999) has been defined.
You attempted to define more than 9,999 global formats. You cannot add any more global format definitions to the repository until you delete one or more.
Maximum number of key references (200) has been defined for structure structure name.
A key reference documents each time a structure is used as a “to” structure in a relation and each time a structure is used in an external key segment definition. The maximum total number of these two types of references is 200 per structure. You cannot define any more external key segments or relations for the specified “to” structure until you reduce the number of key references.
Maximum number of keys (99) has been defined.
You’ve attempted to define more than 99 keys for the current structure. You cannot add any more key definitions to the structure until you delete one or more.
Maximum number of members (100) has been defined.
You’ve attempted to define more than 100 members for an enumeration. You cannot add any more member definitions to the enumeration until you delete one or more.
Maximum number of relations (99) has been defined.
You’ve attempted to define more than 99 relations for the current structure. You cannot add any more relation definitions to the current structure until you delete one or more.
Maximum number of structure-specific formats (250) has been defined.
You’ve attempted to define more than 250 structure-specific formats for the current structure. You cannot add any more format definitions to the structure until you delete one or more.
Maximum number of structures (200) has been assigned to the file.
You’ve attempted to assign more than 200 structures to the current file. You cannot assign any more structures to the file until you disassociate one or more structures.
Maximum number of structures (9999) has been defined.
You’ve attempted to define more than 9999 structures. You cannot add any more structure definitions to the repository until you delete one or more.
Maximum number of tags (10) has been defined.
You’ve attempted to define more than 10 tags for the current structure. You cannot add any more tag definitions to the structure until you delete one or more.
Maximum number of template references (3000) has been defined for parent template template name.
A template reference is created each time a parent template is used by another template. The maximum number of parent references per template is 3000. You cannot assign this parent template to any more templates until you remove it from one or more other templates.
Maximum number of templates (9999) has been defined.
You’ve attempted to define more than 9999 templates. You cannot add any more template definitions to the repository until you delete one or more.
Maximum precision (28) has been exceeded.
The current precision specification is larger than the maximum precision size of 10.
Missing array dimension.
An array dimension is missing. For example, you may have specified Dim1 and 3, but not 2. Array dimension specifications must be contiguous.
Missing field name.
You’ve defined a key segment of type Field, but you haven’t entered a field name in the Field name or Literal column.
Missing group member definition. At least one member must be defined.
You have not defined any members for the current group field. Define one or more group members by selecting “Edit Group Members” from the Edit Field Functions menu, or clear the Group field.
Missing member definition. At least one member must be defined.
You attempted to save an enumeration definition containing no members. Enumerations must contain at least one member.
Missing segment definition.
You skipped a key segment definition. Segment definitions must be contiguous.
Missing segment definition. At least one segment must be defined.
You have not defined any segments for the current key. Segment number 1 must be defined.
Missing segment type.
You entered a field name, a structure, and/or a literal in the appropriate column(s), but you haven’t selected a segment type in the Seg type column.
Missing structure name.
You’ve defined a key segment of type External, but you haven’t entered an external structure name in the Structure name column.
Modifying enumeration enumeration name will affect one or more template and field definitions. Are you sure you want to save your modifications?
A change to the current enumeration data could affect field definitions that are .INCLUDEd into Synergy DBL source files or referenced in xfServerPlus method catalog definitions. If you don’t want to save the modifications, select No.
Modifying template template name will affect one or more template, field, and key definitions. Are you sure you want to save your modifications?
A change to the current template data will cause all affected field and template definitions to be modified. In addition, all keys (the size and type of keys in the current structure and external segments in other structures) that use those fields will be updated. The record sizes of all affected structures will be updated as well. If you don’t want to make such modifications, select No.
Moving the current field will invalidate its (an) overlay specification.
Either the field you’re attempting to move is an overlay field whose specification would be invalid at the new location, or moving the current field would invalidate one or more other overlay fields. If your goal is to redefine overlay attributes, remove all overlay attributes before reordering the fields. When the fields are in the desired order, add the overlay information.
New repository is invalid. Correct errors in schema file and reload.
Errors have been found in the schema file being loaded by the Load Repository Schema utility. Do not use the new or copied repository. Look at the log file that was created to determine which definitions contain errors. Correct the schema file and reload it.
Original repository cannot be copied. Files are in use.
You are merging a schema into an existing repository. The merge takes place using a copy of the original repository, but the copy cannot be created because the repository is in use by another user. Try again later when the repository is not in use.
Original repository cannot be replaced. Files are in use.
You are merging a schema into an existing repository. The merge takes place using a copy of the original repository, and you have chosen to replace the original when the merge is complete. But the original cannot be replaced because it is use by another user. You can either keep trying or clear the Replace original repository check box. If you are running rpsutl from the command line, repeat the command and suppress (-s) the replacement of the original repository.
Overlaid field does not exist.
An overlay specification in your .INCLUDE file refers to a field that doesn’t exist.
Print specifications are incomplete.
You have not entered all the required information. To print repository definitions, you must specify the repository filenames, the name of the file into which to print, and the print option. Additionally, if you’ve selected the Single option, you must specify the structure, file, template, and/or format name.
|
|
For detailed information on record locking in Repository, see Record locking. |
Record locked. Do you want to view the definition?
You have selected to modify a structure, file, template, format, or enumeration that another user is already modifying. Only one user at a time can modify these definitions. To view the definition without being able to modify it, select Yes.
Record locked. Please try again later.
Another user is currently modifying a record that you need to modify. This message can occur in any of the following circumstances:
- Deleting a structure, file, template, format, or enumeration
- Saving changes to a structure, file, template, format, or enumeration
- Adding or copying a structure
- Adding a group
- Saving a field that is a group
- Selecting the Attributes menu for the first time after having copied a structure
Record locked. Structure references cannot be saved.
Another user is currently modifying a structure that either references or is referenced by the definition that you are attempting to modify. Try again later.
Record locked. Template references cannot be saved.
Another user is currently modifying a template or enumeration that is referenced by the definition that you are attempting to modify. Try again later.
Referenced structure cannot be the current structure.
The referenced structure name you’ve specified within an implicit group or Struct type field definition is the same as the current structure name.
Relation cannot be examined. Specifications are invalid.
You’ve tried to examine a relation without entering all of the required information. You must specify the “from” and “to” structure and the “from” and “to” key before you can examine the relation.
Relation definition is incomplete.
You have not entered all the required information. When you define a relation, you must specify the “from” key, the “to” structure, and the “to” key.
Repository filenames cannot be the same.
When specifying the two repository files to verify and the two repository files to create, you did not enter unique filenames.
Repository files already exist. Do you want to merge the schema?
You have specified the name of an existing repository for the Load Repository Schema utility. If you want the utility to create a new repository into which to load the schema, select No and specify another repository. If you want to merge the schema definitions into the existing repository, select Yes. You must then specify how you want both new and existing definitions to be handled.
Schema specifications are incomplete.
You have not entered all the required information. To generate the schema (Synergy Data Language), you must specify the repository filenames and the name of the file into which the schema is to be generated. To load the schema, you must specify the name of the file that contains the schema to be loaded, the repository filenames, and the log filename.
Set specifications are incomplete.
You have not entered all the required information to set the current repository. You must enter both repository main and text filenames.
Size of selected Date type field cannot be modified.
Repository determines the field size based on the storage format selected for a Date type field. You cannot alter this size.
Size of selected Struct type field cannot be modified.
Repository determines the field size based on the structure selected for a Struct type field. You cannot alter this size.
Size of selected Time type field cannot be modified.
Repository determines the field size based on the storage format selected for a Time type field. You cannot alter this size.
“Structure” can only be specified when no explicit group members are defined.
You’ve specified a structure name (which designates an implicit group) when explicit group members are already defined. Either remove the structure name or delete the explicit group members.
Structure cannot be deleted. Field reference exits.
You cannot delete the current structure because it is referenced within one or more implicit group or Struct type field definitions. Use the Print Repository Definitions utility to see where it is referenced.
Structure cannot be deleted. File reference exists.
The current structure is assigned to one or more file definitions. You cannot delete it until you disassociate it from all files. Use the Print Repository Definitions utility to see where it is referenced.
Structure cannot be deleted. Key reference exists.
Either this structure is used as a “to” structure in a relation defined by another structure, or a field in this structure is defined as an external key segment by another structure. You cannot delete the structure.
Structure definition is incomplete.
You haven’t entered all the required information. When you define a structure, you must specify the name, file type, and description.
Structure has been modified. Do you want to save changes?
Whenever you modify a structure’s attributes, a temporary copy of that structure is created. As a result, you have the opportunity to abandon any changes you’ve made since entering the “Edit Attributes” function.
Structure is assigned to a file. File type cannot be modified.
You cannot modify the file type of this structure, because it must match the file type of the file it’s assigned to. Before you can change a structure’s file type, you must disassociate it from all files.
Structure is referenced as a group, and therefore at least one field must be defined.
The current structure is referenced within an implicit group specification. Groups must contain at least one member. Use the Print Repository Definitions utility to see where the structure is referenced.
Structure no longer exists.
The structure you tried to select was deleted by another user between the time it was displayed in a list and the time you selected it.
Structure structure name is referenced as an implicit group or structfield. Modifying it will affect one or more field and key definitions. Are you sure you want to save your modifications?
A change to the current structure data will cause all affected field definitions to be modified. In addition, all keys (the size and type of keys in the current structure and external segments in other structures) that use those fields will be updated. The record sizes of all affected structures will be updated as well. If you don’t want to make such modifications, select No.
Structure’s primary key does not match those of other assigned structures.
If more than one structure is assigned to a file, the primary key definition must be the same for all assigned structures. (The primary key is assumed to be the first key defined and must be an access key.) The following primary key information will be compared: key size; sort order; dups allowed flag; key data type; number of segments; and type, position, length and order of each segment. You will get this message if the key information is not the same.
Structures are assigned to this file. File type cannot be modified.
You cannot modify the file type of this file, because it must match the file type of the structures assigned to it.
Tag definition is incomplete.
You haven’t entered all the required information. When you define a field type tag, you must specify the field name and the comparison operator.
Tag fields are defined for this structure. Tag type cannot be modified.
You cannot modify the tag type of this structure because there are tag fields defined. Before you can change the structure’s tag type, you must delete all tag definitions.
Template cannot be deleted. Field reference exists.
You cannot delete the current template because one or more field definitions use it. Use the Print Repository Definitions utility to see where it is referenced.
Template cannot be deleted. Template reference exists.
You cannot delete the current template because one or more template definitions use it as a parent, which means you cannot delete it. Use the Print Repository Definitions utility to see where it is referenced.
Template definition is incomplete.
You haven’t entered all the required information. When you define a template, you must specify the name, data type, and size.
Template name and parent template cannot be the same.
The parent template name you’ve specified is the same as the current template name. The parent must be a template other than the current one.
Template no longer exists.
The template you attempted to select was deleted by another user between the time it was displayed in a list and the time you selected it.
This field is defined as a key. All affected keys in the current structure will be updated when you save changes. Are you sure you want to make modifications?
A change to the current field definition will cause the key size and type of all affected key definitions in the current structure to be modified. In addition, the current structure’s record size will be updated. If you don’t want to make modifications, select No.
This field is defined as an external segment by another structure. All affected keys in all external structures will be updated when you save changes. Are you sure you want to make modifications?
A change to the current field definition will cause the key size and type of all affected key definitions in external structures to be updated. The record sizes of all affected structures will be updated as well. If you don’t want to make modifications, select No.
“TO” KEY must be an ACCESS key.
You’ve tried to specify a foreign key as a “to” key in a relation. Only true keys in the data file (that is, access keys) can be used as “to” keys.
Validation specifications are incomplete.
You have not entered all the required information to validate the repository. You must specify the repository filenames to validate, as well as the log filename.
Verification specifications are incomplete.
You have not entered all the required information. To verify the repository, you must specify the repository filenames to verify, the repository filenames to create (if inconsistencies are found), and the log filename.
