Ref: [TEC371] limit for string used in PROLOG list

Thank you I.V.Blankenship for your suggestion for fact file. It did not
occur to me.
I will try it.
Thanks again.
--------------------Response from I.V Blankenship

Date: Fri, 28 Jan 2005 10:17:13 -0500
From: "Blankenship, I.V. (Contractor)" <I.V.Blankenship.ctr@xxxxxxxx>
Subject: RE: [tme10] Ref: [TEC371] limit for string used in PROLOG list

if I recall correctly the limit to the size of a list is the amount of
memory you have available. Now the limit on a Prolog string atom is
something around 32k.

As for a better way of handling the logic as you add more strings to check
it will take longer to process each event.

You could use facts or the recorded database to keep the string lists
short,
or even use simple facts to handle the strings. For example:

% Prolog source file to be compiled and loaded at TEC_Start
atompart_match_fact('EVENT_Class','Fatal Exception occurred').
atompart_match_fact('EVENT_Class','IsEvents  ERROR
IntegrationServiceException').
atompart_match_fact('EVENT_Class','java.io.IOException: Stream closed').
atompart_match_fact('EVENT_Class2','The maximum number of characters for
this COBOL').
atompart_match_fact('EVENT_Class2','Failure retrieving policy access').


Your TEC rule would now look something like:
reception_action:
 (
  bo_get_classof(_event,_class),
  findall(_match,
            (
             atompart_match_fact(_class,_match),
             atompart(_msg,_match,_,_), !),
           [_matched]),  /* succeeds if at least one match is found */
        drop_received_event,
        commit_set
  ),

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