IBM Support

PM06030: ZSUMM INCREMENTS TSO FOREGROUND THREADS COUNT & BATCH CONNECTION CONNECTIONS COUNT AS QMF BATCH JOB. WRONG THREAD TYPE REPORTED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Omegamon panel ZSUMM identifies a batch QMF job as a TSO or
    foreground thread (incorrect), but a Batch Connection
    (correct).
    
    Also, ZSUMM Batch Connection and Thread counts aren't correct.
    They don't agree with DB2 DIS THREAD, and Classic Thread
    Display.  They don't agree with DB2 internal counter of batch
    connections, and hence IDBK exception processing isn't correct.
    Additional change:
    Fixed defect found in PTF UK54122: DSNTEP2 parallel threads
    reported as TSO threads instead of Background threads.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Classic Interface                        *
    *                 -   CUA Interface                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: QMF Batch job thread incorrectly shown  *
    *                      as TSO foreground thread in ZSUMM.      *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    *                                                              *
    ****************************************************************
    PROBLEM SUMMARY:
    Thread type 'TSO' incorrectly assigned to all QMF threads
    without respect to agent's address space origin.
    
    PROBLEM CONCLUSION:
    Code changed to fix this problem.
    

Problem conclusion

  • Code changed to fix this problem.
    
    KEYWORDS : QMF BATCH JOB THREAD TSO
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM06030

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-27

  • Closed date

    2010-03-10

  • Last modified date

    2010-04-03

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

    PM00701

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

    UK54805 UK54993

Modules/Macros

  • KO2CTHIA KO2CTHIS KO2CTHI2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK54993

       UP10/03/17 P F003

  • R420 PSY UK54805

       UP10/03/17 P F003

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:
03 April 2010