PH24358: DB2 12 ZPARM SIMPLIFICATION ENHANCEMENTS, CONTINUED: REMOVE COMPRESS_SPT01 AND SPT01_INLINE_LENGTH

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This is the second APAR (following PH21370) for E491, Db2 12
  zPARM simplification
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the following Db2 subsystem                     *
  * parameters are affected by this change:                      *
  * - COMPRESS_SPT01                                             *
  * - SPT01_INLINE_LENGTH                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * This APAR removes the COMPRESS_SPT01                         *
  * and SPT01_INLINE_LENGTH subsystem                            *
  * parameters from Db2 12.                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  COMPRESS_SPT01 and SPT01_INLINE_LENGTH provide for configuring
  the Db2 SPT01 directory table.
  .
  COMPRESS_SPT01 specifies whether the SPT01 directory table
  space is to be compressed.  Currently, compression of SPT01 is
  disabled by default.  However, compression is low cost and is
  good practice for scalability.
  .
  SPT01_INLINE_LENGTH specifies the maximum length of LOB column
  data in the SPT01 directory table space that is to be
  maintained in the base table.  Currently, the maximum length
  of 32138 is used by default because maximizing inline LOB
  data is good practice for performance.
  

Problem conclusion

Temporary fix

Comments

• To encourage best practices for SPT01 configuration, this
  APAR removes COMPRESS_SPT01 and SPT01_INLINE_LENGTH from
  Db2 12. When the fixing PTF is applied, Db2 always
  compresses SPT01 and always uses 32138 as the inline LOB
  length.
  -------------------------------------------------------------
  Pre-APPLY guidance for customers who currently set
  COMPRESS_SPT01 to NO:
  -------------------------------------------------------------
  If you currently set COMPRESS_SPT01 to NO on Db2 12, be
  aware that the SPT01 base table space will be compressed the
  next time you run the REORG TABLESPACE utility on SPT01 on
  any subsystem or data sharing member where the PTF is
  applied.
  If you currently set COMPRESS_SPT01 to NO on Db2 11,
  including members in data sharing coexistence with Db2 12,
  be aware that the SPT01 base table space will be compressed
  the first time you run the REORG TABLESPACE utility on SPT01
  on any subsystem or data sharing member that you have
  migrated to Db2 12 with the PTF applied.
  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 switch to using COMPRESS_SPT01=YES (on all
  members in data sharing), then optionally execute the REORG
  TABLESPACE utility on SPT01 to compress it.
  -------------------------------------------------------------
  Pre-APPLY guidance for customers who currently set
  SPT01_INLINE_LENGTH to less than 32138:
  -------------------------------------------------------------
  If you currently set SPT01_INLINE_LENGTH to a value less
  than 32138 on Db2 12, be aware that SPT01 will be placed in
  REORG-pending (AREOR) advisory status the next time you run
  the -SET SYSPARM command on any subsystem or data sharing
  member where the PTF is applied.
  If you currently set SPT01_INLINE_LENGTH to a value less
  than 32138 on Db2 11, including members in data sharing
  coexistence with Db2 12, be aware that SPT01 will be placed
  in REORG-pending (AREOR) advisory status the first time
  you run the -SET SYSPARM command on any subsystem or data
  sharing member that you have migrated to Db2 12 with
  the PTF applied.
  In AREOR status, SPT01 is not restricted and can be accessed
  by both readers and writers.  However, the modification does
  not take effect until you run the REORG TABLESPACE utility
  on SPT01 to materialize the definition changes.
  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 switch to SPT01_INLINE_LENGTH=32138 (on all
  members in data sharing).  Do not run the -SET SYSPARM
  command on any member until you have switched all members
  to use SPT01_INLINE_LENGTH=32138.  After switching (all
  members) to SPT01_INLINE_LENGTH=32138, run the -SET SYSPARM
  command to initiate the change and place SPT01 in AREOR
  status. Then run the REORG TABLESPACE utility on SPT01 to
  materialize the definition changes and clear the AREOR
  status.
  

APAR Information

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

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

  UI69863

Modules/Macros

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

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI69863

     UP20/06/10 P F006

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.