John,
When we ran ADSM on MVS, we mirrored our database and recovery logs. I
do remember the ADSM server writing a message to the activity log in
cases where a mirrored copy was taken offline or lost due to some other
issue.... don't remember the error message number but I did used to
check for it in my daily server management jobs (think it was an
ANRxxxxE message so I just did a Q ACTLOG searching for that mask).
Tim Pittson
tpittson AT himail.hcc DOT com
>----------
>From: John O'Neall[SMTP:jon AT IN2P3 DOT FR]
>Sent: Monday, January 06, 1997 8:48 AM
>To: Multiple recipients of list ADSM-L
>Subject: audit DB? (fwd)
>
>This is an old note about detecting when a mirror volume has a problem,
>the only reply to which was that one can stop the server and do an AUDIT
>DB, which may take days, obviously an unacceptable method. Otherwise,
>I've determined that, even at restart, the server sends NO message saying
>that a mirror volume is offline: One must do a 'q dbvol' or 'q logvol' to
>get the info.
>
>To my mind, this makes mirroring _practically_ useless, in the real
>meaning of the word. IBM claims it improves perforamance, but I've seen
>no evidence for this either.
>
>This is like a RAID disk which doesn't signal any error when a disk
>fails. Can you imagine such a thing? (Unfortunately, I can.)
>
>:-( John
>--------------------------------------------------------------
>John O'Neall e-mail: jon AT in2p3 DOT fr
>Centre de Calcul de l'IN2P3 phone: +33 (0)4 78 93 08 80
>Villeurbanne, France fax: +33 (0)4 78 94 30 54
>
>---------- Forwarded message ----------
>Date: Fri, 27 Dec 1996 14:36:39 +0100 (MET)
>From: John O'Neall <jon AT in2p3 DOT fr>
>To: ADSM List <ADSM-L AT vm.marist DOT edu>
>Subject: audit DB?
>
>Is there any command equivalent to "audit db", just to ask ADSM to go out
>and check on the DB and log volumes?
>
>In order to test a new version of ADSM (2.1.0.10) before putting it into
>production, I recently installed a small test server (default storage
>pools + one exabyte). I also mirrored the DB and log into /tmp. Then I
>erased the /tmp/DB entry and filled /tmp with junk data. That was 24
>hours ago and ADSM still hasn't noticed. Granted, this is a fake
>situation. Nothing is happening to fill up the log, which is what I
>suppose is necessary in order to force a write to the DB. Still, it might
>happen over holidays.
>
>Any reply would be helpful. TIA. John
>--------------------------------------------------------------
>John O'Neall e-mail: jon AT in2p3 DOT fr
>Centre de Calcul de l'IN2P3 phone: +33 (0)4 78 93 08 80
>Villeurbanne, France fax: +33 (0)4 78 94 30 54
>
|
