osdir.com
mailing list archive

Subject: RE: [TEC] Refreshing the Rules cache - msg#00303

List: sysutils.tivoli.tme10

Date: Prev Next Index Thread: Prev Next Index

In an older version of TEC I remember seeing the duplicate detect predicates
finding the current evaluated event but I think that was only during redo
analysis. Can you recreate the problem and post a trace?

I think a periodic cache refresh would be problematic in that during the
refresh process as you read for the database, create the BAROC file, delete
the existing cache, then repopulate the cache; you will not be able to
process any events. Also consider the complexity of dealing with timers set
on events, you would have to save those off and reload them as well. All
this can be done but IMHO it is not worth it..



-----Original Message-----
From: Moran, Joseph [mailto:joseph.moran@xxxxxxxxxxxxx]
Sent: Friday, March 11, 2005 10:56 AM
To: tme10@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] [TEC] Refreshing the Rules cache


Thanks for the detailed explanation of these predicates. Apart from a
reference to them in a rule example in a redbook I could not find any info
on them.

We are experiencing some problems with tec at the moment. In our
investigation we noticed the following behaviour:

1) I closed all current Events a specific class, lets call it joeclass, in
the TEC.
2) A new joeclass Event came in
3) Our dup detect rule ran and even though there were no open events in the
repository, the first_duplicate predicate matched an existing event, even
though there is a "status: outside [ 'CLOSED' ]" clause on the rule.
4) I bounced the TEC and replayed the event. The event was successfully
entered into the repository.

I was just wondering if a scheduled refresh of the cache, without restarting
the tec server as described above, is something that is used, and might
solve this problem.

Cheers

Joe




-----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx
[mailto:owner-tme10@xxxxxxxxxxxxxxxx]On Behalf Of Blankenship, I.V.
(Contractor)
Sent: 11 March 2005 13:51
To: 'tme10@xxxxxxxxxxxxxxxx'
Subject: RE: [tme10] [TEC] Refreshing the Rules cache


The save_event_cache predicate dumps the event cache to a flat BAROC file.
This file is formatted similarly to a BAROC class definition file but does
have some differences.

CLASS_NAME ;
SLOT_NAME =
SLOT_VALUE;
.
.
.
END

.
.
.

The restore_event_cache predicate calls bo_parse_baroc_file/2 to read the
file and add the instances to the event cache. Both save and restore
predicates call get_config_param to read the your
$BINDIR/TME/TEC/.tec_config file for the event_cache_file parameter and will
only work if that parameter is defined. To dump your cache to an arbitrary
file you can use print_cache(FILENAME). To read from any BAROC file do
something like this:

bo_get_config_options(_old_quote,_old_parse_in,_old_parse_out),
bo_set_config_options(_old_quote,0,_old_parse_out),
bo_parse_baroc_file(FILENAME,add_to_cache),
bo_set_config_options(_old_quote,_old_parse_in,_old_parse_out),


If you wanted to "reload" the event cache I suppose you could write a
program or perl script to read from the event repository to build a BAROC
file, iterate through all instances of events in your cache and remove them
with bo_delete_instance/1 and then call bo_parse_baroc_file/2 to reload the
events.

The real question is not "can you" (there is almost always a way...) but
"why would you need to?" Are you experiencing problem where you events in
cache are out of sync with your repository as a result of forced cache
cleaning? If so you would be better off implementing better duplicate detect
rules, drop and or close irrelevant events, and increase your event cache
size.

-----Original Message-----
From: john willis [mailto:john_willis@xxxxxxxxxxxx]
Sent: Friday, March 11, 2005 6:38 AM
To: tme10@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] [TEC] Refreshing the Rules cache


The undocumented predicates I saw in a flisting output were
save_event_cache and restore_event_cache. My guess is they are used in
the non-tme TEC. Other than that I think you are going to have to
wait till I.V. checks in.

John Willis
Gulf Breeze Software
www.gulfsoft.com
OpenESM Project
www.sourceforge.net/projects/gulfsoft


-----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]
On Behalf Of Moran, Joseph
Sent: Friday, March 11, 2005 6:27 AM
To: tme10@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] [TEC] Refreshing the Rules cache

John,

Thanks for the explanation of the rules cache update process.

I don't suppose you, or anyone on the list, know any of these
undocumented predicates, that you mentioned so I can search for them,
and take a look?

Regards,

Joe

-----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx
[mailto:owner-tme10@xxxxxxxxxxxxxxxx]On Behalf Of john willis
Sent: 11 March 2005 10:55
To: tme10@xxxxxxxxxxxxxxxx
Subject: RE: [tme10] [TEC] Refreshing the Rules cache


>Has anyone got a method to refresh the rules cache without restarting
the >tec?

I don't believe there is a documented way to do this. There are some
undocumented predicates but I am not brave enough try them.

>Also when an event slot is modified (closed on the console for example)
>what is the process that is triggered in order to update that event in
the >Cache, from the event in the event repository?

It kinds of works the other way around. First the requested change is
queued for the TEC_Rule process. TEC_Rule then processes the change
against the change_rules. If the change is not dropped the rules cache
copy is updated and a request is sent to the TEC_Dispatch to request an
update of the event in the event repository.

John Willis
Gulf Breeze Software
www.gulfsoft.com
OpenESM Project
www.sourceforge.net/projects/gulfsoft


-----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]
On Behalf Of Moran, Joseph
Sent: Friday, March 11, 2005 5:29 AM
To: tme10@xxxxxxxxxxxxxxxx
Subject: [tme10] [TEC] Refreshing the Rules cache

Hello list,

Has anyone got a method to refresh the rules cache without restarting
the tec?

Also when an event slot is modified (closed on the console for example)
what is the process that is triggered in order to update that event in
the Cache, from the event in the event repository?

Thanks in advance,

Joseph Moran








Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Re: TME Job Posting Inquiry

Hey Brian, I remembered it being Tivolisource.com. I can't get to it from work but try that site. Regards, Gregory R. Mendes ESM Technologies, Inc. "Brian Backer" <brian.backer@Cen turyTel.com> To Sent by: <tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx> owner-tme10@lists cc .us.ibm.com Subject [tme10] TME Job Posting Inquiry 03/11/2005 01:41 PM Please respond to tme10-XtjxT7Vmt5b2/ifjfJUUEg@xxxxxxxxxxxxxxxx m.com Hey all, Wasn't there a place that you could go to post Tivoli related Jobs? Anyone have that information? I can't find it. Thanks Brian ***************************************************************************************************************************************************************************************** This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential and privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You *****************************************************************************************************************************************************************************************

Next Message by Date: click to view message preview

RE: TME Job Posting Inquiry

www.tek-tips.com is a great forum. Also, they recently began hosting techical job postings. -----Original Message----- From: Brian Backer [mailto:brian.backer@xxxxxxxxxxxxxx] Sent: Friday, March 11, 2005 1:42 PM To: tme10@xxxxxxxxxxxxxxxx Subject: [tme10] TME Job Posting Inquiry Hey all, Wasn't there a place that you could go to post Tivoli related Jobs? Anyone have that information? I can't find it. Thanks Brian

Previous Message by Thread: click to view message preview

RE: [TEC] Refreshing the Rules cache

Thanks for the detailed explanation of these predicates. Apart from a reference to them in a rule example in a redbook I could not find any info on them. We are experiencing some problems with tec at the moment. In our investigation we noticed the following behaviour: 1) I closed all current Events a specific class, lets call it joeclass, in the TEC. 2) A new joeclass Event came in 3) Our dup detect rule ran and even though there were no open events in the repository, the first_duplicate predicate matched an existing event, even though there is a "status: outside [ 'CLOSED' ]" clause on the rule. 4) I bounced the TEC and replayed the event. The event was successfully entered into the repository. I was just wondering if a scheduled refresh of the cache, without restarting the tec server as described above, is something that is used, and might solve this problem. Cheers Joe -----Original Message----- From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]On Behalf Of Blankenship, I.V. (Contractor) Sent: 11 March 2005 13:51 To: 'tme10@xxxxxxxxxxxxxxxx' Subject: RE: [tme10] [TEC] Refreshing the Rules cache The save_event_cache predicate dumps the event cache to a flat BAROC file. This file is formatted similarly to a BAROC class definition file but does have some differences. CLASS_NAME ; SLOT_NAME = SLOT_VALUE; . . . END . . . The restore_event_cache predicate calls bo_parse_baroc_file/2 to read the file and add the instances to the event cache. Both save and restore predicates call get_config_param to read the your $BINDIR/TME/TEC/.tec_config file for the event_cache_file parameter and will only work if that parameter is defined. To dump your cache to an arbitrary file you can use print_cache(FILENAME). To read from any BAROC file do something like this: bo_get_config_options(_old_quote,_old_parse_in,_old_parse_out), bo_set_config_options(_old_quote,0,_old_parse_out), bo_parse_baroc_file(FILENAME,add_to_cache), bo_set_config_options(_old_quote,_old_parse_in,_old_parse_out), If you wanted to "reload" the event cache I suppose you could write a program or perl script to read from the event repository to build a BAROC file, iterate through all instances of events in your cache and remove them with bo_delete_instance/1 and then call bo_parse_baroc_file/2 to reload the events. The real question is not "can you" (there is almost always a way...) but "why would you need to?" Are you experiencing problem where you events in cache are out of sync with your repository as a result of forced cache cleaning? If so you would be better off implementing better duplicate detect rules, drop and or close irrelevant events, and increase your event cache size. -----Original Message----- From: john willis [mailto:john_willis@xxxxxxxxxxxx] Sent: Friday, March 11, 2005 6:38 AM To: tme10@xxxxxxxxxxxxxxxx Subject: RE: [tme10] [TEC] Refreshing the Rules cache The undocumented predicates I saw in a flisting output were save_event_cache and restore_event_cache. My guess is they are used in the non-tme TEC. Other than that I think you are going to have to wait till I.V. checks in. John Willis Gulf Breeze Software www.gulfsoft.com OpenESM Project www.sourceforge.net/projects/gulfsoft -----Original Message----- From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx] On Behalf Of Moran, Joseph Sent: Friday, March 11, 2005 6:27 AM To: tme10@xxxxxxxxxxxxxxxx Subject: RE: [tme10] [TEC] Refreshing the Rules cache John, Thanks for the explanation of the rules cache update process. I don't suppose you, or anyone on the list, know any of these undocumented predicates, that you mentioned so I can search for them, and take a look? Regards, Joe -----Original Message----- From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]On Behalf Of john willis Sent: 11 March 2005 10:55 To: tme10@xxxxxxxxxxxxxxxx Subject: RE: [tme10] [TEC] Refreshing the Rules cache >Has anyone got a method to refresh the rules cache without restarting the >tec? I don't believe there is a documented way to do this. There are some undocumented predicates but I am not brave enough try them. >Also when an event slot is modified (closed on the console for example) >what is the process that is triggered in order to update that event in the >Cache, from the event in the event repository? It kinds of works the other way around. First the requested change is queued for the TEC_Rule process. TEC_Rule then processes the change against the change_rules. If the change is not dropped the rules cache copy is updated and a request is sent to the TEC_Dispatch to request an update of the event in the event repository. John Willis Gulf Breeze Software www.gulfsoft.com OpenESM Project www.sourceforge.net/projects/gulfsoft -----Original Message----- From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx] On Behalf Of Moran, Joseph Sent: Friday, March 11, 2005 5:29 AM To: tme10@xxxxxxxxxxxxxxxx Subject: [tme10] [TEC] Refreshing the Rules cache Hello list, Has anyone got a method to refresh the rules cache without restarting the tec? Also when an event slot is modified (closed on the console for example) what is the process that is triggered in order to update that event in the Cache, from the event in the event repository? Thanks in advance, Joseph Moran

Next Message by Thread: click to view message preview

Re: [TDW] v1.3 will be GA by end of March & shipping in e arly April.

That's the word I've received from TDW developers. No release notes yet or anything, but one of biggest changes will be DB2 8 support. As for future of TDW, who knows, I've heard the Candle warehouse product is likely to supercede TDW. Rob Traill ----------------------------------------- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by