IBM Support

PM28704: EXCESSIVE DSNB357I MESSAGES WERE FLOODING THE CONSOLE DB2STGLK/J

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MSGDSNB357I is displayed in a tight loop during a DB2
    restart following a temporary loss of a Coupling Facility.
    LPL recovery and DB2 restart are very slow.
    An inconsistency in DB2 code has been found that may lead to the
    excessive DSNB357I messages
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 users.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Excessive DSNB357I messages, indicating *
    *                      automatic LPL recovery suppressed.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The DSNB357I messages (automatic LPL recovery suppressed) are
    supposed to be limited in the same way that the DSNB250E
    messages (page range added to LPL) are.  However, the limiting
    of the messages may not be effective for multi-piece non-
    partitioned pagesets, for two reasons:
      - An inconsistency in which PB0 control block is checked for
        the DSNB250E message count.
      - For the case of an open failure, a PB0 may not exist for the
        dataset associated with the page being added to LPL.
    

Problem conclusion

  • The LPL logic has been modified to maintain only one DSNB250E
    message counter for non-partitioned objects - in the first PB0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM28704

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-13

  • Closed date

    2011-01-24

  • Last modified date

    2011-03-02

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

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

    UK64156 UK64157 UK64158

Modules/Macros

  • DSNB1LPL
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK64156

       UP11/02/08 P F102

  • R810 PSY UK64157

       UP11/02/08 P F102

  • R910 PSY UK64158

       UP11/02/08 P F102

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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 March 2011