IBM Support

IZ45039: SITUATION SEVERITY WRONG AT TEC FOR DOOPERED SITUATIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment:
    
      ITM 6.2 - OS was AIX 5.3
      TEC 3.9 - OS was AIX 5.3
    
    
    
    Problem Description:
    
     The severity of situation changes when viewed through EIF tab
    and TEC .
     example : In the EIF tab of Situation Editor , customer has set
    the severity as
    "Warning". But when the event is forwarded to TEC then what we
    receive
    the situation is a severity "Critical".
    
    
    Had a look at the ms logs :
    
    (494B06F1.08C9-C:kfaottev.c,423,"KFAOT_Translate_Event") Input
    sit:
    sitName<DB2_Buffer_Pool_Warning_N>, oStatus< >, nStatus<Y>,
    sitInfo<S=C;F=Y;D=0
    
    which shows severity as Critical
    
    Looking at the sit.out for the same situation :
    
    <SITINFO>
    <![CDATA[TFWD=Y;SEV=Warning;TDST=0;~]]>
    </SITINFO>
    
    which shows that the severity is Warning.
    
    
    The conclusion drawn was :
    --------------------------------------------------------------
    If there are 2 similar situations that have the same sampling
    interval but different severities, then one severity value may
    overlay
    the other.
    -------------------------------------------------------------
    
    
    Detailed Recreation Procedure:
    
    
    
    Related Files and Output:
    
    All the related log files are located in Ecurep:
    
    https://ecurep.mainz.de.ibm.com/aex/browseServer.jsp?browseDirec
    tory=/ecurep/pmr/8/2/82375,000,738
    

Local fix

  • If there are 2 similar situations that have the same sampling
    interval but different severities, then one severity value may
    overlay the other . So we can modify the sampling interval of
    one of the situation .
    

Problem summary

  • If two similar situations are dupered at monitoring server
    start-up, and these situations have different security levels
    specified for the Event Integration Facility of the Tivoli
    Enterprise Console, the security level presented at the Tivoli
    Enterprise Console may be incorrect.
    

Problem conclusion

  • The code was modified to move Event Integration Facility
    parameter information to the situation's original object so it
    will not be confused with the dupered object.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
       | interim fix | 6.2.0.3-TIV-ITM-IF0001
    

Temporary fix

  • Specify only one security level for all situations that are
    dupered together.
    

Comments

APAR Information

  • APAR number

    IZ45039

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-03

  • Closed date

    2009-06-29

  • Last modified date

    2009-07-21

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

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

    OA29587 OA30265 IZ59463

Fix information

  • Fixed component name

    TEC GUI INTEGRA

  • Fixed component ID

    5724C04TG

Applicable component levels

  • R620 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCTLMS","label":"ITM TEC GUI Integration V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
21 July 2009