Here one scenario at the tasks needed to recover the database.
Database recovery
Conditions:
 ADSM database is lost/non-readable.
 Volume history file and device configuration file exist. (VOLHIST.BK1
and DEVCONFG.BK1)
 Mirroring is inactive
                Database backups are run daily as FULLs.


Tasks:

Halt the ADSM server.

1. Acquire the last database backup tape volume.

2. Does the volume history file exist? - VOLHIST.BK1

If Yes, proceed to Step 3.
If No, proceed to Step 2a.

2a. Create volume history file from contents of DRM plan or from a remote copy
of the file.

3. Does the device configuration file exist? - DEVCONFIG.BK1

If Yes, proceed, to Step 4.
If No, proceed to Step 3a.

3a. Create device configuration file from contents of DRM plan or from a remote
copy of the file.

4. Restore database
Do the database and recovery log volumes exists?
If No, proceed to step 4b.
If Yes, proceed to step 4c.

4b. Use DSMSERV DSMFMT to format new db and recovery log volumes
 DSMSERV DSMFMT )M  -DB xxxxxx.xxx   size
 DSMSERV DSMFMT )M )LOG xxxxx.xxx  size
The orignial allocation settings are in DSMSERV.DSK. The file is updated
anytime DSMFMT is executed.
4c. Restore the database from the latest backup.
 DSMSERV RESTORE DB )VOLUMENAMES-=Adxxxx DEVCL=3570C COMMIT=NO

5. Start the ADSM server
/USR/LPP/ADSMSERV/BIN/DSMSERV QUIET &

6. Audit the storage volumes against the database.
AUDIT VOLUME FIX=YES

 One question.. Does database restore imply that I need to reformat/build the
recovery log also or is it left unchanged?