That's true, I should have qualified my statement to say I've had no reason
to do that on AIX or Windows TSM servers.

The tape management is different for OS/390, and many people use different
device classes for just the reason you noted.


-----Original Message-----
From: Matthew Lynch [mailto:Matthew.Lynch AT TEALE.CA DOT GOV]
Sent: Wednesday, June 25, 2003 1:57 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Device Class


We have different device classes simply to assign a different dataset name
prefix to the offsite volumes.  We then use the DSN prefix as our selection
criteria for ejecting the volumes from the STK silos .

Matthew Lynch
Teale Data Center
Storage Administration
E-mail: Matthew.Lynch AT teale.ca DOT gov
Phone: (916) 464-4204



                      "Prather, Wanda"
                      <Wanda.Prather@JH        To:
ADSM-L AT VM.MARIST DOT EDU
                      UAPL.EDU>                cc:
                      Sent by: "ADSM:          Subject:  Re: Device Class
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      06/25/2003 10:39
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






I've never seen any reason to have different device classes for primary &
copy pools, assuming they are physically the same device type.


-----Original Message-----
From: Zosimo Noriega [mailto:znoriega AT ADNOC DOT COM]
Sent: Wednesday, June 25, 2003 4:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Device Class


Hi to All,

What is the importance of using a different Device Class for onsite &
offsite storage pools?  Here in our site, we used single device class for
primary & copy pools.  Any feedback is really appreciated.  Thanks.

Zosi Noriega
Analyst, Data Storage
P.O. Box 898
ADNOC AUH UAE
009712 6024987