IBM Support

PM67547: MSGDSNP031I MAXIMUM EXTENTS 251 REACHED WHEN EXTENDING DB2 PAGE SET WITH DSSIZE OR PIECESIZE GREATER THAN 64 GB

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MSGDSNP031I MAXIMUM EXTENTS 251 REACHED WHEN EXTENDING DB2 PAGE
    SET WITH DSSIZE OR PIECESIZE GREATER THAN 64 GB.  MSGDSNP011I
    RC00D70014.
    

Local fix

  • Suggest set DFSMS SMS Data Class Extent Constraint Relief field
    to YES, which removes 251-255 extent limit and supports up to
    7257 extents.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Error message MSGDSNP031I or            *
    *                      MSGDSNP011I RC00D70014, maximum extents *
    *                      of 251 reached, is issued when          *
    *                      extending a DB2 data set associated     *
    *                      with the page set created with DSSIZE   *
    *                      (or PIECESIZE) 128 or 256 GB.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The current DB2 sliding scale algorithm is designed for page set
    with DSSIZE (or PIECESIZE) up to 64 GB.  The new size 128 and
    256 GB introduced in DB2 V10 may receive RC00D70014, maximum
    extents 251 reached during extend.  The error could be avoided
    if SMS Data Class Extent Constraint Relief is enabled as it
    allows maximum 7257 extents.
    

Problem conclusion

  • DB2 sliding scale is changed to support 128 and 256 GB DSSIZE
    (or PIECESIZE).  It is for DB2 users who do not enable SMS Data
    Class Extent Constraint Relief feature provided by DFSMS.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM67547

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-25

  • Closed date

    2012-10-23

  • Last modified date

    2012-12-04

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

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

    UK82873

Modules/Macros

  • DSNPDFN1 DSNPXTN0 DSNPXTRC DSNUGSPC
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK82873

       UP12/11/08 P F211

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":"10.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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 December 2012