IZ71694: Increase FLUSH TIME to avoid missing records at RTEMS / Mirror

APAR status

• Closed as program error.

Error description

• The trouble is, the Stage2 at an RTEMS can take longer than 2
  minutes.
  Sitmon opens its EIBLOG listener before beginning to synchronise
  its tables and it does not begin to look at the EIBLOG queue
  until the table resync has completed.
  
  So any EIBLOG notifications generated at the Hub will sit on the
  queue until either the RTEMS completes its Stage2 .... or they
  are purged ... whichever happens first.
  
  This is how an RTEMS can end up dropping a whole set of EIBLOG
  notifications all generated within a short time span while the
  listener appears to be functioning properly.
  
  This problem applies to the following MDVs:
  6.2.0-TIV-ITM-FP0003
  6.2.0.3-TIV-ITM-IF0001
  6.2.0.3-TIV-ITM-IF0002
  6.2.0.3-TIV-ITM-IF0003
  6.2.1.0-TIV-ITM-IF0003
  6.2.1.0-TIV-ITM-IF0004
  6.2.1-TIV-ITM-FP0001
  6.2.2 GA
  6.2.2-TIV-ITM-FP0001
  

Local fix

• Define EIB_FLUSH_TIMER=120 in the TEMS config file, then recycle
  the TEMS to pick up the changes.
  

Problem summary

• IZ45193 introduced garbage cleanup to the EIB Log queue. The EIB
  log queues can sometimes become abandoned resulting in memory
  growth. IZ45193 utilized existing EIB log queue maintenance to
  perform cleanup of EIB log records that have not been picked up
  by the intended target within a reasonable amount of time.
  Unfortunately, it turns out that there are some cases where the
  intended target has not been able to pick up its EIB log records
  within the default expected time frame. This results in EIB
  records being missed by the intended target. The missed EIB log
  records are known to result in an incomplete node list. This in
  turn can cause incomplete situation distributions on the remote
  Tivoli Management Server.
  
  The problem has also been seen at the hot standby Tivoli
  Management Server. This can result in a variety of missing
  information at the hot standby Tivoli Management Server.
  

Problem conclusion

• The default time interval for EIB log queue maintenance has been
  increase to two hours from its original two minutes. This should
  be more than enough time for an intended target to pick up EIB
  log records intended for it. The existing EIB_FLUSH_TIMER
  keyword can be used to override this default by placing it into
  the Tivoli Management Server configuration file.  For instance:
  EIB_FLUSH_TIMER=60 to set the time interval to 60 minutes.
  
  
  
  The fix for this APAR is included in the following maintenance
  vehicle:
      | fix pack | 6.2.1-TIV-ITM-FP0002
      | fix pack | 6.2.2-TIV-ITM-FP0002
  

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:

  OA32181 OA32396 OA32897

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R621 PSY

     UP