Jeff,

Since the compression is implemented in hardware, ADSM thinks he wrote
30G on a 3590, even though a 3590 only actually holds 10G.  I typically
get 15 to 25G on a tape since my data is not very compressible.

I code 0 for max always. If you code a max, ADSM will stop when he
reaches max - probably not what you want.

If you code 30G for estimated, the est cap displayed on Q STG will be
based on 30G per tape (regardless of how much is actually on the tapes.)
The advantage here is that your storage pools will have nice consistant
numbers for capacity.

If you code 0 for estimated, the est cap displayed on Q STG will be
based on actual capacities of tapes that are in the pool (I'm not
exactly sure what the algorithm is).  The storage pools will vary in
capacity even if they have the same max volume limits.

Either way, if max=0, ADSM will write until he runs out of room on the
tape.

Ron Clendenny
Callaway Nuclear Plant
Fulton, Missouri
<rdclendenny AT cal.ue DOT com>

> -----Original Message-----
> From: Jeff Connor [SMTP:connorj AT NIMO DOT COM]
> Sent: Friday, October 31, 1997 6:53 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Device class capacity values for 3590 Magstar
>
>   We are adding Magstar drives to our MVS system for use with our ADSM
> v2.1.10 MVS server.  I'm not sure what values to use for estimated
> capacity
> and/or maximum capacity, 10GB? 30GB?, when defining the device class
> for
> the 3590s.  Can anyone using 3590s with ADSM let me know what values
> you
> selected?  Also are there any other 3590 related issues I should be
> aware
> of with ADSM for MVS or MVS in general?  We are installing the 3590s
> in a
> 4410 STK silo.  Thanks
>
> Jeff Connor
> Systems Programmer
> Niagara Mohawk Power Corp
> Syracuse, NY