[Top] [All Lists]

Re: Ruleset - refreshing

To: nv-l@lists.tivoli.com
Subject: Re: Ruleset - refreshing
From: James_Shanks@tivoli.com
Date: Wed, 2 Aug 2000 09:28:06 -0400

What goes on in the dynamic display is completely separate from what actionsvr
is doing.  He is a user just as you are.  When he starts, he "asks" nvcorrd to
load the rulesets in ESE.automation for him and send him the results, just as
you effectively do when you create the dynamic workspace.  That's why it is so
important not to use a Forward node in a "background" ruleset run by actionsvr
out of ESE.automation -- he has no display and cannot process the forwarded
events, so they just fill up his socket and cause a performance problem.

As for what happened with your ruleset in the dynamic case, I don't know for
certain.  I do the same thing all the time as a part of testing code and I
haven't had an occasion where I changed a ruleset and didn't get the new copy
when I started a new dynamic workspace.   Are you certain that the ruleset was
properly saved before you reloaded?  That's all I can think of.
Sorry.   If it happens again, please call Support and perhaps we can figure out
some tracing that will be helpful.

You can tell what a ruleset looks like after you open the workspace by issuing
"nvcdebug -n".  This causes nvcorrd to write a sort of  text copy of all the
rulesets he has loaded  to the nvcorrd.alog/blog.  That way at least you can see
what he thinks he is running, whether or not it is what you intended.

James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT

"Gavin Newman" <NEWMANGJ@stgeorge.com.au> on 08/02/2000 01:13:04 AM

Please respond to IBM NetView Discussion <nv-l@tkg.com>

To:   nv-l@tkg.com
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  [NV-L] Ruleset - refreshing

I created a rule and tested it by creating a dynamic workspace event display.
I then closed the dynamic display, changed the rule and then restarted a dynamic
event display but the old version of the ruleset was used not the newly modified

I then used ovstop & ovstart to cycle the actionsvr daemon in case it was
caching the rule but this had no effect.

How do I force the new version of the rule to be used?

Cheers - Gavin

   *****   IMPORTANT INFORMATION    *****
This document should be read only by those persons to whom
it is addressed and its content is not intended for use by
any other persons. If you have received this message in
error, please notify us immediately. Please also destroy and
delete the message from your computer. Any unauthorised form
of reproduction of this message is strictly prohibited.
St.George is not liable for the proper and complete transmission
of the information contained in this communication, nor for any
delay in its receipt.
NV-L List information and Archives: http://www.tkg.com/nv-l

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

Archive operated by Skills 1st Ltd

See also: The NetView Web