IBM Support

PH26317: DB2 12 ZPARM SIMPLIFICATION ENHANCEMENTS, CONTINUED: REMOVE OBJECT_CREATE_FORMAT AND UTILITY_OBJECT_CONVERSION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • This is the third APAR (following PH21370 and PH24358) for
    E491,Db2 12 zPARM simplification
    
    Note:
    Tables in a clone table relationship are not automatically
    converted to extended RBA/LRSN format by REBUILD INDEX, REORG
    INDEX, REORG TABLESPACE, or LOAD REPLACE utility execution. As
    a result, these utilities can fail if the format conversion is
    required for tables in clone table relationships. You can apply
    APAR PH30562 to prevent the utilities from failing. However, to
    convert the objects in clone table relationships to extended
    format, you must manually DROP the clone, convert the base
    table, and recreate the clone.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Db2 12 for z/OS users, and Db2 11 for                        *
    * z/OS users who are migrating to Db2 12,                      *
    * who are using any of the following Db2                       *
    * subsystem parameters are affected by this                    *
    * change:                                                      *
    * - DSN6SPRM.OBJECT_CREATE_FORMAT                              *
    * - DSN6SPRM.UTILITY_OBJECT_CONVERSION                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * This APAR removes the                                        *
    * OBJECT_CREATE_FORMAT                                         *
    * and UTILITY_OBJECT_CONVERSION                                *
    * subsystem parameters from Db2 12.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    OBJECT_CREATE_FORMAT and UTILITY_OBJECT_CONVERSION have been
    identified as obsolete or rarely used.
    OBJECT_CREATE_FORMAT specifies whether Db2 is to create new
    table spaces and indexes to use a basic or extended log record
    format. Currently, Db2 12 operates as it is set to
    EXTENDED, the current default setting.
    UTILITY_OBJECT_CONVERSION specifies whether Db2 utilities that
    accept the RBALRSN_CONVERSION option will convert existing
    table spaces and indexes to a 6-byte page format, to a
    10-byte page format, or perform no conversion. In Db2 12, the
    no conversion page format is used by default.
    Important: Tables in a clone table relationship are not
    automatically converted to extended RBA/LRSN format by
    REBUILD INDEX, REORG INDEX, REORG TABLESPACE, or LOAD REPLACE
    utility execution. As a result, these utilities can fail if
    the format conversion is required for tables in clone table
    relationships. You can apply APAR PH30562 to prevent the
    utilities from failing. However, to convert the objects in
    clone table relationships to extended format, you must
    manually DROP the clone, convert the base table, and
    recreate the clone.
    

Problem conclusion

Temporary fix

Comments

  • -------------------------------------------------------------
    To encourage best practices for Db2 zparms, this APAR
    removes OBJECT_CREATE_FORMAT and UTILITY_OBJECT_CONVERSION
    from Db2 12. When the fixing PTF is activated, Db2 always
    creates new table spaces and indexes to use an extended log
    record format and Db2 utilities that accept the
    RBALRSN_CONVERSION option always convert existing table
    spaces and indexes having the traditional 6-byte page
    (BASIC) format to the 10-byte page (EXTENDED) format.
    -------------------------------------------------------------
    Pre-APPLY guidance for customers who currently set
    OBJECT_CREATE_FORMAT different from EXTENDED:
    -------------------------------------------------------------
    If you currently set OBJECT_CREATE_FORMAT different from
    EXTENDED on Db2 12, be aware that any Db2 subsystem or
    data sharing member where this PTF is activated, Db2 will
    always create new table spaces and indexes to use an
    extended log record format.
    Activating the PTF on a Db2 subsystem or data sharing
    member means that you have:
    - applied it there; and then
    - rebuilt the Db2 subsystem parameter (DSNZPxxx) module;
      and then
    - either restarted Db2 or run the -SET SYSPARM LOAD or
      RELOAD command with the rebuilt subsystem parameter
      (DSNZPxxx) module
    If you currently set OBJECT_CREATE_FORMAT different from
    EXTENDED on Db2 11, including members in data sharing
    coexistence with Db2 12, be aware that Db2 will always
    create new table spaces and indexes to use an extended
    log record format on any Db2 subsystem or data sharing
    member that you have migrated to Db2 12 where this PTF
    is activated.
    Therefore, before you either :
    - apply the fixing PTF for this APAR on a Db2 12 subsystem
      (or any member of a Db2 12 data sharing group); or
    - migrate a Db2 11 subsystem (or any member of a Db2 11 data
      sharing group) to Db2 12 with this PTF applied
    you need to rebuild its Db2 subsystem parameter (DSNZPxxx)
    module to use OBJECT_CREATE_FORMAT=EXTENDED (on all members
    in data sharing). Do not run the -SET SYSPARM or restart Db2
    command on any member until you have switched all members
    to use OBJECT_CREATE_FORMAT=EXTENDED. After switching
    (all members) to OBJECT_CREATE_FORMAT=EXTENDED, run (on all
    members in data sharing) the -SET SYSPARM command or restart
    Db2 to initiate the change.
    -------------------------------------------------------------
    Pre-APPLY guidance for customers who currently set
    UTILITY_OBJECT_CONVERSION different from NOBASIC:
    -------------------------------------------------------------
    If you currently set UTILITY_OBJECT_CONVERSION different
    from NOBASIC on Db2 12, be aware that any Db2 subsystem
    or data sharing member where this PTF is activated, Db2
    utilities that accept the RBALRSN_CONVERSION option will
    always convert existing table spaces and indexes having
    the traditional 6-byte page (BASIC) format to the 10-byte
    page (EXTENDED) format.
    Activating the PTF on a Db2 subsystem or data sharing
    member means that you have:
    - applied it there; and then
    - rebuilt the Db2 subsystem parameter (DSNZPxxx) module;
      and then
    - either restarted Db2 or run the -SET SYSPARM LOAD or
      RELOAD command with the rebuilt subsystem parameter
      (DSNZPxxx) module.
    If you currently set UTILITY_OBJECT_CONVERSION different
    from NOBASIC on Db2 11, including members in data sharing
    coexistence with Db2 12, be aware that Db2 utilities that
    accept the RBALRSN_CONVERSION option will always
    convert existing table spaces and indexes having the
    traditional 6-byte page (BASIC) format to the 10-byte page
    (EXTENDED) format on any Db2 subsystem or data sharing
    member that you have migrated to Db2 12 where this PTF
    is activated.
    Therefore, before you either :
    - apply the fixing PTF for this APAR on a Db2 12 subsystem
      (or any member of a Db2 12 data sharing group); or
    - migrate a Db2 11 subsystem (or any member of a Db2 11 data
      sharing group) to Db2 12 with this PTF applied
    you need to rebuild its Db2 subsystem parameter (DSNZPxxx)
    module to use UTILITY_OBJECT_CONVERSION=NOBASIC (on all
    members in data sharing). Do not run the -SET SYSPARM
    command or restart Db2 on any member until you have switched
    all members to use UTILITY_OBJECT_CONVERSION=NOBASIC.
    After switching(all members) to
    UTILITY_OBJECT_CONVERSION=NOBASIC, run (on all members in
    data sharing) the -SET SYSPARM command or restart Db2 to
    initiate the change.
    

APAR Information

  • APAR number

    PH26317

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-10

  • Closed date

    2020-07-24

  • Last modified date

    2021-01-13

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

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

    UI70750

Modules/Macros

  • DSNTINMF DSNDQWPZ DSNTIP7  DSNWZIFC DSNTIDXA DSNTIVMD DSNTIJUZ
    DSNTINST DSNTIDXC DSNTIWIA DSNTIDXB DSNTIVIA DSNTIWMD DSNTIWIE
    DSNTIVIE DSNFUDRD DSN@XAZP DSN6SPRM DSNTXAZP DSNTIWPC DSNDSPRM
    DSN6SPRC DSNFUDIR DSNTIVMN DSNTIWMN DSNTIVAF DSNTIVIN DSNTIWMS
    DSNUMSGD DSNTIVMS DSNTIWAF DSNTIWIN
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI70750

       UP20/08/01 P F007

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"12.0"}]

Document Information

Modified date:
14 January 2021