This is just one of the reasons I really like this group. It gives me the chance to hear about how other shops are doing things that are different than my approach to similar issues. I'm so used to dealing with a homogeneous shop (1 kind of DASD) that I wasn't even thinking about using older, slower DASD for ML2. Although putting my ML2 on a tapeless Virtual Tape System is effectively doing that also. We're just choosing to eliminate the ML1 as I have lots of ways & places I can use all that DASD space.
Our recall times from the VTS are more than adequate for our purposes as we've got fairly good standards (or at least standards that work for us) for how long datasets remain on primary. And if we find there are some applications that are having an issue with the small delays recalling from ML2, I'll adjust their management classes to give them a more suitable time on primary. This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
