How To
Summary
A migration project can be a very challenging and time-consuming task. It can also cause grief in the
future if some files are corrupted. Because these problems could potentially be discovered months or
years after the migration, it could become a nightmare to correct them. Therefore, the migration must
be secured to get the assurance that all source files are correctly transferred and if not, we should at
least have a report listing of inconsistent files.
Developing a set of "one off" scripts and procedures for a one-time migration is time consuming when
there is already an existing set of scripts and procedures.
This document proposes a recipe to address this scenario.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
19 January 2022
UID
ibm16538618