ADSM-L

Re: Storage pool DSNs

1998-12-15 10:13:48
Subject: Re: Storage pool DSNs
From: Andy Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 15 Dec 1998 07:13:48 -0800
Check out the PREFIX parameter of the DEFINE DEVCLASS
command.

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

My site is in the process of installing ADSM under MVS. We plan to have all
copy storage pool volumes written on a group of 3590 tape drives. We will
probably have volumes for at least some of the primary storage pools
written
on the same drives. As I understand matters, the datasets on storage pool
volumes written on the 3590 drives will all have the same DSN, regardless
of
which storage pool is involved and regardless of whether it is a primary
pool
or a copy pool.

My site uses the Vault Management System feature of CA-1 to control the
movement of tapes stored offsite. VMS can identify tape datasets that are
candidates for offsite vaulting by DSN, job name, or a combination of the
two.
I would assume that all tapes written by ADSM server functions will share
the
same job name.

Have I missed something, or has IBM neatly and systematically precluded
every
possible means of having VMS identify ADSM tapes that should be sent
offsite?
<Prev in Thread] Current Thread [Next in Thread>