IBM Support

PK58027: MESSAGE ID "O20910" IS NOW "KO2O0910W"

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MESSAGE ID "O20910" IS NOW "KO2O0910W"
    
    Code in SPENU(KD2SMSG) must be updated to correctly process a
    changed message ID. "O20910" is now "KO2O0910W". This simple
    change is required.
    

Local fix

  • The customer put together a NETVIEW (workaround) routine to send
    a modify command (see below) to Omegaview when it sees certain
    DB2 console messages indicating that DB2
    is down so that Omegaview will display the correct DB2 status
    and stop repeatively polling Omegamon DB2.
    .
    F CANSMV,NTD KMVAF 'RKANCMD(KMVAFC8) RID(R27) REQUEST(STOP)
    SESSION(DB2A)'
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   CUA Interface                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Status for lost DB2 subsystems          *
    *                      not reported in OMEGAMON for DB2 CUA    *
    *                      session.                                *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    Because the message OMEGAMON for DB2 issues for a lost
    subsystem changed from "O20910" to "KO2O0910W" the status
    lights reported in OMEGAMON for DB2 CUA session were not
    updated. Consequently the lights on OMEGAVIEW were incorrect
    as well.
    
    PROBLEM CONCLUSION:
    Change logic to detect the new message and
    properly report the changed status to OMEGAVIEW.
    

Problem conclusion

  • Change logic to detect the new message and
    properly report the changed status to OMEGAVIEW.
    
    KEYWORDS :
    CUA INCORROUT LOST DB2 SUBSYSTEM MSGO20910 MSGKO2O0910W
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK58027

  • 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

    2007-12-11

  • Closed date

    2008-03-03

  • Last modified date

    2008-04-01

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

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

    UK34200 UK34201

Modules/Macros

  • KD2ESTAT KD2SMSG
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R310 PSY UK34200

       UP08/03/05 P F803

  • R410 PSY UK34201

       UP08/03/05 P F803

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:
01 April 2008