Planning and implementation
This section contains a migration methodology, and best
practice guideline to be used in conjunction with a data migration
project. Additionally, because zDMF is a data set level migration
tool that includes updating the information in the catalog and interacts
with SMS, there are sections that discuss their role in the migration
process.
Installation considerations and requirements
Before you begin the installation, you need to be aware of all requirements and considerations.
Planning the migration
Planning for migration prior to execution contributes to having a successful migration. Planning includes establishing a migration management team, and performing pre-migration tasks.
Data set considerations
Before using zDMF to perform data migrations, you should review this section for details that may affect your data sets .
DFSMS considerations
Reserve Handling requirements
zDMF has explicit requirements in the area of reserve handling in a shared storage environment. More specifically, zDMF requires that Hardware Reserves issued for the SYSVTOC and SYSZVVDS resources for all source and target volumes be converted to Global ENQs. Additionally, any Hardware Reserve issued by z/OS® address spaces, including system, application, and jobs, that reference migration data sets must be converted to Global ENQs.
TCP/IP considerations
zDMF uses a TCP/IP concurrent-server architecture to communicate critical time-dependent internal messages between zDMF servers, executing on separate z/OS systems. Up to 127 zDMF servers can share internal messages in this manner. These zDMF servers can reside on any number of Sysplexes or none at all.
Volume considerations
Migration considerations
Catalog management considerations
Separate catalog(s) and unique target data set high-level qualifiers should be established as part of the migration planning process. The use of dedicated catalogs and unique target high-level qualifiers will mitigate catalog growth impact of adding large numbers of target data set entries and will simplify the management of post-migration data extent deletion tasks.
Backup considerations
zDMF device swap processing
If HyperSwap® is available, device swaps will be transparent to zDMF processing. When a device swap occurs, it is automatically recognized by all zDMF Servers, and the device allocations are transparently adjusted for all migration groups. Message GZD3125I is issued for each device that is swapped. This message reports the volume serial, old device number, and new device number of the swapped device. This message is issued on all zDMF Servers that have migration groups using the swapped device.
zDMF audit trail
To help you conform to regulatory requirements and provide additional information related to migrations and command execution, zDMF provides two optional types of audit trail: