IZ95074: WHEN INTERMEDIATE NODE IS INSERTED IN NAV TREE, SITUATION ON FIRST NODE IS NO LONGER DISPLAYED.

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• Customer sees open situations on an instance of the VI agent.
  Customer starts a second instance of the VI agent on the same
  server.  The open situations clear from the first instance and
  then open on the new instance. Customer expects the situations
  to remain open on the first instance while the second instance
  comes online.
  

Local fix

• Restart the TEPS or you can restart the situation though in the
  later you will have to wait until the sit fires again.
  

Problem summary

• When starting a second instance of a subnode based application
  (ex.  DB2), a situation that was open on the first subnode
  instance disappears.  Recycling the portal server causes the
  event to be displayed again.
  
  When a second instance of a subnode or instance based
  application is started, an application group folder is inserted
  in the physical navigator, and all instances of the application
  are placed in the group folder.  When the first subnode instance
  is moved under the group folder, any events that were open on
  the first instance are removed from the physical topology and
  the situation event console.  The second subnode instance
  correctly displays any open situations.  Recycling the portal
  server causes the missing events to reappear on the first
  subnode instance.  This problem only occurs when starting with a
  single subnode instance, then starting a second subnode
  instance, causing the application group folder to be inserted.
  Starting a third (or more) subnode instance behaves correctly.
  

Problem conclusion

• Previous implementation deleted and recreated the managed object
  representing the first subnode instance, causing the portal
  server to lose any situation state information about that
  subnode.  Modified code to move the subnode by deleting the edge
  to the current parent, and creating a new edge to the new
  parent.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0006
  

Temporary fix

• Recycle the portal server.
  

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

  TEPS

• Fixed component ID

  5724C04PS

Applicable component levels

• R622 PSY

     UP