IBM Support

PM65767: IN V10 NFM, WORKFILE TABLE SPACE SELECTION ALGORITHM IS NOT SELECTING WORKFILE PBG TABLE SPACES IN AN EXPECTED MANNER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In V10 NFM, DB2 allows for creation of partition-by-growth (PBG)
    table spaces in Workfile database. However, DB2 is not selecting
    these table spaces in a manner it should. Specifically:
    .....
    1) DGTT with WFDBSEP=YES should select PbG as the first option
       (regardless of SECQTY), as opposed to selecting any
       SECQTY > 0 table space (classic-segmented or PBG).
    .....
    2) Non-DGTT with WFDBSEP=NO (e.g. sort workfiles) should select
       PbG as the last resort (regardless of SECQTY).
    .....
    3) Non-DGTT with WFDBSEP=YES (e.g. sort workfiles) should
       never select PbG (even if the PbG has SECQTY 0).
    .....
                                              (f150319 f150363)
    ....
    Please note that the current behavior is not really a bug (i.e.
    it will not cause an abend), it is more that the behavior is not
    in line with the direction for workfile database PBG.
    
    Additional keywords: SQLPBG
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS (NFM) users of Workfile  *
    *                 database with partition-by-growth (PBG)      *
    *                 workfile table spaces in it                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: In DB2 10 NFM, workfile table space     *
    *                      selection algorithm is not selecting    *
    *                      workfile PBG table spaces in an         *
    *                      expected manner                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DB2 10 NFM allows for creation of partition-by-growth (PBG)
    table spaces in Workfile database. However, in particular
    scenarios, DB2 was not selecting these table spaces in a manner
    that it should. Specifically:
    
    1. DGTT, when the zparm WFDBSEP value is YES, should select PBG
       as the top choice (regardless of its SECQTY, so even if the
       PBG has a zero SECQTY), as opposed to the top choice being
       any non-zero SECQTY table space (classic-segmented or PBG).
       This is already followed today for the case of DGTT with
       WFDBSEP=NO.
    
    2. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value
       is NO, should select PBG as the last resort (regardless of
       its SECQTY, so even if the PBG has a zero SECQTY).
    
    3. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value
       is YES, should never select PBG (regardless of its SECQTY, so
       even if the PBG has a zero SECQTY).
    

Problem conclusion

  • Code has been changed in the workfile table space selection
    algorithm to select PBG workfile table spaces in the following
    manner:
    
    1. DGTT, when the zparm WFDBSEP value is YES, will select PBG
       as the top choice (regardless of its SECQTY, so even if the
       PBG has a zero SECQTY). This is already followed today for
       the case of DGTT with WFDBSEP=NO.
    
    2. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value
       is NO, will select PBG as the last resort (regardless of its
       SECQTY, so even if the PBG has a zero SECQTY).
    
    3. Non-DGTT (e.g. sort workfiles), when the zparm WFDBSEP value
       is YES, will never select PBG (regardless of its SECQTY, so
       even if the PBG has a zero SECQTY).
    
    Additional keywords: SQLPBG SQLDGTT SQLCGTT
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM65767

  • 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-05-29

  • Closed date

    2012-08-27

  • Last modified date

    2012-10-01

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

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

    UK81340

Modules/Macros

  • DSNIBWAC DSNIGWAC
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK81340

       UP12/09/12 P F209

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:
01 October 2012