IMPORTANT ! ! !
Now I got to where I extended the DB & LOG to exactly what they were
when my data base backup was taken. If I didn't extend them, that is
just do the define dbvol blah... then the dsmserv parm='/restore db
devclass=blah vol=vol1,vol2,... commit=yes' would blow up.
You might be able to just extend them all the way if you don't have
info on where they were at the time of the db backup but I have auto
jobs that run about every 4 hours on each of my adsm servers and
gather all information necessary for a potential adsm db recovery.
Oh, that is one of those make copies of all the files you still have
that might get blown away so you can ensure they exist when you run
the dsmserv restore db job ;-)
And if you don't have the diskpool volumes available it will whine and
not start either... that is one of those "I tried with 0 of 100
diskpool volumes and that didn't work so went to the other extreme"
Oh, and you can do the f adsm,blahblahblah... for all the define
dbvols and all the define logvols and all the extend log & extend db
and and and but I found it easier to just f adsm,register admin you
yourpswd and then f adsm,grant authority you class=system THEN fire up
a dsmadmc from my pc or anywhere I had dsmadmc available to do all
that other stuff. I think the operators get a little nervous when I'm
hanging around their consoles (and I don't blame them either!)
Hope this helps
later,
Dwight
______________________________ Reply Separator _________________________________
Subject: Re[2]: ADSM/MVS Server Recovery
Author: Frank.Rehor (Frank.Rehor AT clorox DOT com) at unix,mime
Date: 10/27/98 11:04 PM
Dwight,
I'm curious about your approach. After you fire up adsm and define the
additional DB's what do you do? Stop adsm and submit a batch dsmserv
restore? I ask because in the ADSM V3R1 MVS Admin Guide, page 387,it
says: "Attention: do not start the server until after you restore the
database. Starting the server before the restore would destroy any
existing volume history files."
Later,
Frank Rehor
The Clorox Services Company
______________________________ Reply Separator _________________________________
Subject: Re: ADSM/MVS Server Recovery
Author: decook AT amoco DOT com at Internet
Date: 10/27/98 4:09 PM
Along with the apar mentioned in the other note...
I would always just put in a single DB & LOG volume initially, then
fire up adsm with its nice new db and from the console define my admin
id, then initiate a dsmadmc session to define the other/additional db
vols & log vols.
I think my initial failing attempts had my parm field around 200
characters on 3 lines. Once I got the continuations correct it yelled
on the parm length, then I screamed!
later,
Dwight
______________________________ Reply Separator _________________________________
Subject: ADSM/MVS Server Recovery
Author: Frank.Rehor (Frank.Rehor AT clorox DOT com) at unix,mime
Date: 10/27/98 2:31 PM
Hi,
I'm attempting to recover my ADSM/MVS V3.1.1.3 server on a test LPAR.
I am using the procedures documented in the ADSM for MVS: Recovery and
Disaster Recovery Redbook. I have allocated and formatted my recovery
log (one file) and database (four files). When I try to initialize the
files with the batch DSMSERV FORMAT utility I get various errors. 1st
I discover that the 'PARM' field can only handle up to 100 characters
(this is NOT documented in the Administrator's Reference). With 5
files to initialize this is not enough. So I broke the job into 2
steps with the recovery log in step1 and the DB's in step2. The
recovery log init'd ok, but the DB step gave me the following error
msg: "Invalid database count for format mode." The JCL was coded:
// PARM='/FORMAT 4 SYS3.ADSMP.DB01 SYS3.ADSMP.DB02 SYS3.ADSMP.DB03
// SYS3.ADSMP.DB04'
Any help is most appreciated. Thanks.
Frank Rehor
The Clorox Service Company
925 847 4814
frank.rehor AT clorox DOT com
|
