Re: Test Development System Survey -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Paul,

ASPs and IASPs have the same rules for disk, *almost. A traditional user ASP can overflow into the system ASP when it runs out of disk. This condition can be messy to clean up but does mean that you don't really have to worry about filling one (i.e. crashing the system or job when it happens) however you DO have to worry if you think that no job using ASP 2-32 is going to impact system storage. IASPs run on dedicated disks as do traditional ASPS but they do NOT overfloow onto the system ASP when full. This is good and bad, just as it was bad and good for traditional ASPs. You pay your money and you make your choice!

- Larry

PaulMmn wrote:

I am familiar with the 'traditional' ASPs; we used to have our system split into 2 sections so we could RAID the bulk of our disks, yet Mirror the system portion.

It was always fun remembering to use the proper ASP number.

Do the new IASPS require you to make a fixed allocation of disk space? If so, the library list finagling would seem to be a more usable solution-- your test and live environments can fight over the available space without the (I assume) need to re-allocate space to the IASP. Yes? No?/

--paul E Musselman

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.