Dig out the old references to Tape Mount Management in SMS. I'm redirecting 3480 type tape to SMS disk and let HSM sweap the disk to 3590. You will have problems if you allowed non-cataloged tape datasets.....
> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Bobby Brake > Sent: Monday, August 15, 2005 12:09 PM > To: [email protected] > Subject: 3590 Strategies without virtual tape? > > We've just installed a STK L700e using 3590 tapes. These > tapes hold up to > 300GB and this system works great for our weekly backups > where we backup > our entire DASD farm. What I would like to ask the group is > what are some > strategies for batch processing without virtual tape? We use > TLMS as our > tape mmanagement system. When batch jobs run that write to > tape, a lot of > capacity is wasted because once a batch job is closed the tape is no > longer a scratch tape. Of course we use > VOL=(,RETAIN,,,REF=*... but that > still doesn't solve the problem. The STACKING function of > TLMS partially > solves the problem, but causes other problems concerning > contention when a > tape dataset needs to be read and the volume in the STACK > pool is still > open for output. What are others on this group doing besides > using virtul > tape systems? > > ---------------------------------------------------------------------- > 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
