How do we convert old tape media to a new tape media?
search cancel

How do we convert old tape media to a new tape media?

book

Article ID: 42610

calendar_today

Updated On:

Products

ASM2- STORAGE MANAGEMENT ASM2 Backup and Restore

Issue/Introduction

Question:

How do we convert tape media within ASM2? For example; we want to keep our long term archive tapes that are currently on 3420 media but want to move them to 3480 or 3590 media.

Solution:

This will assist you in your process to convert the tape media and also reduce the number (in most cases) of files stored that are no longer required to be maintained within the ASM2 IPC. 

 

                                     Convert Tape media Cookbook

 A few changes to be aware of when converting to a new tape media and still using the old media.

The utility to accomplish this task is the Forward Merge Utility. This is documented in the System Reference Guide for ASM2: section 14:6

1)      Gather a tape list from the $MAINT output that lists all the tape volsers in the IPC. It will also list the media type.

2)      In the Forward Merge proc CAIPROC(ASM2FMRG) alter the following JCL to reflect the correct tape esoteric to be used for input and output.

 

//ASM2FMRG PROC CTLVOL=ASMVOL,                              

//         CTLDEV=ASMUNIT,                                  

//         WHAT=ARCH,IDX='CAI.ASM2.NONVSAM',                

//         POOL=$TAPPOOL,RIDX='CAI.ASM2.R42',                                    

//         INUNIT=TAPE,OUTUNIT=TAPE                                                                   -à tape device esoteric                

//******************************************************    

//*         CA-ASM2 RELEASE 4.2 FORWARD MERGE           *   

//******************************************************    

//ASM2FMRG EXEC PGM=$FM,REGION=4096K                        

//ASMPRINT DD  SYSOUT=(*)                                   

//SYSPRINT DD  SYSOUT=(*)                                   

//SYSUDUMP DD  SYSOUT=(*)                                   

//ABNLDUMP DD  DUMMY                                        

//INTAPE   DD  UNIT=(&INUNIT,,DEFER),DISP=OLD,VOL=SER=ASM2XX       à   tape device esoterics

//OUTAPE   DD  UNIT=(&OUTUNIT,,DEFER),DISP=(NEW,KEEP),                       à   tape device esoterics

//             VOL=SER=XXXXXX,                              

//             DSN=&IDX..&WHAT..DUMMY                       

 

3)      Make sure to change all the CAIPROC procs to reflect the new esoteric for the unload processing.

4)      Update $OPTIONS $TPUNIT fields and reassemble $OPTIONS.

 

$TPUNIT   EQU   *                                       USER MODAB

$TP3420   DC    CL8'RTAP    '     UNIT NAME FOR 3420 ALLOCATIONS 

$TP3480   DC    CL8'CART    '     UNIT NAME FOR 3480 ALLOCATIONS 

$TPM860   DC    CL8'M860    '     UNIT NAME FOR M860 ALLOCATIONS 

$TP348X   DC    CL8'3480    '     UNIT NAME FOR 3480 XF DRIVES   

$TP349E   DC    CL8'3490    '     UNIT NAME FOR 3490 E ALLOCATIONS

$TP359E   DC    CL8'3590-1  '     UNIT NAME FOR VTAP ALLOCATIONS 

          DC    CL8'        '     UNIT NAME TABLE EXPANSION      

 

Keep the old esoteric in the fields for reloads during the forward merge process. Also, no duplication of an esoteric is allowed.

 

**NOTE** for the first run after the conversion, add the parm $NEWTAPE to all the unload jobs so the new device types will be used and new tapes created. Once this process is completed normally then you can remove the $NEWTAPE parm and continue as before.  

 

Environment

Release: ASM2..00200-4.2-ASM2-Backup and Restore
Component: