IV04685: UA SUBNODES MAY FAIL TO COME ONLINE, EVEN DATAPROVIDER SUBNODE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Severity: 1
    Approver:BEH
    Compid:  5724K1000 Tivoli Universal Agent
    Abstract:UA Subnodes may fail to come online, even DataProvider
    subnode
    
    Environment:
    ITM 6.2.2
    
    Problem Description:
    DataProvider failed to start when UA started intermittently.
    Node status of DP gets "N" although Universal Agent itself is
    "Y".
    At that time, you cannot see data on TEP client.
    
    Detailed Recreation Procedure:
    Recreate is very difficult as problem is rooted in thread timing
    that can expose a thread safety issue on WaitList.
    
    Related Files and Output:
    The following trace parameter is useful to diagnose.
    
    KBB_RAS1=ERROR (UNIT:kumdcw STATE DETAIL) (UNIT:kumdchsv STATE)
    (UNIT:kumamain ALL)
    

Local fix

Problem summary

  • Universal Agent subnodes may fail to come online during startup.
    
    
    Universal Agent subnodes may fail to come online during startup
    due to the internal data structure not being thread safe. This
    exposure only exists during the startup phase of Universal Agent
    when the internal data structure is being populated.
    

Problem conclusion

  • Two steps were taken to address the thread safety exposure.
    First, a mutex lock was implemented on the internal data
    structure. Second, a new Universal Agent environment variable
    named KUMA_USE_WAITLISTLOCK was introduced to arm or disarm the
    mutex lock.  By default this environment variable is not
    defined, meaning the mutex lock is not being used.
    
    To arm the mutex lock, thus realizing effects of this APAR fix,
    the user must add to um.ini (UNIX/Linux) or KUMENV (Windows) the
    environment variable as ->
    KUMA_USE_WAITLISTLOCK=Y.
    
    Because this APAR has been so rarely encountered, it is highly
    recommended to not implement KUMA_USE_WAITLISTLOCK=Y unless this
    problem is experienced.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.2.2-TIV-ITM-FP0007
      | fix pack | 6.2.3-TIV-ITM-FP0001
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV04685

  • Reported component name

    UNIVERSAL AGENT

  • Reported component ID

    5724K1000

  • Reported release

    622

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-07

  • Closed date

    2011-09-20

  • Last modified date

    2012-06-07

  • 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

    UNIVERSAL AGENT

  • Fixed component ID

    5724K1000

Applicable component levels

  • R622 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Universal Agent

Software version:

622

Reference #:

IV04685

Modified date:

2012-06-07

Translate my page

Machine Translation

Content navigation