Attribute 2 is appropriate only for NetView traps.

The best way to understand what your ruleset is doing is to trace.  The
command nvcdebug will let you do that.  There's a man page for it.  But I
usually recommend that you just issue "nvcdebug -d all" while testing.
Then you can examine the nvcorrd.alog/blog and see what's going on.  You'll
see an eyecatcher "Received a trap" and "Finished with the trap".
Everything in between is nvcorrd running that trap through your ruleset and
any others that are active.  The smartset query has plenty y of trace
message to tell you what the issue is.
"nvcdebug -r" will reset tracing to nothing.

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