My replies below

>>1) Operations staff reports that sometimes the events window stops logging
>>events and they have to restart the NV GUI.  Events are still coming into
>>trapd.log at this time.  The freeze button is not on and no new correlation
>>rules were in place.  Just wondered if this has happened to anyone else and
>>where I might look to troubleshoot.

This will be difficult and probably require you to get help from Tivoli Support.
The events application has no tracing.  The first thing I would do is issue
"nvcdebug -d all" and start nvcorrd tracing.  Then look at the nvcorrd.alog and
see whether he is keeping up with the trapd.log or not.  If not, then you may
have too many rulesets running or the processing they are doing is taking too
long. If not, then
the problem may be in nvserverd.  Are you forwarding to TEC?

I have also seen this symptom after a trap storm or when you have DNS problems.
But the fact that it gets fixed after they restart the GUI puzzles me.  Are they
also
restarting the daemons?

>>2) I have a frequently recurring event that I want to suppress.  I went into
trap
>>customization and changed it to "Log Only", yet I still see it in the event
desk
>>- the event card even shows "LogOnly" - am I doing something wrong?  Please
note
>>that I don't have the r/w map, but I didn't think this was necessary (I was
root
>>at the time).

Check xnmtrap again and make sure you changed the Event Category box.  You can
only do so by clicking the pull-down button.  If that is correct, then grep for
the event name in trapd.conf :  cd /usr/OV/conf/C  and  grep <event_name>
trapd.conf
Does it say "Log Only Events" as the last thing?   It should.
If not, then you haven't really changed it.  If it does, then please call
Support.

>>3) How can event filters be saved permanently?  I noticed in the Admin Guide
>>that there are 2 fields in /usr/OV/app-defaults/Nvevents (saveEnvOnExt and
>>loadEnvOnInit) - do I need to change these both to True?  The manual goes on
to
>>say that if you want to save your workspace config, you must have
loadEnvOnInit
>>set to True, so what is the purpose of saveEnvOnExt?

They are independent.  You can set saveEnvOnExt :  True  and also loadEnvOnInit
to True, and then when you log in, you will always get the same environment you
had when you logged out.  Or you could leave saveEnvOnExt as False and then you
would bring
up events and start all the workspaces you want with whatever filters you want,
pull down the Options menu and click Save Environment.  Then that environment
will be saved when you
log out and it will be the one you always get when you log in again, no matter
what you
do while you are there.  In the later case, you could have a standard
environment which always opens three workspaces, and it wouldn't matter if you
decided to close one, as all
three would still start the next time.  In the case where saveEnvOnExt is True,
only what you had open when you left would be re-started.  Do you follow that?

The best way to do this is by user.  Copy /usr/OV/app-defaults/Nvevents to your
$HOME directory and chnage your local copy, so you can let others do what they
want.

If all you want to do, is automatically open the default window with
forwardall.rs running and some filters applied, you can skip the above and
create a .<userid>.events file in your
home directory.  This is just a list of filters you always want applied.  You
create it with an editor. For example, if you are user mary, and your $HOME
directory is /home/mary,
then in /home/mary your would create a file called ".mary.events" and in that
file you would put first the name of the filter file and second the name of the
filter.  If your filter were called "test1" then your file would say
/usr/OV/filters/filter.samples test1


James Shanks
Tivoli (NetView for UNIX and NT) L3 Support