IBM Support

PK41044: OMEGAMON EXCEPTION LOGN PARM SHOULD NOT ALLOW 0 AS VALUE / THE VALUE IS FROM 1 TO 100 PER MANUAL

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Omegamon Exception LOGN parm should not allow 0 as value /
    the value is from 1 to 100 per manual.
    Currently, the customer entered LOGN=0 with no error msg.
    However, the DB2 syslog showed 1 active log available, yet
    Omegamon still flag the alert with active log=1.
    If the customer wants to disable this LOGN exception, they need
    to change the STATE=OFF from the profile for LOGN and they
    should not use LOGN=0.
    With this apar/fix, we will disallow LOGN=0 condition, the code
    and the manual will match with each other.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   OMEGAMON Server                          *
    *                 -   CUA Interface                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: The minimum threshold values for LOGN   *
    *                      and 24 other exceptions was allowed to  *
    *                      be 0, though their documented ranges    *
    *                      are 1-100.  The maximum value of the    *
    *                      LKUS and RELM exceptions was allowed to *
    *                      be 99999999, though their ranges are    *
    *                      documented as 1-100.                    *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    Macro default of 0 was being used for the minimum threshold
    value for 25 exceptions.  Maximum threshold values for LKUS and
    RELM were incorrectly explicitly specified.
    

Problem conclusion

  • The minimum threshold value of 1 is now explicitly specified on
    the exceptions' definitions.  The maximum threshold values for
    LKUS and RELM now default to 100.
    
    KEYWORDS :
    CICT COMT DWAT EDMU ENTO ENTU ENTW ETIM GETP IDBK IDBT IDFR INDT
    LKUS LOGN PGUP POLU POLW PREF RELM RIO  SUSL TCPU THDQ TMAX
    THRESHOLD VALUE EXCEPTION
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK41044

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-03-12

  • Closed date

    2007-03-22

  • Last modified date

    2007-04-01

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

    OA18865

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

    UK23273 UK23274

Modules/Macros

  •    KD2LOPTN KO2ODFEB
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R310 PSY UK23273

       UP07/03/29 P F703

  • R410 PSY UK23274

       UP07/03/29 P F703

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

Document Information

Modified date:
01 April 2007