IJ36202: REQUESTS TO READ THE GLOBAL LOCATION BROKER MAY RETURN INCOMPLETE RESULTS. A SCAN OF THE GLB MIGHT CAU

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 12 (6.3.0.7-TIV-ITM-SP0012)

APAR status

• Closed as program error.

Error description

• In order to download the contents of the Global Location Broker,
  a client will typically allocate a buffer and issue one or more
  requests that populate the buffer until all entries in the GLB
  have been read.
  
  The code that populates the buffer fails to correctly calculate
  where the next read from the client should start.
  
  Consequently, the entries returned to the client might be
  incomplete or duplicates.
  
  Depending on how the client is implemented, the client may loop
  and return the same entries until terminated.
  
  Exposure to the defect occurs when the number of entries in the
  GLB exceeds 128.
  
  The number of entries in the GLB is a function of the number of
  RTEMS and Warehouse Proxy Agents throughout the ITM enterprise
  together with the number of network interfaces and protocols
  that each supports.
  
  To date, the only application known to loop as a result of the
  defect is the kdclbad utility.
  
  However, other applications that scan the GLB, such as an RTEMS
  when searching for its associated WPA, can be affected because
  of the incomplete results that are returned.
  
  
  (Solution)
  The code was modified to correctly return to the client where
  the next read of the GLB should begin.
  
  The code was also optimized so that each request to the GLB
  returns only as many entries as can be accommodated in the
  client's buffer.
  
  ***
  

Local fix

Problem summary

• In order to download the contents of the Global Location Broker,
   a client will typically allocate a buffer and issue one or more
   requests that populate the buffer until all entries in the GLB
  have been read.
  
  The code that populates the buffer fails to correctly calculate
  where the next read from the client should start.
  
  Consequently, the entries returned to the client might be
  incomplete or duplicates.
  
  Depending on how the client is implemented, the client may loop
  and return the same entries until terminated.
  
  Exposure to the defect occurs when the number of entries in the
  GLB exceeds 128.
  The number of entries in the GLB is a function of the number of
  RTEMS and Warehouse Proxy Agents throughout the ITM enterprise
  together with the number of network interfaces and protocols
  that each supports.
  
  To date, the only application known to loop as a result of the
  defect is the kdclbad utility.
  
  However, other applications that scan the GLB, such as an RTEMS
  when searching for its associated WPA, can be affected because
  of the incomplete results that are returned.
  
  
  - Requests to read the Global Location Broker may return
  incomplete results.
  - A scan of the GLB might cause an application, e.g.  the
  utility kdclbad, to loop.
  

Problem conclusion

• - The code was modified to correctly return to the client where
  the next read of the GLB should begin.
  - The code was also optimised so that each request to the GLB
  returns only as many entries as can be accommodated in the
  client's buffer.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0012
  

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