Dave,

     which version of *SM are you using, my experience is that the ANR8302
     is certainly something to watch out for but is mostly accompanied by a
     higher level event stating the fact that a volume was set te read-only
     due to write errors. We're catching these errors using the event
     mechanisms in *SM (tivoli, userexit).
     If I would chose a method to catch certain *SM events I would
     certainly follow the route I've followed till now but add for example
     an event interpreter to further process a critical event. This is
     something you could do with a monitoring tool such as HP-Openview or
     Tivoli-T/EC.
     At the moment I'm watching *SM events sent to me by mail using a
     userexit (the userexit writes filtered events to disk which are then
     processed by a mail agent), but the same mechanisme could be used to
     do some intelligent processing on the *SM server itself.
     The flexability of using the *SM event mechanism is that event
     filtering can be done within *SM leaving you with some event fine
     tuning but with the end result that only those events critical for you
     can/will be let thru (missed backup's, db/log problems, drive
     failures, tape errors, etc etc etc.)


     my two cents worth,

     regards Walter Ridderhof.


______________________________ Reply Separator _________________________________
Subject: running dsmserv as a ksh co-routine
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at INET-1
Date:    4/5/00 3:47 PM


Hi, *Smers

We have been bitten (HARD) by a tape drive going bad - it gave a write
error, but adsm carried on using it for many, many tapes.  A significant
percentage of these were then rendered unreadable.  We have recovered them
all, but it was a major job.

I have been considering running dsmserv as a ksh co-routine so that I can
trap a message such as ANR8302E containing the string OP=WRITE, and issue a
command to vary the affected drive offline until we can investigate.

Is anybody running dsmserv in this way?  Any problems or disadvantages?  It
<seems> ok on our test rig so far.

Tia

dave


----------------------------------------------------------------------------
The information contained in this email is confidential
The information contained in this email is confidential
and intended only for the use of the individual or
entity named above. If the reader of this message is not
the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this
communication is strictly prohibited. Guardian will
accept no responsibility or liability in respect to this
email other than to the addressee.

If you have received this communication in error, please
notify us immediately by telephone at 44 (0) 1932835900
or by email.


PLEASE NOTE:
The information contained in this electronic mail message is
privileged and confidential, and is intended only for use of the
addressee. If you are not the intended recipient, you are hereby
notified that any disclosure, reproduction, distribution or other
use of this communication is strictly prohibited.
If you have received this communication in error, please notify
the sender by reply transmission and delete the message without
copying or disclosing it.