ADSM-L

FW: ADSM Storage Management 101

1996-01-22 16:22:00
Subject: FW: ADSM Storage Management 101
From: "PITTSON, TIMOTHY" <PITTSON1 AT BWMAIL1.HCC DOT COM>
Date: Mon, 22 Jan 1996 16:22:00 EST
Jerry,
     Since you need to preformat these ADSM files before using them, I'd
allocate 2 separate datasets.  However, I think if you use SMS with a
storage class using  the guaranteed space attribute, you would be able to
allocate the dataset across multiple volumes - I think with guaranteed space
if you were to define a 1000 cylinder dataset on 2 volumes, you'll get 2
1000 cylinder datasets at allocation time as opposed to getting the space on
the second volume later on.  (the rules on this did change a couple of years
back - I think this is the way it works today)

Tim Pittson
pittson1 AT bwmail1.hcc DOT com
 ---------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Subject: ADSM Storage Management 101
Date: Monday, January 22, 1996 4:08PM

Date:     January 22, 1996            Time:    15:13
From:    Jerry Lawson
    ITT Hartford Insurance Group
    (203) 547-2960    jlawson AT itthartford DOT com
 -----------------------------------------------------------------------------
This question seems simple to me, but we can't seem to find the answer in a
manual......

We are trying to allocate (on an MVS Server) a DASD Pool that exceeds the
physical size of 1 volume.  Is there a way with the VSAM define to specify
that the data set will span volumes, or should we allocate 2 data sets (one
on
each volume).  If the later is the case, how do you pick up the second
volume
with the administrator when you assign the data sets to a storage pool?

*****************************************************************************
                        Jerry
<Prev in Thread] Current Thread [Next in Thread>