The messages indictae that the database or recovery log data sets have not
been formatted or their format has been over written.  Please run the PARM
='/FORMAT ....  step before running the restore.

-----------------------------------------------------------------------------------------------------------
Mike Kaczmarski
Mike Kaczmarski
Product Architecture
Tivoli Systems: Storage Software
(520)799-2318
mkaczmar AT tivoli DOT com



"Glass, Peter" <Peter.K.Glass AT WELLSFARGO DOT COM>@VM.MARIST.EDU> on 
06/08/2001
10:34:47 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Database Recovery Fails


We're attempting a point-in-time recovery of our ADSM Database.
ADSM Release is at Version 3 Release 1 Level 2.50, running on platform
OS390
Level 2.10.
The recovery is through batch JCL:

//SERVER EXEC PGM=DSMSERV,DYNAMNBR=300,TIME=NOLIMIT,
//   PARM='/RESTORE DB TOD=05/01/2001 TOT=17:00:00'

However, when we run the recovery batch job, ADSM appears to ignore the
RESTORE DB. Instead, it goes right into the following:
ANR5140I HTTP (IBM) communications is listening for clients on port xxxx
ANR5090I TCP/IP driver ready for connection with clients on port xxxx
ANR0259E Unable to read complete restart/checkpoint information from any
database or recovery log volume.
...and then the batch job terminates.
We have used this identical recovery job in the past without any problem.
The last time we ran this successfully, it was under OS390 2.8. Now we're
under OS390 2.10.

Any ideas?

Peter Glass
Distributed Storage Management (DSM)
Wells Fargo Services Company
> * 612-667-0086  * 866-249-8568
> * peter.k.glass AT wellsfargo DOT com
>