IJ22910: EIF EVENTS FOR A GIVEN SITUATION GENERATED BY FTO HUB PAIRS ARE DIFFERENT IF THE EIF SLOTS HAVE BEEN CUSTOMISED.

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 5 (6.3.0.7-TIV-ITM-SP0005)

APAR status

• Closed as program error.

Error description

• Event Maps that are added, updated or deleted at the Primary
  Hub are not replicated to the runtime cache of the Mirror Hub.
  Consequently, after a failover occurs to the Mirror Hub, the
  events it generates will not honour the customization specified
  in the Situation's Event Map.
  

Local fix

• After an Event Map is added, updated or deleted at the Primary
  Hub, the Mirror Hub can be restarted. This will rebuild the
  Event Map cache so that it matches the associated DB table
  again.
  

Problem summary

• Event Maps that are added, updated or deleted at the Primary Hub
   are not replicated to the runtime cache of the Mirror Hub.
  Consequently, after a failover occurs to the Mirror Hub, the
  events it generates will not honour the customisation specified
  in the Situation's Event Map.
  
  
  EIF events for a given Situation generated by FTO Hub pairs are
  different if the EIF slots have been customised.
  

Problem conclusion

• FTO was changed to ensure EIFLOG notifications are generated
  which triggers the OTEA code to update the cached Event Map
  table when changes are made at the Primary Hub.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0005
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels