Overview

Data Transfer Between Dictionaries › Overview

Overview

To maintain existing entity relationships while transferring data, the user must transfer entity definitions in the proper order. The following list specifies the order in which entities, entity options, and nests should be added to or replaced in the target dictionary:

Alternative pictures
Comment keys
Relational keys
Users
Classes
Attributes for classes defined with manual attributes
User-defined entities that IDD will reference
Systems
Files
Elementary elements
Subordinate elements
Group elements
Records
Modules
Programs
User-defined entities that reference IDD entities

The Effect of ATTRIBUTES ARE AUTOMATIC

Attributes within classes assigned the ATTRIBUTES ARE AUTOMATIC qualifier are transferred automatically. Therefore, to facilitate the transfer, it is recommended that the user change all class definitions that include the ATTRIBUTES ARE MANUAL specification to ATTRIBUTES ARE AUTOMATIC and return the specification to ATTRIBUTES ARE MANUAL when the transfer is complete.

Handling Unresolved Relationships

Even if entities are transferred to a dictionary in the order specified above, unresolved relationships may exist if any of the following clauses are present in USER, SYSTEM, PROGRAM, and FILE statements:

Statement	Optional clause
USER	OF SYSTEM/SUBSYSTEM ACCESS TO SUBSCHEMA/SIGNON QFILE ACCESS TO QFILE ACCESS TO SYSTEM/SUBSYSTEM ACCESS TO FILE SIGNON PROFILE WITHIN USER
SYSTEM	WITHIN SYSTEM/SUBSYSTEM
FILE	RELATED FILE
PROGRAM	PROGRAM CALLED

If any entities being transferred contain one or more of these clauses, modify the definition of those entities to include the unresolved relationships once the transfer is complete.