Robert, No, I don't think I'm confused. The OP wrote that 2 drives were allocated for 1 Backuptask. While I've done what you're suggesting to speed up batch jobs, I'm not sure how or why you would specify Unit=(TAPE,2) for a HSM subtask. Could you elaborate?
I take it you are awash with spare tape drives. Dave O'Brien NIH Contractor ________________________________________ From: IBM Mainframe Discussion List [[email protected]] On Behalf Of Robert A. Rosenberg [[email protected]] Sent: Thursday, April 16, 2009 11:35 PM To: [email protected] Subject: Re: DFHSM MAXBACKUPTASKS(1) using 2 drives At 15:49 -0400 on 04/16/2009, O'Brien, David W. (NIH/CIT) [C] wrote about Re: DFHSM MAXBACKUPTASKS(1) using 2 drives: >Er Jay, We're talking about tape drives here. > >1 Backup Task should have 1 DASD unit as input and 1 Tape unit as output. > >The OP specified Duplexing was turned off. > >Dave O'Brien >NIH Contractor I think there is some confusion. MAXBACKUPTASKS(1) means start 1 task. DUPLEX BACKUP(N) means create only 1 Backup Dataset (ie: One DD). DUPLEX BACKUP(Y) would mean to allocate 2 DDs (and thus 2 backup datasets) and write each record to both DDs. The two tape drives allocated is probably due to UNIT=(TAPE,2) being used for the allocate (ie: Allocate 2 drives and switch to the 2nd drive/tape at EOV on the first tape to save time when you rewind/unmount it and need a second tape mounted to continue to backup file create [the 2nd tape is already mounted/ready]). ---------------------------------------------------------------------- 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
