Better:

A port connection is a more reliable method of alerting and it is generally
real time.

Test this on a low impact Server first
1.      Enable events tivoli severe
2.      Enable events tivoli error
                3.      disable any events not wanted (this is hard to
determine)  cmd: disable event tivoli anr0001   (note: no letter on the end)
3.      Configure tivoli to point to a local port (loop back and whatever
port you want)
4.      Write a simple program to monitor this port, receive the alert,
change the format and send the error in the format the receiver wants (ITO,
Netcool, etc.)
5.      Bounce ADSM server to establish the connection.
6.      To test connection: enable event tivoli anr2017
7.      Run q actlog
8.      Watch event receiver for event.
Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.

WAL-MART CONFIDENTIAL


        -----Original Message-----
        From:   Prather, Wanda [SMTP:Wanda.Prather AT JHUAPL DOT EDU]
        Sent:   Tuesday, October 23, 2001 9:01 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: ITO alarms and TSM error messages

        I have no idea what ITO is, and my background is AIX rather than
Solaris....
        But, look at the ENABLE command in the ADMIN GUIDE and ADMIN
reference.

        You can issue the ENABLE command to cause TSM to forward error
messages real
        time to a "receiver"  such as a Netview/Openview monitoring server
via SNMP.

        But there are other kinds of "receivers" as well.  Instead of
forwarding the
        error messages to the SNMP daemon, you can write them to a flat
file, or
        send them to a user exit program that you create, where you could do
        anything you want with them.  I"ve never done the user exit myself,
but I've
        done used SNMP and the flat file method, and they work fine (at
least from
        an AIX TSM server).

        You can choose to have all messages forwarded by severity (ERROR,
SEVERE,
        WARNING, INFORMATIONAL), or just select the ones you care about by
number.

        Hope that helps..


************************************************************************
        Wanda Prather
        The Johns Hopkins Applied Physics Lab
        443-778-8769
        wanda_prather AT jhuapl DOT edu

        "Intelligence has much less practical application than you'd think"
-
        Scott Adams/Dilbert
        Scott Adams/Dilbert

************************************************************************







        -----Original Message-----
        From: Glass, Peter [mailto:Peter.K.Glass AT WELLSFARGO DOT COM]
        Sent: Monday, October 22, 2001 6:01 PM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: ITO alarms and TSM error messages


        We would like to setup an error message monitoring process that
sends alarms
        to the Helpdesk for a select group of error messages, as they occur,
in the
        Solaris TSM Server Activity Log. We normally use ITO for this kind
of thing.
        How can we get a non-TSM error message monitor to "listen in" on the
TSM
        Server for messages to report -- as they occur? Any ideas or advice
would be
        most welcome!
        Thanks, in advance.

        Peter Glass
        Distributed Storage Management (DSM)
        Wells Fargo Services Company
        > * 612-667-0086   * 866-407-5362
        > * peter.k.glass AT wellsfargo DOT com
        >


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**********************************************************************