ADSM-L

Re: Event Notification

1998-01-13 21:00:36
Subject: Re: Event Notification
From: Michael Kaczmarski <kacz AT US.IBM DOT COM>
Date: Tue, 13 Jan 1998 21:00:36 -0500
With the ADSM version 3 product you can drive server and client events into a
user exit.  This exit will get all messages/types for which it is configured
and you can write code to page the appropriate party.



Mike Kaczmarski
IBM Corporation
ADSM Development
kacz AT us.ibm DOT com



        ADSM-L AT VM.MARIST DOT EDU
        01/13/98 10:35 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet


To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
Subject: Re: Event Notification

We'd LOVE some form of paging from the ADSM server! We're currently looking at
what Tivoli can do for us in that area, but something directly from ADSM would
be fantastic.


The BIG thing on my personal wish list, though:
I'd like to write something for NT that opens an ADSM *console* and watches the
messages there, but also opens an administrative client and responds to
particular messages. For example... I'd like to chain 12 admin commands
together, but have no two of them running at the same time. "COMMIT" in a macro
just isn't cutting it. So this thing I want would send the first command in the
admin client session, then watch for the completion in the console session and
send the next command. (Does something like this already exist? I've seen talk
of scripts for AIX that do this, but the ones I have seen just do Q AC a lot and
check for completion.)

But paging from ADSM would do for now. ;)




<Prev in Thread] Current Thread [Next in Thread>