You could delete the diskpool files from ADSM before shutting down, and
define them again after starting up after the backup.  The ADSM delete
doesn't do an mvs dataset delete so you don't need to define and format the
files every time.  If you don't use caching it shouldn't take long.  At the
hotsite, you can't get much smaller than 0!

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.
_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: ADSM in a DR situation
02-17-1998 11:44 AM

I have an interesting question for ADSM in the DR arena.   I am running
ADSM  R2.1 L17 on MVS.
I take ADSM down daily long enough to get all the system files backed up
for restore at a hot site.
Restore works great and ADSM works great to get the PC/Servers recovered
from the BFS files.
My question is _ Is there a way to bring ADSM up at the hot site with a
smaller  primary STORAGE pool?
I already clean the primary STORAGE pool down to 0% via migration to BFS
files prior to the system backup.
I spend a lot of extra time backing up and restoring the very large primary
storage pool VSAM datasets that are empty.
Any ideas or experiences?
Paul Brown
PDBrown AT Ashland DOT com