Planning
Specific program products or functions must be taken into consideration when you plan or run a TDMF session. Subsequent user actions are also documented here.
- Storage requirements
This table lists storage requirements for the basic ECSA, CSA, and Extended Private for TDMF. - DASD space requirements
Refer to the following topic for all DASD space requirements. - Activating new hardware I/O configurations
TDMF prevents operating system corruption of UCB LookUp Tables (ULUT) from swap migrations. This capability is available when the MVS ACTIVATE command is submitted to dynamically change the hardware I/O of the LPAR. - CA products
Use the following for information on Computer Associates Products, which includes migrating volumes, event management and automation, job management, resource sharing and moving multi-image manager control data sets. - Cache fast write and sort programs
Ensure that cache fast write (CFW) is off for source volumes that are involved in swap migration, if possible. - Class names and esoteric names
TDMF is not aware of DFSMS class names or system esoteric names that are defined within an operating system. - Coexistence with other TDMF products
The following use case scenarios apply to all versions of zDMF. - Cross memory services
When TDMF is first run on an MVS system, a system linkage index (LX) is retained for the use of subsequent TDMF sessions. - Device states: Before and after a swap migration
The states of a device are related back to the subsystem it is connected to. The states in question are caching (CFW) and DASD fast write (DFW). A device cannot have CFW or DFW active at the volume level while not active at the subsystem level. - Data facility products
Use the following information when you work with control data sets or DFSMS. - Daylight saving time
An active TDMF session operates normally during a local time change (a switch to/from "summer time" or "Daylight Saving Time"). Time intervals are not calculated by using local time. The TOD clock is used for all time stamps. The local time option can be specified for the session. Also, the local time option can be set as default when the security key is generated. For both options, the local time offset that is used throughout the session is the one in effect at session initialization. - DFSort
You can use JCL to temporarily turn off CFW. Use either the DFSPARM or SYSIN DD statement to do so. These statements are only valid on 3990 controllers. - Duplexing functions
TDMF stops migration if volumes are detected that are involved in a primary/secondary duplexing function (such as Dual Copy). Such volumes can be found by standard architectural techniques. Duplexing functions that are started midway through a migration are included. The operation ensures secondary copies are not jeopardized in a Disaster Recovery situation. - EMC DASD
Using EMC DASD might require the installation of EMC Application Interfaces, obtained from EMC. - Enhanced catalog sharing (ECS)
When using TDMF to perform a migration of a volume containing a catalog managed by ECS, it is possible that the quiesce is not immediately processed. - Extended functions
If data striping and VSAM data compression is supported on the source subsystem, it is the user’s responsibility to ensure that these extended functions are supported on the target subsystem as well. - File allocation managers
The TDMF COMMDS must be allocated in contiguous cylinders. If a product that actively manages file allocation (for example, ProSMS or SAMS: Vantage) is installed, be aware that the possibility that the message GTD1080S might be created causing the migration session to end. This message states that the COMMDS space is not contiguous. The COMMDS needs to be reallocated outside of the control of the file allocation manager. - Global resource serialization
Information to ensure that the reserves that TDMF issues are not converted to global enqueues by GRS. - Host software component
Note the following for installations using StorageTek’s Host Software Component (HSC) for Library Storage Module (LSM). - HCD and Input/Output definition files
The specified values of the hardware configuration definition (HCD) files must be updated for migrating volumes containing Input/Output Definition Facility (IODF) files before the next initial program load (IPL). - HFS and zFS files
TDMF supports the migration of volumes that contain Hierarchical File System (HFS) files or zSeries File System (zFS) files. - ICKDSF
Do not run ICKDSF against any volumes involved in an active session. TDMF will dynamically detect the CCW operation codes from this program and terminate that volume’s migration. If an ICKDSF function is necessary, terminate the migration for that specific volume via the TDMF TSO Monitor, and then restart the volume migration using the TDMF TSO Monitor or the Batch Monitor. - IPL volumes
It is best to migrate active IPL volumes during a low activity period. Test this function in your test environment before you run a migration in a production environment. It is your responsibility to ensure that one or more new device addresses are communicated to the appropriate areas before the next IPL. Failure to do so can result in an invalid IPL. - Invalid count fields
The Count-Key-Data (CKD) and Extended-Count-Key-Data (ECKD) channel command sets write data out to a volume in a CKD format. - JES considerations
TDMF can migrate JES2/3 checkpoint and spool volumes. However, you must run the appropriate JES command to drain the spool to limit the amount of activity for that volume. - LISTDATA information
When using the LISTDATA command via IDCAMS to verify the status of the subsystem or volumes (for example, CFW on or off), there are some commands that query the physical controller and others that obtain the information from memory. - Migration of control data sets
TDMF can migrate a volume that contains Control Data Set (CDS) for any product. - Migration of stand-alone dump data sets
If the installation has generated the stand-alone dump program to use dump data sets on direct access devices, the program locates the data sets using device number rather than volume serial number. - Migration of RAID and non-RAID devices
TDMF will migrate volumes that are RAID or non-RAID devices. - Migration of unlike device types
It is now possible to move larger devices to smaller devices, in a Swap migration only. - Migration of volumes formatted for VM use
You can now use TDMF on MVS to copy and relabel VM volumes. - Model 204 considerations
Model 204 takes advantage of Cache Fast Write (CFW). - z/VM Agent considerations
In z/VM® environments, two associated types of volume labeling are applicable to virtual guest and multiple volume migrations. - MVS running under VM
TDMF provides the following list of detailed information when you run TDMF with VM and MVS environments. This information includes data set considerations, parallel access volumes, devices that were previously formatted for VM, and VM volume tolerance. - Operating parameters of TDMF
TDMF operates under a certain set of parameters. For example, the number of TDMF sessions, the number of groups per TDMF session, and the number of volumes per TDMF session. - Page and swap data sets
TDMF will migrate a source volume containing an active PLPA or common page data set, or both. - Parallel sysplex considerations
TDMF will migrate Sysplex Couple Data Sets (CDS). - Peer-to-peer remote copy support
IBM Peer-to-peer remote copy (PPRC) ensures that a user’s disaster recovery environment is not inadvertently destroyed or changed. TDMF is designed to be consistent with this type of data protection. - Real-time monitors
Various real-time monitors can sometimes cause migration-related error messages for which seeking a vendor-supplied fix is advisable. - Shared device definition
Ensure that the device is defined for sharing before adding a Communications Data Set (COMMDS) for multi-system sessions; otherwise, TDMF initialization fails as indicated by message GTD1386I. - Enterprise storage server support
TDMF supports the IBM® Enterprise Storage Server® (ESS) Storage Controller with the Parallel Access Volume (PAV) feature. - Define an I/O device as static, installation static, or dynamic
With MVS/ESA SP V4, the ability to define I/O devices as static, installation static, or dynamic was introduced through HCD. - Storage space requirements for virtual arrays
Certain storage space requirements should be considered for copying volumes to SVA (shared virtual array) and RVA (RAMAC virtual array) type arrays. - TDMF ownership of target volume
TDMF "owns" the target volume during the life of the migration session to preserve physical data integrity. Except for a few non-disruptive inquiries, any I/O operation to the target volume by anything other than TDMF is rejected. Also, a message is created with IOSB completion code X’4A’ (the I/O was prevented). The message might be IOS000I or some other MVS message that indicates an error by the application or MVS system component - TDMF and volume table of contents
Selecting the dynamic ICKDSF option causes TDMF to reformat the Volume Table of Contents (VTOC) by dynamically starting the ICKDSF REFVTOC or EXTVTOC function when the target volume device characteristics do not match that of the VTOC. - Soft Fence
DS8870 disk subsystems can provide a Soft Fence function. The purpose of this function is to prevent unintended access to a device in a logical subsystem (LSS). Most I/O operations (like reading and writing data) to a device are prevented by the disk subsystem if the Soft Fence state is set for the device (the device is soft fenced). - SPID Fence
DS8700, DS8800, and DS8870 storage systems provide a SPID Fence function to prevent an offline device from being brought online. - Suppressing warning messages in TDMF
The NOWARNing option allows users to suppress the effect of individual warning message on the completion code of the TDMF session. Using this option keyword causes the system to disregard the warning message(s) about the migration, and resets the completion code to zero. - XRC support
TDMF allows a volume that is the primary in an XRC session to be specified as a source or target volume for a Swap or Point-In-time migration. Restrictions on the use of an XRC active source volume in a Swap migration are listed below.