|
Oliver-- As Someone mentioned, there's -no separation- just having their libraries in ASP/2 while yours are in ASP/1! It's just a physicallay separate block of DASD. Slip up on your library list, and you're using 'their' data. How are you going to separate their QGPL and QUSRSYS from yours? The last time we had a separate ASP we were protecting the OS, back before you could mix mirroring and RAID in a single ASP. As that famous Someone also mentioned, the only -true- separation would come from using LPAR and defining a totally separate system. --Paul E Musselman PaulMmn@ix.netcom.nospam.com >Al, > >>2). Just give them their own library names in the system ASP, and your >>company get's the benefit of more disk arms. With the system moving from >>proprietary DASD to PC commodity DASD, DASD densities will grow through the >>roof, and I predict that the next bottleneck for many ships will be DASD >>arm contention. > >yeah, that's my attitude. But I guess my $PHB will want some seperation - as >this data has nothing to do >with our system. > >Regards, > >Oliver
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.