That was the problem.  The Admin manual talks about doing an install in the
middle of a DumpDB/RestoreDB operation, but not when doing a straight restore
of a DB from a backup tape.  The Redbook missed that step completely.  Also,
when you have the pubs folks on this issue, have them include an example with
multiple DB vols and recoverlogs - The answer is in the JCL reference, but a
good example of a continuation in the ADSM doc wouldn't hurt.  Also, since
there is a 100 character limit on parm information, what to do it you have
more than that amount of info to pass.  We eventually ran the install with
only one DB and recovery log, then started ADSM and added the rest of them,
then took ADSM down and ran the restore.  This worked, but we were unsure if
we were on the right track.  We thought that the disklog contained the names
of the DB and recovery logs, but there seems to also be a copy of that info in
the DB as a backup copy.  We were out of synch between the two until we did
the process the way I stated above.

Thanks for the info.

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: adsm db restore
11-21-96 01:39 PM

 Jerry...as Tim Mortimer mentioned...it looks like you missed the dsmserv
install step after formatting the db volumes and before you do
the dsmserv restore db command....this is not documented very clearly
in the pubs...I will pass this on to our pubs folks...it's probably
my fault...I should have caught that when I reviewed that section in
the admin guide...greg tevis