After NDVRDLVR has been run and all entities have been punched from the Source Dictionary, NDVRBOOK will be used to migrate the entities into the Target Dictionary. When this type of processing is being performed, NDVRBOOK is being executed in migration mode and must be run under Batch/CV.
When running DDDL compilers or other utilities that invoke compilers to perform the migration on the target system, NDVRBOOK is run in a special migrate mode.
Note: In order to run NDVRBOOK in Migration Mode, the user must be associated with a Security Class with MIGRATE=Y and DE-CCID (Derived CCID) = N. Derived CCID processing is not valid for migration processing.
When running in migrate mode, NDVRBOOK will read the NDVRENI file for control information before invoking the necessary compiler or utility to be executed. The SOURCE SYSTEM/DICTIONARY and VERIFY DATE/TIME will be extracted from the NDVRENI file and passed to the Change Monitor.
When processing the NDVRENI file for a migration at the target system, NDVRBOOK updates each entity record in the target CCDB applicable to the compiler named in the PROGRAM IS program-name statement with the migration-id. If the VERIFY ALL clause is specified on the OPTION IS MIGRATE statement, each entity record in the target CCDB is updated with the migration-id regardless of the compiler named in the PROGRAM IS program-id statement. NDVRBOOK performs the migration-id updated for the first applicable entity on the NDVRENI file last and checks for this entity's being updated with the migration ID first, ensuring that duplicate and incomplete updates are avoided.
When the compilers ADD or MODIFY any entity while under migrate mode, a special Change Log Entry will be produced which contains an action code of V (Migrate-in), the SOURCE SYSTEM/DICTIONARY, and the VERIFY DATE/TIME extracted from the NDVRENI file. This record serves as an audit trail or "footprint" to register the entity's source origin and selection time, as well as the time it was received. CLEs are created when the Change Monitor detects an update by the executing compiler or migrator. When an update is performed by an executing compiler in migrator mode, the Change Monitor compares the migration-id for the entity in the CCDB (which had been previously updated by NDVRBOOK) with the migration-id for this session. If they are equal, a V type CLE is created. If they are not equal, no CLE is created. Migrate-in CLEs can be reported on in summary fashion by NDVRPT17, the TARGET MIGRATION REPORT (See Chapter 12 of the CA Endevor/DB for CA IDMS User Guide).
The Migrate-in CLEs created by the Change Monitor running in migrate mode are an essential part of the Correlation and Verification integrity checking process. They also provide an essential audit trail that assists in the resolution of production problems.
|
Copyright © 2013 CA.
All rights reserved.
|
|