Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• CREATE TABLE and SQLRULES(STD) to have DB2 generate the table
  spaces, LOB tables spaces and indexes for their tables. When
  DB2 generates the table spaces and index spaces, it uses the
  default PRIQTY and SECQTY values. In some cases, this is not
  adequate. The number of allowable dataset extents is reached
  and the customer cannot insert any more data into the table.
  This is of particular concern for LOB table spaces since REORG
  of a LOB table space does not reclaim space so altering the
  SEQTY does not provide relief after all the extents have been
  used.
  Two new ZParms are added, TSQTY and IXQTY. TSQTY specifies the
  default PRIQTY and SECQTY for table spaces and IXQTY specifies
  the default PRIQTY and SECQTY for index spaces. If neither
  PRIQTY or SECQTY is specified (as would be the case for
  default table spaces and index spaces created by DB2) then the
  default values specified by the ZParms are used.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 users.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: This is an enhancement to DB2 to        *
  *                      support customizable size defaults for  *
  *                      DB2-defined datasets. DCR DG337.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During CREATE TABLE processing, if CURRENT RULE = 'STD' and the
  user did not specified a tablespace to use, DB2 implicitly
  generates a tablespace.  However, DB2 uses the default PRIQTY
  and SECQTY values for this implicitly generated tablespace. In
  some cases, this is not adequate. The number of allowable
  dataset extents is reached and the customer cannot insert any
  more data into the table. Indentical case for indexes and
  indexspaces. This is of particular concern for LOB tablesapces
  since REORG of a LOB tablespace does not reclaim space so
  altering the SECQTY does not provide relief after all the
  extents have been used.
  

Problem conclusion

Temporary fix

Comments

• DB2 has been modified to use the ZParm's new parameters TSQTY
  and IXQTY for the appropriate case. DB2 function is not altered
  and will function the same as before if the ZParm is not rebuild
  to use the new feature.
  
  Additional Keywords: SQLCREATE
  
  Version 6 ++HOLD
  
  This APAR is for an enhancement in DB2. This section is only
  applicable to users who want to use this new feature. In order
  to use the new feature, the zparms must be rebuild correctly.
  The following is instruction on how to rebuild the zparm.
  ***Action for PQ53067 (release 610):
  
  This PTF adds the TSQTY and IXQTY keywords to DSNTIJUZ, the job
  that assembles and link edits the DSNZPxxx load module.
  - TSQTY specifies the default PRIQTY and SECQTY values in kilo-
    bytes to be allocated for the DB2-defined data set for a table
    space that is being created without the USING clause.
  - IXQTY specifies the default PRIQTY and SECQTY values in kilo-
    bytes to be allocated for the DB2-defined data set for an
    index space that is being created without the USING clause.
  The default value for TSQTY and IXQTY is zero, which indicates
  that the PRIQTY and SECQTY values are determined by DB2 in the
  "traditional" manner (see the SQL Reference for details).
  
  IF YOU HAVE ALREADY INSTALLED DB2 VERSION 6:
  
  After applying this PTF, you need to perform the following
  actions:
  (1) Update your customized CLIST library:
      * This PTF changes the DSNTINST CLIST in the prefix.SDSNCLST
        data set.  You need to redo any record format changes
        and reapply any tailoring you have done to your copy of
        this CLIST. You may also want to move this CLIST to the
        prefix.NEW.SDSNCLST data set, where the CLISTs processed
        by job DSNTIJVC reside.
  (2) Update your system parameter (DSNZPxxx) load module:
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for table spaces that are created without the
        USING clause, you need to add the keyword TSQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for index spaces that are created without the
        USING clause, you need to add the keyword IXQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * Run the first two steps of the DSNTIJUZ job you modified,
        to assemble and link the load module.
      * After the job completes, you must stop and start DB2 for
        the changes to take effect
  
  IF YOU APPLY THIS APAR BEFORE INSTALLING DB2 VERSION 6:
  
  The TSQTY and IXQTY parameters, each set to the default of 0,
  will be included in the invocation of the DSN6SPRM macro in your
  customized version of job DSNTIJUZ after you have run the CLIST.
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for table spaces that are created without the
        USING clause, you need to add the keyword TSQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for index spaces that are created without the
        USING clause, you need to add the keyword IXQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * Run DSNTIJUZ as specified in the Installation Guide.
  
  
  
  Verson 7 ++HOLD
  
  This APAR is for an enhancement in DB2. This section is only
  applicable to users who want to use this new feature. In order
  to use the new feature, the zparms must be rebuild correctly.
  The following is instruction on how to rebuild the zparm.
  ***Action for PQ53067 (release 710):
  
  This PTF adds the TSQTY and IXQTY keywords to DSNTIJUZ, the job
  that assembles and link edits the DSNZPxxx load module.
  - TSQTY specifies the default PRIQTY and SECQTY values in kilo-
    bytes to be allocated for the DB2-defined data set for a table
    space that is being created without the USING clause.
  - IXQTY specifies the default PRIQTY and SECQTY values in kilo-
    bytes to be allocated for the DB2-defined data set for an
    index space that is being created without the USING clause.
  The default value for TSQTY and IXQTY is zero, which indicates
  that the PRIQTY and SECQTY values are determined by DB2 in the
  "traditional" manner (see the SQL Reference for details).
  
  IF YOU HAVE ALREADY INSTALLED DB2 VERSION 7:
  
  After applying this PTF, you need to perform the following
  actions:
  (1) Update your customized CLIST library:
      * This PTF changes the DSNTINST CLIST in the prefix.SDSNCLST
        data set.  You need to redo any record format changes
        and reapply any tailoring you have done to your copy of
        this CLIST. You may also want to move this CLIST to the
        prefix.NEW.SDSNCLST data set, where the CLISTs processed
        by job DSNTIJVC reside.
  (2) Update your system parameter (DSNZPxxx) load module:
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for table spaces that are created without the
        USING clause, you need to add the keyword TSQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for index spaces that are created without the
        USING clause, you need to add the keyword IXQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * Run the first two steps of the DSNTIJUZ job you modified,
        to assemble and link the load module.
      * After the job completes, you must either use the SET
        SYSPARM command or stop and start DB2 for the changes
        to take effect.
  
  
  IF YOU APPLY THIS APAR BEFORE INSTALLING DB2 VERSION 7:
  
  The TSQTY and IXQTY parameters, each set to the default of 0,
  will be included in the invocation of the DSN6SPRM macro in your
  customized version of job DSNTIJUZ after you have run the CLIST.
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for table spaces that are created without the
        USING clause, you need to add the keyword TSQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * If you want to override the DB2 default value used for
        primary and secondary space allocation for DB2-defined
        data sets for index spaces that are created without the
        USING clause, you need to add the keyword IXQTY=x, where
        x is an integer ranging from 1 to 4194304 (kilobytes), to
        the invocation of the DSN6SYSP macro in your customized
        version of the installation job DSNTIJUZ.  Make sure to
        add a continuation character in column 72 if needed.
      * Run DSNTIJUZ as specified in the Installation Guide.
  

APAR Information

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

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

  UQ75033 UQ75034 UQ75035

Modules/Macros

•    DSN@ZP   DSNDQWPZ DSNDSYSP DSNTIJUZ DSNTINST
  DSNWZP   DSNXICTS DSNXICX2 DSNXNUM  DSN6SYSP
  

Fix information

• Fixed component name

  5740 IBM DATABA

• Fixed component ID

  5740XYR00

Applicable component levels

• R610 PSY UQ75033

     UP03/04/01 P F304

• R710 PSY UQ75035

     UP03/04/01 P F303

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.

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Product categories:

Software

Data Management

Data Servers (Database Management Systems)

DB2 for z/OS

Software version:

610

Reference #:

PQ53067

IBM Group:

Software Group

Modified date:

2003-05-03