Thomas Crutcher asks:

>We are having problems getting a backup of several ADSM VSAM files while ADSM
>is up.  We need these for disaster recovery purposes, and would prefer not to
>shut down the ADSM address space to take them.  We have tried changing the
>share options, but this did not help.  We need some way of getting them not to
>be allocated EXCLUSIVE by ADSM.  We can use FDR to get a backup, but would
>prefer to use our primary disaster recovery tool, Sterling's SAMS:DISK
>(DMS/OS).  The data sets are the storage pool data sets, recovery logs, and
>the DB2 data set.  Does anyone know of a way to do this?

This is a *very* dangerous method of backing up your ADSM server environment.
I do not recommend pursuing this avenue and further. Instead, I recommend that
you do the following:

1) If you are not already at ADSM/MVS V2 R1, then you should upgrade. Current
   maintenance level is V2 R1 L0.7.

2) Use the BACKUP DB command to back up your ADSM database.

3) Use the BACKUP STGPOOL command to back up your ADSM storage pools.

You can do these backups while the ADSM server is running. Please refer to the
Administrator's Reference for further details on these commands.

*In theory* you could use mainframe utilities like DFDSS, FDR, or whatever to
back up your ADSM database, recovery log, and disk storage pool data sets.
Notice that I said, "in theory". *One* requirement for such a backup scheme to
work reliably, if indeed it works reliably at all, is that the ADSM server has
to be shut down. You do not want "fuzzy" copies of these data sets because it
is very likely that, in the event of a disaster, you will not be able to get
your ADSM server up and running.

There are probably a number of ADSM customers who use mainframe tools to back
up their ADSM server environment. As long as they do it with the ADSM server
shut down, and as long as they periodically test their disaster recovery
procedures to verify that this process works, they'll probably be alright.
But I discourage this method of backup for ADSM (and I have a mainframe
background!  :-)   ).

Unless there is a very compelling reason to do otherwise, I *strongly* urge you
to use the ADSM backup tools that are provided to back up the database and
storage pools (as I described above). I also recommend that you read the ADSM
Administrator's Guide, Chapter 14, for more information on backup and recovery
of the ADSM server.

Hope this helps,

Andy Raibeck
ADSM Level 2 Support
408-256-0130