IJ44324: A HUB TEMS FAILS TO RESPOND TO REQUESTS TO START OR STOP SITUATIONS; SITUATIONS FAIL TO START ON AN FTO HUB AFTER IT IS PROMOTED

APAR status

• Closed as program error.

Error description

• The Hub's EIB log is the device used by the Sitmon component of
  an RTEMS to keep the local database in sync with the Hub's. The
  EIB log is also used to send commands to the Sitmon component at
  any TEMS, including the Hub's. If no EIB log updates are
  received by Sitmon for a prolonged period, Sitmon assumes that
  the connection to the Hub has been lost. It therefore recreates
  the EIB log request to the Hub and initiates another database
  resynchronisation. The problem is that after dropping the EIB
  Log request, the Hub's Sitmon was not recreating the request. As
  a result, the Hub's Sitmon would not 'hear' requests to stop or
  start Situations or to promote itself to the Primary Hub.
  
  In fact, it isn't necessary for the Hub's Sitmon to drop its EIB
  request to the Hub, even after prolonged periods of inactivity.
  So, the code has been changed to avoid dropping the EIB log
  request at the Hub.  In addition, while such periods of
  inactivity are not usual, the code writes additional diagnostics
  whenever the EIB log is inactive for prolonged periods so that
  the cause can be investigated further.
  

Local fix

Problem summary

• A Hub TEMS fails to respond to requests to start or stop
  Situations; Situations fail to start on an FTO Hub after it is
  promoted to primary.
  
  
  The Hub's EIB log is the device used by the Sitmon component of
  an RTEMS to keep the local database in sync with the Hub's.  The
  EIB log is also used to send commands to the Sitmon component at
  any TEMS, including the Hub's.  If no EIB log updates are
  received by Sitmon for a prolonged period, Sitmon assumes that
  the connection to the Hub has been lost.  It therefore recreates
  the EIB log request to the Hub and initiates another database
  resynchronisation.  The problem is that after dropping the EIB
  Log request, the Hub's Sitmon was not recreating the request.
  As a result, the Hub's Sitmon would not 'hear' requests to stop
  or start Situations or to promote itself to the Primary Hub.
  

Problem conclusion

• In fact, it isn't necessary for the Hub's Sitmon to drop its EIB
   request to the Hub, even after prolonged periods of inactivity.
    So, the code has been changed to avoid dropping the EIB log
  request at the Hub.  In addition, while such periods of
  inactivity are not usual, the code writes additional diagnostics
   whenever the EIB log is inactive for prolonged periods so that
  the cause can be investigated further.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0014
  

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