Promotion Support Facilities › NDVRDCOR Correlation

NDVRDCOR Correlation

The Correlation processor reads the entity list file produced by NDVRDSEL (NDVRENO) as ddname NDVRENI for entity names and control information. The CCDB and IDD on the target system is examined for modifications made to the entities in the list after they were last migrated into the target system dictionary from the source system dictionary.

Any modifications made to the entities on the list are reported as potential candidates for problems since corresponding changes may not have been made in the source system. The user is also warned when updates are made without a user or CCID, or when multiple user or CCID updates have been made to an entity on the target since last migration from the source dictionary. A warning is issued to an entity that has been migrated in (CLE Action = V) from a dictionary other than the source dictionary since its last migration from the source dictionary.

Note: If entities are routinely renamed when they are migrated to QA or Production, or if their version number is set to a value other than the source system, make sure to change those values in the ENT statements contained in the NDVRENI file before running the Correlation Processor (NDVRDCOR).

NDVRDCOR can be instructed to ignore a warning for an entity if its Status has been set to a particular value. Using this mechanism, it is possible to suppress warnings in those cases where the user has prior knowledge as to its state on the sending system. For example, this technique can be used to mark entities for which all updates made to the Production or QA system were also made on the source system.

Note: Since NDVRDCOR is a read-only process, no special security is required to execute it.

The Correlation Processor can be run in conjunction with NDVRDSEL executed in TRIAL mode by unauthorized application developers to qualify entities for migration before involving the DA or DBA. This process can be run to identify potential regression problems arising from multiple update or from updates occurring independently in the QA or Production dictionaries that did not originate in the source system (i.e., emergency fixes, QA fixes). Development teams can be given the capability to suppress unnecessary warnings through the use of installation standard Status codes.