Hi Ralph,
That’s good to know. I downloaded
FP02 but haven’t done anything
with it yet, as I have been spending some
weeks installing premise
wiring for a new system (if you ever want
to wear your fingertips
down to bloody nubs, that’s a good
way to do it).
In case you are ever standing around the
water cooler with some of
those TEC developers and someone says “Hey,
I wonder what we
could do to make the TEC console more
user-friendly?”, I would
suggest giving the users a way to undo
accidental event closures.
However, if the TEC developer says “I
know, we could pop up a
message box asking if they really want to
close this event!” then
you should just dump your water on his
head and back away.
I wonder if it might be possible to build
in some sort of configurable
time limit, where you have x number of seconds
to change your mind
before the change takes effect. Maybe make
“CLOSING” an actual
status that automatically changes to “CLOSED”
if no one countermands
it within a certain time. Heck, why not
just redesign the whole thing?
I bet an Eclipse-based console would be
mighty purty... :)
Loren Cain
Digicon
From:
owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx [mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx] On Behalf Of Ralph Baldwin
Sent: Monday, November 29, 2004
11:26 AM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] TEC 3.9:
change from ACK to OPEN ?
Hi Loren,
At
3.9 FP02, this is in the README. It should also let you set a CLOSED
event to OPEN, using the -f flag.
Using the wsetemsg command to set the status
of an event to ACK multiple times is no longer permitted by default. You must
now use the -f flag to acknowledge an event
that already has a status of ACK.
You're right in that we don't want people to set events from CLOSED or ACK to
OPEN. In our "normal" scenario, correlation gets a wee bit
munged or worse, if you are not careful.
Cheers,
Ralph Baldwin
Internet email: baldwinr-r/Jw6+rmf7HQT0dZR+AlfA@xxxxxxxxxxxxxxxx
Advisory Software Engineer
IBM Software Group - Tivoli
Software
Performance & Availability
Office: 512-286-3665
|
"Loren Cain"
<loren.cain-dF2bnGa4wqY7tRa4sXbB6w@xxxxxxxxxxxxxxxx>
Sent
by: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
11/29/2004 06:54 AM
|
|
To
|
<tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
RE: [tme10] TEC 3.9: change from ACK to OPEN
?
|
|
I'm
not sure what the underlying rationale is, but from looking
at the definition of the set_event_status
predicate, you can see
that someone went to a lot of trouble to prevent
this from
happening:
set_event_status( _event , _new_status ) :-
bo_get_slotval( _event ,status, _old_status
),
( _old_status == ACK -> (
_new_status == OPEN -> fail ; true);
true ),
( _old_status == CLOSED -> (
_new_status == OPEN -> fail ;
_new_status
== ACK -> fail ; true);
true ),
bo_set_slotval( _event ,status, _new_status
),
re_mark_as_modified( _event , _ ),
! .
It would seem that you could just use
bo_set_slotval directly, but I
don't know what the consequences of doing that
that might be.
I used to get calls from Operations occasionally
asking why they
couldn't re-open events that they had accidently
closed. For example,
"Hey, I fixed a problem on 'host1234', but I
inadvertantly closed a
similar event for 'host5678', can you put it
back?"
I went as far as writing a change rule that would
have reopened an
event if the same operator that closed it closed
it a second time
(ie, 'undo' the close). Then it dawned on me that
the TEC console
grays out the 'close' and 'acknowledge' buttons if
the selected event
is already closed (that's what I get for rarely
using the console GUI).
Even wsetemsg would not accept the change for an
event that was already
closed. At that point I decided that the reward
was not worth the effort
required and moved on to something else.
It seems someone *really* does not want you to do
this...
Loren Cain
Digicon
-----Original Message-----
From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
[mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]
On Behalf Of Francois Le Hir
Sent: Wednesday, November 24, 2004 2:19 PM
To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
Subject: [tme10] TEC 3.9: change from ACK to OPEN
?
Hello,
Looking at the documentation for set_event_status
and
change_event_status,
I see that it doesn't allow changing the status of
an event from ACK to
OPEN. is there any good reason for that
limitation?
I was using 'ACK' for effect events and wanted to
change it to 'OPEN'
when
the cause is resolved but not the effect.
Thanks,
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 964 2145
