The order in which rulesets are loaded has no effect, because nvcorrd build
a huge internal array out of them, so the order in which rulesets are
listed in ESE.automation makes no difference. You can have as many as you
like in there. Having many small rulesets is much better than one large
one, since they are easier to debug and to manage. And nvcorrd doesn't
care whether there is one or several. I have seen customer files with as
many as 30 rulesets in ESE.automation but that is not typical.
Just remember that rulesets in ESE.automation are run by nvcorrd on behalf
of actionsvr. They do not affect the user's display, so you cannot use
things like "Forwrad" or "Resolve" in rulesets run out of ESE.automation,
nor will Override of status work, since that requires an events window for
Tivoli (NetView for UNIX) L3 Support
Eric ORTHEAU <eortheau AT synopse DOT fr> on 09/14/98 09:47:37 AM
Please respond to Eric ORTHEAU <eortheau AT synopse DOT fr>
To: NV-L AT UCSBVM.UCSB DOT EDU
cc: (bcc: James Shanks)
Subject: Use of ESE.automation
I can't find any information about the use of the file ESE.automation :
I'd like to know :
* if I put many rulesets in ESE.automation, what is the order of evaluation
* Can I have several rulesets or one "monster" ruleset ?
* If I can have several rulesets, how many are supported ?
Any help or tips will be welcome.