IBM Support

PK93794: SHOW ALL THREADS IF AUTODETECT=NO FOR CONFIG. WITH TWO MEMBERS OF SAME DSG ON SAME LPAR AND ONLY ONE BEING CONFIGURED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • No threads shown if AUTODETECT=NO for config. with two members
    of same DSG on same LPAR and only one being configured
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   PE Server subtask                        *
    *                 -   Classic Interface                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When members of a Data Sharing Group    *
    *                      are running on the same LPAR and the    *
    *                      OMEGAMON Collector is configured with   *
    *                      option AUTODETECT set to NO and the     *
    *                      scope in the Classic Interface (VTAM)   *
    *                      is set to S for a local member which    *
    *                      was not configured in ICAT, VTAM will   *
    *                      not display thread data.                *
    *                      Message FPEV3016W is issued to the PE   *
    *                      Server subtask log (SYSPRINT).          *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    During start up the OMEGAMON Collector starts PE Server
    subtasks for each configured or automatically detected DB2
    Subsystem. The Classic Interface can then monitor local DB2
    Subsystems for which a PE Server subtask is up and running as
    well as remote members of a Data Sharing Group for which a local
    monitored member exists. When the Classic Interface issues data
    retrieval requests for local members with scope single (S), the
    request is routed to the monitoring PE Server subtask and will
    fail if the monitoring PE Server subtask is not up and running.
    
    PROBLEM CONCLUSION:
    When members of a Data Sharing Group are running on the same
    LPAR and the OMEGAMON Collector is configured with option
    AUTODETECT set to NO and the scope in the Classic Interface
    (VTAM) is set to a local member which was not configured in
    ICAT but another local member of the same Data Sharing Group is
    monitored on the same LPAR, VTAM will display the requested
    thread data for the selected local member.
    When the Classic Interface issues data retrieval requests for a
    local member of a Data Sharing Group with scope single (S), the
    requests are routed to the monitoring PE Server subtask or to
    the PE Server subtask which monitors another local member of
    the same Data Sharing Group.
    

Problem conclusion

  • When members of a Data Sharing Group are running on the same
    LPAR and the OMEGAMON Collector is configured with option
    AUTODETECT set to NO and the scope in the Classic Interface
    (VTAM) is set to a local member which was not configured in
    ICAT but another local member of the same Data Sharing Group is
    monitored on the same LPAR, VTAM will display the requested
    thread data for the selected local member.
    When the Classic Interface issues data retrieval requests for a
    local member of a Data Sharing Group with scope single (S), the
    requests are routed to the monitoring PE Server subtask or to
    the PE Server subtask which monitors another local member of
    the same Data Sharing Group.
    
    KEYWORDS : AUTODETECT DB2 RESTART 3 MINUTES FPEV3016W VTAM
               THREAD SUMMARY DSG SCOPE SINGLE LOCAL MEMBER
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK93794

  • 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-08-13

  • Closed date

    2009-09-03

  • Last modified date

    2009-10-03

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

    PK75757

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

Modules/Macros

  • DUMM1KO2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R420 PSN UK49803

       UP09/09/09 P F909

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 October 2009