Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

DDLIN data set restrictions and considerations

When you use a DDLIN data set to rebalance partitions, REORG PLUS does not explicitly execute the SQL statements. Instead, REORG PLUS extracts the partition number and the associated limit key values from the statements. REORG PLUS reorganizes the data in the partitions based on the new key values and alters the limit keys during the UTILTERM phase, thus rebalancing the data in the partitions.

The following restrictions and considerations apply to using a DDLIN data set to rebalance partitions:

Restrictions

  • REORG PLUS terminates when any of the following conditions exists:

    • You are reorganizing a table space that contains an archive-enabled table.

    • You are running a DSNUTILB reorganization.

  • The DDLIN data set should contain only an SQL ALTER INDEX statement or, for table-controlled partitioning, an ALTER TABLE statement for each limit key that you want to change. REORG PLUS ignores ALTER statements that do not apply to the current reorganization. Thus, you can use a single DDLIN data set for multiple jobs. For more information about this data set, see DDLIN data sets in REORG PLUS.

  • REORG PLUS ignores the Db2 subsystem parameter PREVENT_ALTERTB_LIMITKEY for index-controlled partitioned objects.

  • If the limit key values are altered, Db2 invalidates any plans and packages that are associated with the altered objects. If the value of the DB2 ZPARM AUTO BIND is YES or COEXIST, Db2 rebinds the plans and packages automatically the next time that they are executed. If the value of AUTO BIND is NO, you must rebind the plans and packages before your applications can access the altered objects.

Additional considerations

  • If the DDLIN data set contains an alter limit key value that is equal to the existing limit key value, REORG PLUS performs the reorganization, but no rebalancing is required and no ALTER is performed for that partition.

  • When you use a DDLIN data set to rebalance partitions, and also use dynamic allocation of SYSREC data sets during partition rebalancing, REORG PLUS cannot predict how much data movement will occur between rebalanced partitions. Therefore, REORG PLUS might inadequately size the SYSREC for a partition that has a large amount of data rebalanced into it. Also, when a table space has a non-unique partitioning key, REORG PLUS might not evenly distribute rows across the partitions. In these situations, BMC recommends that you code the required SYSRECnn DD statements for these types of partitions in the JCL. Continue to allow REORG PLUS to dynamically allocate all other SYSRECnn data sets.

  • When processing a DDLIN data set, REORG PLUS echoes all of the statements in the data set to SYSPRINT and issues a message for each statement that it will process. For sample SYSPRINT output, see Sample ALTER INDEX statements and resulting messages and Sample ALTER TABLE statements and resulting messages.

  • You can use a previously created DDLOUT data set as DDLIN input. For more information about this data set, see DDLOUT data sets in REORG PLUS.

Was this page helpful? Yes No Submitting... Thank you

Comments