Changing the tape library using Disk merge.

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

We will migrate from VTS 3494-Bxx to TS7700 as sample and we need to a have a proc about how the OLD tape should be copied to the new tapes?

Resolution

Please find the following proc about the merge to copy the old to a new robot:

You use the Disk Merge utility to perform the copy.

You would use the INCLUDE parameter to provide the merge job a list of up to 100 VOLSERs to process. PERCENT=0 would be coded to limit processing to only those VOLSERs provided in the list. The MAXVOLS parameter can be used to limit the total number of VOLSERs processed by the Merge job.

The INCLUDE parameter can also be coded with a pattern as opposed to a specific VOLSER. If the old VTS uses a VOLSER range of 100000-199999, you could code INCLUDE=100/ to process the 100000-100999 volumes, force only those volumes to be selected, and limit processing to 100 volumes by coding:

MERGE INCLUDE=(100/),PERCENT=0,MAXVOLS=100,...

The first step is to find the MERGE job you are currently running, copy it, and then modify the copy by adding the INCLUDE, changing the PERCENT, adding or adjusting the MAXVOLS, and adding SIMULATE. Go ahead and submit it to test the command syntax.

When it is time to do the migration, remove the SIMULATE and submit the job. If you have things set up correctly to route the Disk output tape selection for the old library to the new library, the VOLSERs in the 100000- 100999 range that Disk has used will be merged.

If there are more than 100 Disk tapes in the set of 1000 being processed you can adjust the MAXVOLS parm to a higher value to grab them all. The reason for the MAXVOLS is to limit the run time of the Merge job so that you do not submit a job that runs for days. You can run a few times to get a feel for how long it will take to process 100 VOLSERs and then adjust the parameter accordingly to run within any time or processing restrictions you have.

Or

Use another DYNnUNIT to be set to the unit name of their new TS7700, e.g. use DYN3 and set first:

ARESUNI3TS7700 - for auto-restore
DYN3UNITTS7700 - for all other functions

Maybe consider other data set names on the new device:

ARC0NAME...
ARCCNAME...
MERP1NAM...
MERC1NAM...

//STEP01 EXEC MERGE
//MERGE.SYSPARMS DD *
SYSPARMSS
MERP1TYPDYN3
MERP1NAM...
MERC1TYPDYN3
MERC1NAM...
DYN1UNITAUTO
DYN2UNITAUTO
DYN3UNITTS7700
//MERGE.SYSIN DD *
MERGE SIMULATE,TYPES=(DYN1,DYN2),PERCENT=0,INCLUDE=(vvv/)
/*

Merge-Parameter to be considered later: MAXVOLS= instead of INCLUDE=.