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 number
IJ36202
Reported component name
TEMS
Reported component ID
5724C04MS
Reported release
630
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-11-18
Closed date
2022-05-02
Last modified date
2022-05-24
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
08 March 2023