IBM Support

IV43806: SITUATIONS ASSOCIATED WITH SYSTEM STATUS DATA (KA4SYSTS) RANDOMLY FAIL.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Approver: Terry Ackman
    
    Reported Release:  6.2.3 FP2
    
    Problem: Situations, or data, associated with System Status may
    randomly fail to be presented. If, on the System workspace
    screen, there may be no data shown for the System Status line.
    If a situation, you may see something like this in the message
    queue log for the situation:
    
    Stopping situation I5_ASP_All_Warning.
    Failure for a report or situation I5_ASP_All_Warning.
    
    
    If displaying the data from the workspace you may see the
    following:
    
    Failure for a report or situation .
    
    For a situation, the attribute group is OS400 System Status or
    you might see ka4systs. It's the data like CPU percent, etc. It
    is these situations associated with System Status data that are
    randomly failing.
    

Local fix

  • This may or may not work, sometimes changing the logging
    level for the ka4agentxx files (found in file QAUTOTMP/KMSPARM)
    can make this work or fail. If only logging errors:
    
    KBB_RAS1=ERROR
    
    change it to:
    
    KBB_RAS1=ERROR (UNIT:KA4 ALL) (UNIT:KRA ST)
    
    and it may work. Or if already logging a lot, changing to only
    log ERROR may make this work.
    

Problem summary

  • Situations or data associated with System Status, such as CPU
    utilization, may randomly fail to be presented.  This issue
    affects the OS400 System Status (KA4SYSTS) attribute group.
    This attribute group contains the CPU percent utilization
    attribute.
    
    For a situation, messages similar to the following may appear in
    the QAUTOMON/KMSOMLOG message queue log (DSPOMALOG):
    
        Stopping situation I5_ASP_All_Warning.
        Failure for a report or situation I5_ASP_All_Warning.
    
    When displaying data in the portal client using the System
    workspace, there may be no data shown for the System Status view
    or there may be missing data if using a historical view.  A
    message similar to the following may appear in the
    QAUTOMON/KMSOMLOG message queue log (DSPOMALOG):
    
        Failure for a report or situation.
    

Problem conclusion

  • The agent code was changed to correct how a variable was handled
    that caused unpredictable issues with an OS API.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.2.3-TIV-ITM-FP0004
      | fix pack | 6.3.0-TIV-ITM-FP0002
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV43806

  • Reported component name

    ITM AGENT ISERI

  • Reported component ID

    5724C04A4

  • Reported release

    623

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-05

  • Closed date

    2013-07-18

  • Last modified date

    2013-10-17

  • 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

    ITM AGENT ISERI

  • Fixed component ID

    5724C04A4

Applicable component levels

  • R623 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"623"}]

Document Information

Modified date:
30 December 2022