logo       

Ref:[tec39] root baroc and custom slots.: msg#00487

sysutils.tivoli.tme10

Subject: Ref:[tec39] root baroc and custom slots.

I got following explanation from Tivoli support for custom slots .

TEC 3.9 you will have to put a default value in for any extended slot that
you have defined in your barocs or it will not be seen in the event after
it parses.
This "feature" was not in place at 3.7.1.

- -----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx
[mailto:owner-tme10@xxxxxxxxxxxxxxxx]On Behalf Of vpatel@xxxxxxxxx
Sent: Friday, February 18, 2005 10:54 AM
To: tme10@xxxxxxxxxxxxxxxx
Subject: [tme10] Ref. [tec39} root.baroc and custom slots.


Hi, List.
I upgraded tec37 to tec39 on our development tec. There are some custom
slots in root.baroc file. I am using my old rule base. The root baroc is
from tec37.
tpm_ticket: STRING;
chb_key: STRING;
chubb_slot: STRING;
pager: STRING;
dup_suppress: STRING, default = 'yes';
managed_object: STRING;
probe_arg: STRING, default="N/A";



I send "wpostemsg -m TEST EVENT EVENT". Only two slots chb_key. Only two
slots "chb_key" and "dup_supress" are inherited from root.baroc, but other
slots did not?

I created a new rule base"tec39_rb1". Added my custom slots in root baroc
and send same event. I also tried with Su_Failure event and I got the same
result as my old rule. Chb_key slot One of the rule assigns value to
Chb_key slot.
Chb_key and dup_supress appeared in attribute list.

Is it possible if other slot does not have value then it will not appear in
attribute list? With tec37 all events inherits all slots from root.baroc.
Is some thing changed in TEC39?

Vina Patel
IT Infrastructure,
Tivoli Support
Chubb & Sons, Inc.
Phone: 908-903-5794
vpatel@xxxxxxxxx




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise