Overview

In a typical promotion, entities are copied from a source data dictionary to a target data dictionary. CA Endevor/DB Facilities perform the following functions:

Selection of entities to migrate based upon input selection criteria, IDD relationships, and Change Log information.
Integrity checking the source system prior to migration for complete development activity (for example, dialogs generated when a subordinate process or map is changed, records updated when subordinate elements are changed, maps generated when work records are modified, subschemas recompiled when schemas are changed, etc.). A complete description of integrity checks is contained later in this chapter.
Impact analysis prior to migration on the target dictionary by examining the IDD relationships and the CCDB history of changes on that system. During impact analysis, migrating entities and related entities in the target system are examined for update activity since they last migrated from the source system. Any update usually represents an inconsistency between the source and target systems.
Migration of changed entities from the source to the target system using the CA Endevor/DB native mode migrator.
Automatic Signout of migrating entities during impact analysis to prevent update until the migration process is completed.
Building a standard IDD Class/Attribute structure in the source dictionary as an interface to other vendors' migration facilities at an installation, if desired.
Audit trail creation on the source and target systems reflecting the origin and destination of migrated entities.

The Promotion Support architecture, in conjunction with the Dynamic Change Monitor and the CCDB, gives CA Endevor/DB the unique capability to assure accurate promotions while eliminating a majority of the time-consuming tasks normally associated with migration. CA Endevor/DB facilities can be used to perform all migration tasks or to interface with an existing migrator in use at an installation.

Important! CA Endevor/DB Promotion Support does not currently migrate CLASS/ATTRIBUTE or USER definitions. If you have entities with ATTRIBUTES or any of the ATTRIBUTE-related characteristics (USER-DEFINED-COMMENTS, USER-DEFINED-ENTITIES, simple ATTRIBUTES), then you must ensure that the CLASSES and ATTRIBUTES are defined at the target dictionary before running the target-dictionary portions of promotion. For instance, if a source-dictionary entity is defined with MYCLASS=MYATTRIBUTE, then that characteristic will be migrated. If MYCLASS and MYATTRIBUTE are not already defined at the target, then do so manually before running NDVRBOOK (OPTION=MIGRATE).