Re: Test Development System Survey

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

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