IBM Support

PK76938: SCREEN ZDFVS DOES NOT DISPLAY THREADS THAT ORIGINATE DISTRIBUTED ALLIED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With distributed allied threads there is an originating DB2 and
    a targetDB2.
    We are displaying the threads correctly on the target
    because they are a distributed allied type of thread.
    We need to also check for threads of any type that start a
    distributed allied thread on another system and show them on the
    display.
    The ZDFVS screen now just shows Distributed Allied type threads.
    We need to also show the threads that start Distributed Allied
    threads.
    
    Other symptoms possible:
    Dump Title: OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=OMXD2DX ,
                 LMOD=#UNKNOWN#L, CSECT=C2DCNS  , OFFSET=  0748
    SNAP issued from KO2CDCNB+7D2 (at PK74788 level) because no
    TRACKING TABLE was found.  Earlier, there was and ABEND0C4-10
    KO2XDFSA+12C (at PK65753 level) on a D5035004A194 (CLC)
    instruction with R5 bad.  KO2XDFSA tried to access the DB2 LLOCs
    using DB2 V8 (R810) offsets, but should have used DB2 V9 (R910)
    offsets.  This caused the ABEND0C4 and led later to the SNAP
    being issued by KO2CDCNB.  When Omegamon is working with DB2 V9,
    V9 offsets to control blocks should be used.  Users accessing
    DB2 V9 should APPLY the PTF for this APAR.
    .
    Additional symptom:
    Classic panel - ZDFST showed the following msg:
    DDF Not Included In DB2 Subsystem Being Monitored
    though DDF is active running at that time.
    .
    Still another symptom:
    ABEND0C4-10 KO2XVTMG+C4 if z/OS 1.10 is used.  This occurs on
    a 58746000 (Load) instruction, with R6 containing an eyecather
    'DEBX' instead of the ACDEB address.  For searchability:
    KO2XVTSF.
    .
    Another symptom was reported that the DDF Statistics panel
    KD2WDDFD showed all blank values.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Tivoli Enterprise Monitoring Agent       *
    *                 -   Classic Interface                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: SCREEN ZDFVS DOES NOT DISPLAY THREADS   *
    *                      WHICH START A DISTRIBUTED ALLIED        *
    *                      THREAD ON ANOTHER SYSTEM.               *
    *                                                              *
    *                      DDF Status shows active after           *
    *                      STOP DDF MODE(SUSPEND) command.         *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    The thread on the originating system could be of any type and
    start a distributed allied thread on another DB2 system.
    
    When DDF is in SUSPEND status screen still display active.
    
    PROBLEM CONCLUSION:
    Change logic to display threads which have started a
    distributed allied threads on another system.
    
    Check for DDF SUSPEND status.
    

Problem conclusion

  • Change logic to display threads which have started a
    distributed allied threads on another system.
    
    Check for DDF SUSPEND status.
    
    KEYWORDS :  DISPLAY THREADS DISTRIBUTED ALLIED ZDFVS
                DDF SUSPEND
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK76938

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-04

  • Closed date

    2009-04-06

  • Last modified date

    2010-03-02

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

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

    UK44535

Modules/Macros

  • KO2CDFCA KO2CDFCS KO2CDFC2 KO2CDFSA KO2CDFSS
    KO2CDFS2 KO2CSYSA KO2CSYSS KO2CSYS2 KO2CTHIA KO2CTHIS KO2CTHI2
    KO2CTHSA KO2CTHSS KO2CTHS2 KO2CT2IA KO2CT2IS KO2CT2I2 KO2CT2SA
    KO2CT2SS KO2CT2S2 KO2ITCAA KO2ITCAS KO2ITCA2 KO2ODSTB KO2OTCIA
    KO2OTCIS KO2OTCI2 KO2XDFSA KO2XDFSS KO2XDFS2 KO2XTHSA KO2XTHSS
    KO2XTHS2 KO2XVTSF KO2XVTSG
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK44535

       UP09/04/09 P F904

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":"410","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":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 March 2010