You have two choices.  You can run it in the foreground as you are doing 
now, and see in your event window what it's doing, or you can run it in 
the background, but then you can't see what it's doing except by looking 
in the nvaction.alog/blog.

To run it in the background, you have to modify the ruleset first, and 
remove the Forward which puts the events on the display.  The reason fro 
this is that the ruleset will be run in the background by actionsvr, and 
he doesn't have a display.  So if you leave the Forward node in, the 
events that would go to the display will go to his socket instead and 
overwhelm him, eventually hanging him, and then nvcorrd, until trapd 
disconnects him.   Once you've modified your ruleset, edit 
/usr/OV/conf/ESE.automation and add the name of it there.  The full path 
is needed if it is not in /usr/OV/conf/rulesets.

Once your ruleset is listed in ESE.automation, stop and restart actionsvr 
and it will register your ruleset in the background.=, which you can 
confirm in the nvaction.alog.  Note that if you also run your unmodified 
copy of the ruleset in an Event window at the same time then you'll get 
duplicate events going to TEC.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group