IZ80916: MISSING DISTRIBUTION RECORDS AT RTEMS

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

• PROBLEM DESCRIPTION:
  
  Certain events can lead to missing distributions at the RTEMS
  for a
  directly attached agent. The distribution issue does not appear
  until
  after the RTEMS has reconnected to the HUB. This issue is due to
  a
  failure to expand an MSL for an agent that has switched to the
  RTEMS
  before the reconnection with the HUB.
  
  There are a number of conditions in which an MSL may not expand
  at an
  RTEMS when it should.
  
  
  RECREATE INSTRUCTIONS:
  
  - Create agents A1, A2 and A3
  - Add agent A1 and A3 to MSL1
  - Add agent A1 and A2 to MSL2
  - Distribute situation-A to MSL1
  - Distribute situation-B to MSL2
  - Connect agent A1 and A2 to RTEMS-A
  - Connect agent A3 to RTEMS-B
  - Bring up the HUB, RTEMS-A, RTEMS-B and all agents
  - Switch agent A2 to RTEMS-B
  - everything should be fine so far....
  - Restart the HUB causing RTEMS-B to reconnect to the HUB
  - Situation-B will appear to not be distributed to agent A2 at
  RTEMS-B
  after the reconnect.
  - Use ITMSuper to verify
  

Local fix

• Use ITMSuper to correct the distribution or restart the RTEMS
  

Problem summary

• Missing distributions may occur at a remote management server if
  there has been agent switching and the remote management server
  reconnect. The missing distribution will not occur until after
  the remote management server reconnects to the HUB management
  server . Managed System Lists (MSL) must be involved in the
  affected distributions.
  

Problem conclusion

• Management server code has been changed to keep track of MSL
  distributions for agents that have moved to another Remote
  Tivoli Enterprise Management Server.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.1-TIV-ITM-FP0004
    | fix pack | 6.2.2-TIV-ITM-FP0004
  

Temporary fix

• The problem can be corrected using ITMSuper or by restarting the
  remote management server.
  

Comments

APAR Information

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

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

  OA35046 OA35190

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R622 PSY

     UP