Promotion Support Facilities › NDVRDCOR Correlation › NDVRDCOR Command Syntax

NDVRDCOR Command Syntax

The parameters to execute NDVRDCOR are contained in the front of the NDVRENI file as created automatically by NDVRDSEL. The following command syntax specified in the NDVRIPT file is used to supplement the automatic parameters:

►►────── SIGnon ──┬─────────────────────────────────┬────────────────────────►
                  ├─ DBNAme ──────┬── is dictname ──┘
                  └─ DICtName ────┘

 ►────┬─────────────────────────┬───┬──────────────────────────┬─────────────►
      └─ USEr name is user-id ──┘   └─ PASsword is password ───┘

 ►───────────┬────────────────────────────────────────┬──────────── . ───────►◄
             └─ CCId name is ───┬─────── ccid ────────┤
                                │                     │
                                │     ┌─── , ───┐     │ 
                                └─ ( ─▼─ ccid ──┴─ ) ─┘

►►─┬──────────────────────────────────────────────────────────────────┬──────►◄
   │           ┌────────────────────────────────────────────┐         │
   └─ IGNore ──▼─┬── where STAtus name is status ──────┬────┴──── . ──┘
                 └── WIThin CCId name is ccid ─────────┘

►►────────┬──────────────────────────────────────────────────────────┬───────►◄
          └─ EXPand IDD relationships ───────────────────────── . ───┘

SIGNON

Identifies the user responsible for the migration and optional password and CCID list. If no CCID list is specified, the default CCIDs for the user are assigned from the CCDB.

IGNORE

Multiple IGNORE statements can be specified. Ignored from warnings are those items, which have a particular Status. This mechanism is employed as a way of excluding individual entities, even though all other criteria would have resulted in warning.

Note: When the WITHIN clause is specified, the status under the context of the CCID name is examined. When no WITHIN clause is present, only the base status is considered. If the same base and CCID status values are to be ignored, two IGNORE statements are necessary. Multiple IGNORE statements are ORed.

EXPAND

NDVRDCOR performs its correlation processing in two passes:

• Pass 1 reads the input Entity List file and checks the target CCDB to see if any of those entities have been changed at the target since last migration.
• Pass 2 examines the IDD and checks entities related to those which will be migrating.

When the EXPAND option is not in effect (default setting), the input Entity List File is the sole source for entities to be checked. No Pass 2 is performed. In this case, no information will be provided about target changes to related entities and no information will be provided about "migration stopper" entities (See below).

When the EXPAND IDD RELATIONSHIPS clause is in effect, the Pass 2 expansion and checking will be performed. Target dictionary entities that are not migrating, but that are directly related to the migrating entities and that have changed since last migrated from the source (if ever), will be reported in the Expansion Entity Exceptions report. See the "Target System Impact Analysis Rules" section for a complete description of the correlation rules. Also, the Pass 2 processing will produce the Target Entity Exceptions report. This is a listing of all MAPs, SUBSCHEMAs and SCHEMAs that exist at the target dictionary, and include records coming in the migration but are not themselves coming in the migration. Because of the BUILDER CODE rules enforced by CA-IDD, these entities will prevent the import of the new record definitions. You must remove these "migration stopper" entities from the target dictionary before attempting to run the migration import job, or else add them to the set of entities being migrated.

Note: If the CA Endevor/DB migrator is being used, always specify the EXPAND clause.