Legacy ID:KA396634
Event closure is controlled by the EventAutoClose parameter in the mcell.conf.
If an event is closed at or before the 'new' rule phase it is considered 'dropped', if the 'EventAutoClose' parameter is set to 'Yes' then the cell will also close the first duplicate of that event.
A duplicate is classified as any event where all the slots configured as 'dup_detect' slots match. Run a search for 'dup_detect' and 'updates duplicate' in the cell kb reference guide for more info on this:
https://docs.bmc.com/docs/display/TSIM113/New+rules
To find out if this is happening run the cell with verbose tracing enabled and check for entries such as this..
20130513 122417.498605 mcell: RULES: BMC-IMC110008V: Analysing event #1612178 @0xad7b780
20130513 122417.498783 mcell: MESSAGES: BMC-IMC046014V: Send message #1.829645 XACT [27]
20130513 122417.499025 mcell: MESSAGES: BMC-IMC046014V: Send message #1.829646 XACT [26]
20130513 122417.499259 mcell: MESSAGES: BMC-IMC046014V: Send message #1.829647 XACT [13]
20130513 122417.499505 mcell: EVTPROC: BMC-IMC090110V: Removed event #1612178 @0xad7b780
20130513 122417.499594 mcell: RULES: BMC-IMC110009V: Terminating transaction on event #1612178 @0xad7b780
..then an event(1612168) mysteriously closing right after that one is removed.
To stop this behavior set 'EventAutoClose=No' in mcell.conf and restart your cell.
It has been identified as below defect, which is fixed in version 11.3.02:
DRTEC-18: The cell is deleting EVENT_INCIDENT_INFO events due to EventAutoClose=Yes
In TSIM 11.3.02, default value is set as No for EventAutoClose.