IBM DS8000 manual Combine physical and logical data migration

//SYSPRINT	DD DUMMY
//SYSUT1	DD DSN=WB.MIGRATE.CNTL(DSS#SG1),DISP=SHR
//SYSUT2	DD SYSOUT=(A,INTRDR)
//SYSIN	DD DUMMY
//* -------------------------	JOB END ----------------------------	***
//

You might keep the job repeatedly executing through the second step AGAIN, where the same job is read into the system again through the internal MVS reader.

Eventually there remain a few data sets on the source volumes which are always open. These data sets require you to stop the concerned application, close and unallocate these data sets, and then run the job in Figure 14-14once more.

Verify at the end of this logical data set migration that all data has been removed from the source disk server with the IEHLIST utility’s LISTVTOC command.

Again this approach requires you to have the old and new equipment connected at the same time and most likely over an extended period, except if you push the migration jobs through like in Example 14-14 on page 313, in which you can run more than one instance concurrently.

14.3.5 Summary of logical data migration based on software utilities

Problems encountered when not using an allocation manager like system-managed storage are less flexibility when using esoteric unit names, or complex and time-consuming tasks in maintaining hard-coded JCL volume names, which need to be changed when creating new volumes on new disk storage servers. It is recommended that you use system-managed volumes to overcome the limitations with esoteric unit names and hard-coded volume names in JCL.

Logical data migration is difficult and can be time-consuming, and it usually requires system down time. System-managed storage allows for a less difficult data migration, when it is on a logical level, in order to consolidate not just disk storage servers, but also volumes moving to larger target volumes.

14.4 Combine physical and logical data migration

The following approach combines physical and logical data migration:

￿Physical full volume copy to larger capacity volume when both volumes have the same device geometry (same track size and same number of tracks per cylinder).

￿Use COPYVOLID to keep the original volume label and to not confuse catalog management. You can still locate the data on the target volume through standard catalog search.

￿Adjust the VTOC of the target volume to make the larger volume size visible to the system with the ICKDSF REFORMAT command, to refresh REFVTOC, or expand the VTOC EXTVTOC, which requires you to delete and rebuild the VTOC index using EXTINDEX in the REFORMAT command.

￿Then perform the logical data set copy operation to the larger volumes. This allows you to use either DFSMSdss logical copy operations, as outlined before, or the system-managed data approach.

314DS8000 Series: Concepts and Architecture