IBM Support

PM03382: TEP SIT 'IN DB2 PER COMMIT' IS CALCULATED AS "IN DB2 ELAPSED TIME PER COMMIT" INSTEAD OF "IN DB2 CPU TIME PER COMMIT"

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer's env:
z/OS V10, DB2 V9 NFM, OmPE 410, TEP  CJ621_tms621 Build 9166a

Customer's problem:
When setting up ALARM situation in TEP on Thread CPU consumption
ALARM is not generated on selection criteria but instead we get
ALARMs on Thread Elapsed Time. ALARMs are forwarded to our
support DB2 mailbox where we get 30-40 ALARMs a day

Local fix

  • N/A

Problem summary

  • ****************************************************************
* USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
*                 users of component                           *
*                 - Tivoli Enterprise Monitoring Agent         *
****************************************************************
* PROBLEM DESCRIPTION: In DB2 Per Commit in attribute group    *
*                      ALL THREADS is incorrect in TEP         *
****************************************************************
* RECOMMENDATION: Apply this PTF                               *
****************************************************************
PROBLEM SUMMARY:
A wrong In DB2 time field was used to calculate
In DB2 per commit.

PROBLEM CONCLUSION:
Use the correct In DB2 CPU time field to calculate
In DB2 per commit.

Problem conclusion

  • Use the correct In DB2 CPU time field to calculate
In DB2 per commit.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PM03382
    • 

  • Reported component name
    OM XE DB2PE/PM
    • 

  • Reported component ID
    5655OPE00
    • 

  • Reported release
    420
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2009-12-11
    • 

  • Closed date
    2010-04-06
    • 

  • Last modified date
    2010-05-04
    • 





    

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

    
PK98042
    

    • 

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

    
UK55861
    

    • 



Modules/Macros


    

  • KO2CT2SA KO2CT2SS KO2CT2S2

    



Fix information


    

  • Fixed component name
    OM XE DB2PE/PM
    • 

  • Fixed component ID
    5655OPE00
    • 



Applicable component levels


    

  • R420  PSY  UK55861
       UP10/04/09  P  F004
    • 



Fix is available


    

  • Select the PTF appropriate for your component level.
You will be required to sign in. Distribution on physical
media is not available in all countries.
    








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            04 May 2010
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback