We defined the ESTCAP as 30G.  We don't use compression at the client,
     although the only cartridge that ADSM has called "full" so far is made
     up largely of UNIX-compressed data.  It just seems strange that it
     filled at 10G and not 11.8 or 13.


______________________________ Reply Separator _________________________________
Subject: Re: Conversion to Magstar
Author:  bcolwell (bcolwell AT DRAPER DOT COM)
Date:    3/5/98 5:11 PM


In <H00006c10ef74735@MHS>, on 03/05/98
   at 03:13 PM, Jim Kleberg <jrkleberg AT STATESTREET DOT COM> said:

>     I would be interested in anyone's experience in converting to Magstar
>     drives under the MVS ADSM server.  We are currently trying to convert
>     to Magstars defined in compat mode within an STK silo.

>     When we define the drives as devtype=cartridge, it works great but we
>     seem to only get 10G to a cartridge.  When we use devtype=3590, we
>     fail because ADSM doesn't see the UCB as a 3590.  This is a V3 server.

>     Any ideas?

>     Jim Kleberg
>     State Street

>     617-985-8392

We have been researching this here but haven't done it yet.

From what I have read you have probably done everything right.
10 gigs is the rated capacity of a 3590 if there is no gain from
compression at the control unit, which is certainly possible with ADSM if
the clients have already compressed the data.

The v3 admin ref says that the default for estimated capacity for a 3590
device is 9G, so you are in the ballpark.
--
-----------------------------------------------------------
-----------------------------------------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma
bcolwell AT draper DOT com
-----------------------------------------------------------
=========================================================================