Well, we run tivoli to monitor a bunch of "stuff".

     Also I have a small G30 RS6000 box to pull misc information from all
     our adsm servers (12 of them) and I coded the scripts where everything
     executes such as:
     for SERV in $(cat adsm.servers)
        do
        some_script $SERV
        done
     this way all I have to do to report/monitor on a new adsm server is
     add its name to the adsm.servers list PLUS add a subdirectory by the
     same name 'cause all files are written in /somepath/$SERV/file_name
     Any info that has to come from the specific adsm server itself I use
     system variables in all the script and have a generic id that I just
     plop out on the new adsm server... the info is generated there and one
     of the automated tasks back on the G30 is to do automatic FTP's to all
     the adsm servers and pull in specific info (back to a centralized
     location). Things like break out a months worth of dsmaccnt.log and
     port it over into a file name like : adsm_server.acctlog.MthYY
     Another thing I do is (basically)
        dsmadmc -id=xxx -pass=yyy q act begind=-1 s=ANR????E | mail -s
     daily_errors mymailid
     Now I do this with my loop through the servers method and collect all
     E,S,&D messages prefixed with the server name into a single file prior
     to mailing, but every day I have, waiting for me in the morning, a
     list of all problem messages from all servers for the last 30 hours
     waiting on me in the morning (good reading material while I drink my
     coffee)

     Now I have a server that I can rsh to and issue a text page to myself
     so anything I might need to monitor (or just watch for) that tivoli
     won't (which ain't much) I've automated, so pretty much so it doesn't
     matter if I'm at work, home, or other... if my pager isn't going off I
     know the adsm environments are OK ;-)

     Personally I think the ADSM server environments can vary enough (based
     on client load and use) that dealing with specific needs as they arise
     works pretty good... but code routines flexible enough to deal with
     all your environments, rather than code something real specific.

     later,
           Dwight


______________________________ Reply Separator _________________________________
Subject: Scripts or products to improve ADSM reporting
Author:  jdschn (jdschn AT IBM DOT NET) at unix,mime
Date:    4/15/99 11:41 AM


Greetings,
    Can anyone recommend or share scripts or products to improve ADSM
reporting?
It seems like every ADSM implementation I do I have to write a bunch of
scripts to
generate reports about the health of the server, and these reports all
contain information
that is all buried in the activity log, but is frustratingly difficult
to get at.
     Has anyone looked at Sterling Software's SAMS Vantage for ADSM?  It
looks like
it has some nice reports, but I have only looked at the glossy's and not
really tried it out.
     Last year I heard about a product called 'ADSM Manager'.  At that
time it looked
brand new.  Is it still around?  Is it any good?
     Any other products that would save me trouble?  Another thing I
have had to write
scripts to do is issue frequently used commands, so operators don't have
to remember
the syntaxes, or click down through seven layers of the Admin Gui to get
to the command
they want.  Are there any clever ways to improve this?

John Schneider

***********************************************************************
* John D. Schneider       Email: jdschn AT ibm DOT net * Phone: 314-349-4556
* Lowery Systems, Inc.
* 1329 Horan                  Disclaimer: Opinions expressed here are
* Fenton, MO 63026                   mine and mine alone.
***********************************************************************