IBM Support

PM01580: NTH DOES NOT USE DB2 START ECB. 'NOT ACTIVE' STATUS SHOWN ON ZLOG PANEL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Only one of four DB2 subsystems was detected by OmPE after all
    four DB2 subsystems were stopped and started again
    
    Another symptom was reported that the DB2 couldn't be monitored
    and showed NOT ACTIVE on Classic RLOG panel.  All the
    definitions required seems correct including RRS/MVS & RACF
    related.  But the log showed FPEV0223E with RS=00F30091 and the
    DB2 INSTANCE was not started.
    

Local fix

  • Please manually restart the PEServer subtask for the DB2
    subsytem which can't be monitored/identified:
    
    /F <STC_name>,F PESERVER,P <DB2_SSID> to stop the PE Server
    subtask
    /F <STC_name>,F PESERVER,S <DB2_SSID> to start the PE Server
    subtask
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Classic Interface                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: 'Not Active' status incorrectly         *
    *                      displayed on ZRLOG panel.               *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    *                                                              *
    ****************************************************************
    PROBLEM SUMMARY:
    The 'Not Active' status is displayed due to a start-up conflict
    between PE Server and Near Term History.
    
    PROBLEM CONCLUSION:
    Code is changed to avoid DB2 the start-up conflict between PE
    Server and NTH.
    

Problem conclusion

  • Code is changed to avoid DB2 the start-up conflict between PE
    Server and NTH.
    
    KEYWORDS : DB2 NTH PESERVER
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM01580

  • 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-11-19

  • Closed date

    2010-02-19

  • Last modified date

    2010-03-01

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

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

    UK54368 UK54369

Modules/Macros

  • KO2OSBSB
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK54368

       UP10/02/24 P F002

  • R420 PSY UK54369

       UP10/02/24 P F002

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:
01 March 2010