Re: Too Much DASD

In a message dated 97-05-17 23:13:41 EDT, you write:

<< We ran a Reclaim spool storage command and set the  default days to two
 from the original eight.  We were astounded at the dasd we got back.  The
 machine went from 86% to 78.8%   -  a huge change.  Now though I am
 concerned that maybe we went one bridge too far.  We haven't noticed any
 bad things happening but this turned into such a major change that  I am
 suspicious.  Any comments or experiences to share? >>

   The advantage of reducing the number from 8 to 2 is it gets rid of excess
spool members (don't think of this as spool files, but the members where the
spool files were held).  This saves DASD.  Unfortunately, like everything
else this is a balancing act.  The next time a spool file is created by one
of your jobs, it must go out and acquire one of these spool members to write
the data into.  If there are no spool members available, the system must
create one.  As you know, there is a lot of overhead in creating a member.
 So the disadvantage to setting the number of days too low, is that it will
effect performance, as the system must create a spool member before it can
assign one to a job, there are no "empty" spool members available.

   If you didn't see a performance slowdown, you might still have some empty
members, and you hit the right number. 

HTH

Pete Massiello
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *