To build new target system (original)
  - make sure 7337 library is not in autoload mode
  - files to transplant: dsmserv.opt desmserv.devconv volume.history and dsmserv.dsk
  - on target system:
    1. install, set license stuff
    2. build volume group, then logical volume (> 4GB for db, >1GB for log) names need to match
       those on source system, i.e. db1 and log1 (/dev/rdb1 and /dev/rlog1)
    3. bring up dsmserv, def dbv and logv, extend, delete db.dsm and log.dsm (builds dsmserv.dsk)
  - dsmserv.opt file is copied from source
  - volume.history is copied from source
  - dsmserv.devconv needs to be copied, abbreviations, ensure rmt0/1 matches element #s
    (the lines that look like comments actually map the library contents - required)
  - restore the data base: dsmserv restore db tod=today preview=n
  - restore took < 15 min, when done, you may have to redefine rmt0/1 again, if elements dont match

>From note to Paul ...
Things that only need to be done the first time only:
 - define a volume group for the adsm data base and recovery log
 - create a logical volume "db1" at least 4 GB and a recovery log "log1" at least 1 GB
 - dsmserv.opt - cut and paste from the source system
 - dsmserv.devconv - cut and paste from the source system, with some editing
 - dsmserv.dsk - this is the tricky one. My practice has been to use raw logical volumes
   for all the adsm disk volumes: data base, recovery log and storage pool. To set this up,
   bring up the adsm/tsm server in the foreground. 
   - set up licensing: "reg license *.lic", "reg license 10client.lic"
   (not really part of this process, but a good time to do it)
   - def dbv /dev/rdb1
   - def logv /dev/log1
   - delete the install dbv and logv (del dbv /usr/tivoli/tsm/server/bin/db.dsm &
     del logv /usr/tivoli/tsm/server/bin/log.dsm)
   - extend the db and log to the max

Things to be done the first and subsequent times:
 - volume.history - cut and past from the source system. For transfer to Southbury,
   this file will be on a diskette accompanying the dlt cartridges
 - dsmserv.devconv as above, the lines that look like comments actually map the library
   contents - which is required to mount the db "backupfull" volume
 - load the dlt cartridges in the 7337 library. It is very important to have the correct
   cartridges in the correct "elements" - slots in the library
 - restore the adsm data base: dsmserv restore db tod=today 
   the appropriate dlt cartridge will be loaded, and the adsm/tsm data base will be restored
   takes about 10 minutes
 - define storage pool volumes, if you want (not necessary though)

The adsm/tsm system is now ready to restore the files that were backed up.
Expect about 425GB of data to be available