nv-l
[Top] [All Lists]

Restrictions on rulesets in ESE.automation

To: nv-l@lists.tivoli.com
Subject: Restrictions on rulesets in ESE.automation
From: Scott McCambly <mccambly@NETCOM.CA>
Date: Thu, 5 Nov 1998 16:11:17 -0500
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Hello James and the rest of you NetViewiers,

First I wanted to thank James for that document he posted about rule
writing performance tips.  It has been very useful and I'm going to start
handing it out to people who take the NetView training course.  (Any more
tips docs like this one, James? :-))

I have two questions related to the practice of not using ruleset nodes
that involve a display.

1) Your note and the docs (Admin Guide & Diagnosis Guide) refer to not
using "PASS" or "FORWARD" nodes, but I'm under the impression that a better
rule of thumb is "any node that would affect the display", so that would
include "RESOLVE" and "OVERRIDE" (I'm assuming "BLOCK" is safe, but
pointless).  Can you please confirm this?

2) If this problem were occuring, would you be able to see the backlog of
messages to actionsvr using "netstat -a" (I'd test it but I currently only
have access to production systems)?

Thanks,
Scott McCambly
AIX/NetView/ADSM Specialist - Unopsys Inc.  Ottawa, Ontario, Canada
(613)799-9269

<Prev in Thread] Current Thread [Next in Thread>
  • Restrictions on rulesets in ESE.automation, Scott McCambly <=

Archive operated by Skills 1st Ltd

See also: The NetView Web