Does  your action script also source the Tivoli environment  ( .
/etc/Tivoli/setup_env.sh) before calling wasync?
Remember that the actionsvr daemon shares none of your environment
variables.  So if this works from the command line for you but not for him,
that is almost certainly the problem and you will have to source all the
Tivoli stuff he needs first.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Denny Whelan <dwhelan AT INVACARE DOT COM> on 01/05/99 10:54:15 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  Re: Integrating Netview AIX with Tivoli Framework





We are still getting this error.

My host name is - us-spn1s
the results of uname -s are AIX
the results of uname -a are AIX us-spn1s with some other codes at the end.

Any ideas why we still get this error message


Below is the original E-Mail I sent out.

We are attempting to forward events from Netview to Tivoli Framework.  We
do not have TEC as part of our installation.  We have created a ruleset
that has an action node that calls wasync to pass the event to a async
monitor in Tivoli.  When this process kicks off we get a communication
error (destination dispatcher could not be found) in the actionsvr log.
Both the framework and netview are running on the same box.





"Ken Garst." <KGarst AT GIANTOFMARYLAND DOT COM> on 12/23/98 09:41:14 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.ucsb DOT edu>

To:   NV-L AT UCSBVM.ucsb DOT edu
cc:    (bcc: Denny Whelan/US/IVCR)
Subject:  Re: Integrating Netview AIX with Tivoli Framework




I get the same error message when the uname -S field does not match the
hostname of the machine.  The Tivoli framework checks this field while
Netview checks the hostname.