John, When you create a TAPECOPY the dataset created is HSM.COPY.HMIGTAPE.DATASET. Make sure your SMS routines allow this dataset to go to your ATL. That should take care of your issue with copying existing tapes via the TAPECOPY command.
Just curious - are you using duplexing to create your DR copy or just copying after the fact? If you have the resources I would recommend using duplexing and create the DR copy at the same time as your local copy. Thanks....Rick -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Mattson Sent: Monday, May 18, 2009 4:17 PM To: [email protected] Subject: HSM COPYTAPE ML2 Tape unit type confusion After many years I have finally convinced management (or more nearly accurately SOX and PCI have convinced them) that they might really need ML2 tapes at the DR site in a Disaster. Swell. So now I try implementing it. BUT COPYTAPE ML2 tries to copy my 359L ATL tapes to 3590-1 (non-ATL) volumes. 8700 string is my ATL, and 3400 is the 3590-1's IEF234E K 8702,M00205,PVT,DFHSM,DFHSM IEC501A M 8704,M00205,SL,COMP,DFHSM,DFHSM,HSM.HMIGTAPE.DATASET IEC501A M 8705,M00112,SL,COMP,DFHSM,DFHSM,HSM.HMIGTAPE.DATASET IEF244I DFHSM DFHSM - UNABLE TO ALLOCATE 1 UNIT(S) 436 AT LEAST 1 OFFLINE UNIT(S) NEEDED. IEF877E DFHSM NEEDS 1 UNIT(S) 437 FOR DFHSM SYS02358 FOR VOLUME PRIVAT- 1 OFFLINE 3400-340F IEF878I END OF IEF877E FOR DFHSM DFHSM SYS02358 18 IEF238D DFHSM - REPLY DEVICE NAME OR 'CANCEL'. R 18,CANCEL 19 ARC0381A ALLOCATION REQUEST FAILED FOR PRIVAT FOR TAPECOPY. REPLY WAIT OR CANCEL Now, I can get around this by using a special TAPECOPY command " TAPECOPY MIGRATIONLEVEL2 A3590UNITNAME(TAPEA) " where TAPEA is my ATL estoeric. But what worries me is that HSM uses 3590-1 as the default in this case. All of my parms in my PARMLIB(ARCCMD00) use the TAPEA estoeric. I have spent a couple of hours on the manual, and I have not been able to find a SETSYS, or other cmd, which will change the default. I notice that a LIST of my ML2 shows 3590-1 even though the tapes beginning with "M" are all in the ATL. ********************************* TOP OF DATA ************************************************************************ ** - DFSMSHSM CONTROL DATASET - MIGRATE VOLUME-MCDS--- LISTING ----- AT 11:59:56 ON 09/05/18 FOR SYSTEM=EAI1 VOLSER DEVICE MIGRATE VOL DATE VOL LAST VOL DELETED PSWD EXP RACF AVAILABLE IN USE SELECTED IDRC DUPLEX PCT TYPE TYPE FULL SP MANAGED EMPTY DS ALT FULL M00112 3590-1 L2-TP YES 00/00/00 NO 0000 NO YES NO YES -NO- NO Y *NONE* 96.7 M00205 3590-1 L2-TP NO 00/00/00 NO 0000 NO YES NO YES -NO- YES Y *NONE* 17.9 M00292 3590-1 L2-TP NO 00/00/00 NO 0000 NO YES NO YES -NO- YES Y *NONE* 76.8 So, now, I ask the experts. 1) Should I just use the A3590UNITNAME with tapecopy, or is there a way to make it the default? Is there any downside to this. 2) In particular, I do NOT want to load my ML2 tapes into the ATL at the DR site, and get them rejected because it wants a 3590-1 non-ATL instead. This will be the first time trying ML2 tapes in the DR scenario. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
