Re[2]: ADSM/MVS Server Recovery
1998-10-28 00:04:09
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
|
|
|