Julie,

     Thanks for the reply.  When you performed the restore, did you allocate new
db and rl volumes, rename the degraded ones, then execute the DSMSERV with the
RESTOREDB parameter?  Did you also perform an audit of the db?

                         Ginny





jphinney AT HUMANA DOT COM on 07/23/98 09:52:40 AM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Virginia L Hysock/HI/CSC)
Subject:  Re: RESTORE DB TO 2.1




The last database restore I did was a V2 restore, about 6GB, and it took
around an hour.



Virginia Hysock <Virginia_L_Hysock AT CSC DOT COM> on 07/23/98 06:59:03 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Julie Phinney/Green Bay/Humana)
Subject:  RESTORE DB TO 2.1




Can someone please provide some quick info to me on how much time a restore
and
audit of the database takes?  I have the rest of today and Friday to finish
testing of my conversion from MVS 2.1.13 server to 3.1.1.3.  I have had
some
problems during the test conversion, and I really need to provide a
fallback time
to my management.  I've seen some horror stories on this list regarding db
restores in the past, so I'm pretty nervous about the possibility.  I've
got a
17.5 GB database as of this date.
Also - has anyone had problems on upgrade of their server with TCP error
messages,
specifically ANR5099E Unable to init TCP/IP driver RC(48)?
Thanks for any help,
Ginny