IBM Support

IJ01062: LARGE VOLUME OF KT1 REQUESTS DURING AN ITM-BASED TADDM DISCOVERY CAUSES HIGH CPU AT THE HUB TEMS

A readme is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem:
    When performing an ITM based TADDM discovery using the KT1
    component, a large volume (10K+) of
    getfile/executeCommand/putFile requests are made against the
    node list table on the hub TEMS, resulting in high CPU and a
    performance degradation
    
    Root Cause :
    Validation of each request involves an entire scan of the Node
    List table; the overhead of doing so becomes significant when
    the rate of requests is high and the Node List table is even of
    a moderate size.
    
    Solution :
    Optimise the KT1 code to avoid scanning the entire Node List
    table during request validation.
    

Local fix

  • N/A
    

Problem summary

  • When performing an ITM based TADDM discovery, (which relies on
    the KT1 component), a large volume (10K+) of
    getfile/executeCommand/putFile requests are made which results
    in many SOAP requests to query the
    node list table on the hub TEMS.  This results in high CPU and
    performance degradation at the Hub and also impacts tacmd users
    as that utility also relies on SOAP.
    
    
    Validation of each request involves an entire scan of the Node
    List table; the overhead of doing so becomes significant when
    the rate of requests is high and the Node List table is of even
    a moderate size.
    

Problem conclusion

  • Optimise the KT1 code to avoid scanning the entire Node List
    table during request validation.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
       | service pack | 6.3.0.7-TIV-ITM-SP0001
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ01062

  • Reported component name

    TEMA

  • Reported component ID

    5724C04TE

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-27

  • Closed date

    2019-05-06

  • Last modified date

    2019-05-06

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

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

    OA56394

Fix information

  • Fixed component name

    TEMA

  • Fixed component ID

    5724C04TE

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