In order for DCM to receive an object of a specific type, a definition for that type must exist in the destination database. By default, DCM includes all user-defined type definitions in transfer packages. During a receive operation, DCM automatically creates, in the destination database, any user-defined type definitions that are not already defined in that database.
Some methodologies require a local administrator to define all type definitions. In such cases, automatic type definition replication can be suppressed by excluding type definitions from the transfer set. If a type definition in the transfer package is not defined in the destination database, the receive operation is abandoned, and an error message is displayed.
By default, after a DCM receive operation successfully completes, the type definitions contained in the transfer package are removed from the file system of the receiving database. However, it is sometimes desirable to keep the type definitions. For instance, if type definitions are kept, the ccm typedef
-import -force command can be used to maintain all user-defined type definitions in a central database.
The DCM setting Keep Type Definition after Receive controls whether the type definition data is kept after a successful DCM receive. The default value is FALSE, which means that the data is removed from the file system of the receiving database. A value of TRUE means that the data is kept under the types receive directory, which is described as follows:
The transfer package is extracted under the receive_directory\package_ident path. package_ident is made up of the database, transfer set number, and time value (for example, M#22#UM#962984701). The types directory is located under the package_ident directory, as is the data directory for the exported object.