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

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.
  
  Additional Information:
  Once the PTF of PH26317 is applied where the
  UTILITY_OBJECT_CONVERSION subsystem parameter is removed with an
  internal enforcement of NOBASIC, existing LOAD, REORG, and
  REBUILD INDEX utility execution with the RBALRSN_CONVERISON
  BASIC keyword specification would fail with a RC8 and message
  DSNU1145I issued. While this is existing behavior before PH26317
  is applied when the UTILITY_OBJECT_CONVERSION subsystem
  parameter is set to NOBASIC, customers would observe this
  behavioral change if they currently set
  UTILITY_OBJECT_CONVERSION different from NOBASIC before applying
  this PTF. It is recommended that they remove the
  RBALRSN_CONVERSION keyword specification to resolve this
  behavioral change to enable Db2 Utilities to convert the target
  objects to extended page format whenever possible.
  

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.
  ×**** PE21/07/29 PTF IN ERROR. SEE APAR PH30562  FOR DESCRIPTION
  

APAR Information

• 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