How DCM computes and creates a transfer package

DCM creates a transfer package from the time the transfer package was last generated, the objects in the transfer set, and the destination database definition.

When a DCM generate is performed, DCM determines the collection of objects for the specified transfer set to be sent to the specified destination database. DCM uses a last generated time that defaults to the time that the last DCM generate was performed using that transfer set and destination database. DCM generate performs the following steps:

  1. If the transfer set is the predefined Entire Database transfer set, DCM automatically recomputes the implicit members. If the transfer set is a user-created transfer set, and the transfer set is marked to be recomputed, DCM automatically recomputes the indirect members.
  2. DCM recomputes the query-based members for the change request scope and release scope.
  3. DCM queries for all the existing members that were modified on or after the last generate time. DCM also queries for members that are new direct, indirect, query-based, or implicit members on or after the last generate time.
  4. DCM applies built-in DCM exclusion rules, and exclusions defined on the transfer set to remove ineligible objects from being included.
  5. DCM creates a DCM transfer package containing data that describes the objects to be included.
  6. DCM stores the generate time to be used as the default for the next DCM generate for the transfer set and destination database. By default, DCM saves the 30 most recent generate times for a transfer set and destination database. See How DCM stores generate times for more details.

These objects are excluded from the transfer list when DCM applies its built-in exclusion rules:

You can also exclude objects from the transfer list using one or more of these options in the transfer set Exclude dialog:


Feedback