Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see REORG PLUS for DB2 13.1.

Descriptions of basic installation options

This topic describes each of the basic installation options.

For more information about setting the values of some of these options at runtime, see Syntax-of-the-REORG-command.

ALTRFAIL (obsolete)

In REORG PLUS version 11.1 and earlier, the ALTRFAIL option specified the action that REORG PLUS took when a failure occurred during the processing of limit-key updates. This option applied to limit-key updates that were processed either from a DDLIN data set or as a result of the REBALANCE option, and applied only to a SHRLEVEL REFERENCE or SHRLEVEL CHANGE reorganization.

Beginning with REORG PLUS version 11.2, if a failure occurs when processing limit key updates, REORG PLUS functions as described in General-rebalancing-considerations.

ANALMAX=*

The ANALMAX option indicates the maximum number of tasks to start for the ANALYZE phase. You can use any of the following values:

  • 0 tells REORG PLUS to determine the number of tasks to start.
  • An asterisk (*) tells REORG PLUS to use the TASKMAX value.
  • n tells REORG PLUS to start a maximum of n tasks (where n is a positive integer from 1 through 32767).
  • n% tells REORG PLUS that the maximum number of tasks that it can start is n% of the number of CPUs on the system (where n is a positive integer from 1 through 32768).

For more information about using the multitasking options, see Multitasking installation options.

ARC=NO

This option applies to SHRLEVEL CHANGE only.

The ARC option tells REORG PLUS whether to use the APPLICATION RESTART Control (AR/CTL) interface. You can specify one of the following values:

  • NO tells REORG PLUS not to use the AR/CTL interface.
  • YES tell REORG PLUS to use the AR/CTL suspend-and-resume interface. Batch applications using the AR/CTL product and this interface will experience no outage for the Db2 objects that you are reorganizing.

ARCHDDN=SYSARC

This option applies to table space reorganizations only.

The ARCHDDN option specifies the default ddname for the archive data set. This data set contains the rows that REORG PLUS discards during a table space reorganization as a result of the following:

  • A SELECT or DELETE operation
  • Rebalance of a table space where the last partition key has been altered and the table space is defined in one of the following ways:
    • LARGE (either by definition or default)
    • Defined with DSSIZE
    • Range-partitioned

If you change the default ddnames that BMC supplied, you must also change the names in your JCL. For information about specifying and using this data set, see SYSARC-data-sets-in-REORG-PLUS.

DSNUTILB reorganization jobs

When invoking DSNUTILB, REORG PLUS uses this option only to pass a value for the &DDNAME variable for the data set name pattern. REORG PLUS includes this information in the TEMPLATE control statement that it builds for the IBM Db2 REORG utility.

Overriding this option

You can override the value for this option by using the ARCHDDN command option.

ARCHFORMAT=BMC

This option applies to table space reorganizations only.

The ARCHFORMAT option specifies the format of your archive data set (SYSARC). For more information about the SYSARC data set, see SYSARC-data-sets-in-REORG-PLUS.

Specify one of the following options:

  • BMC tells REORG PLUS to produce the archive data set in BMC internal format. You can reload the rows from the archive data set in this format by using the FORMAT BMC option of LOADPLUS. An archive data set produced with ARCHFORMAT BMC uses less space than one produced with ARCHFORMAT Db2.
  • Db2 tells REORG PLUS to produce the archive data set in the same format as the IBM Db2 REORG utility produces when you specify UNLOAD ONLY. You can reload the rows from the archive data set in this format by using the FORMAT UNLOAD option of either LOADPLUS or the IBM Db2 LOAD utility.

Overriding this option

You can override the value for this option by using the ARCHFORMAT command option.

AUXREORG (obsolete)

In REORG PLUS version 10.2 and earlier, the AUXREORG option specified whether to reorganize (by invoking DSNUTILB) associated LOB table spaces while reorganizing the base table space.

Beginning with REORG PLUS version 11.1, you must specify the AUX command to reorganize the base table space and LOB table spaces in the same reorganization. For more information about the AUX command, see AUX.

AVAILPAGEPCT=100

The AVAILPAGEPCT option controls virtual storage above the 16-MB line that REORG PLUS allocates to BMCSORT for concurrent sort processing. AVAILPAGEPCT specifies the maximum percentage of available memory, in 4-KB pages in the system, that REORG PLUS can allocate. You can specify any integer from 0 through 100.

Note

REORG PLUS defines available pages as pages that have not been used. Total pages (which you can control with the TOTALPAGEPCT option), are pages that are underutilized and are available for use.

  • A value of 0 tells REORG PLUS to ignore the number of available pages when allocating sort memory.
  • A value of 1 through 100 tells REORG PLUS to use up to the specified percentage of available pages when allocating sort memory. For example, AVAILPAGEPCT 50 tells REORG PLUS to use no more than 50 percent of the available pages.

Additional considerations

The following additional information applies to the AVAILPAGEPCT option:

  • Because available pages are rarely subject to system paging, changing this value will have a minimal effect, if any, on system performance.
  • When you specify values greater than 0 for both AVAILPAGEPCT and TOTALPAGEPCT, REORG PLUS uses the lesser of the two calculated results as the maximum amount of memory for sort processing.
  • If REORG PLUS is unable to perform an optimal sort due to an insufficient number of available pages that it is enabled to allocate, the SHORTMEMORY option controls the action that REORG PLUS takes.
  • When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the AVAILPAGEPCT command option.

BILDMAX=300%

The BILDMAX option indicates the maximum number of tasks to start for the index build process. You can specify any of the following values:

  • 0 tells REORG PLUS to determine the number of tasks to start.
  • An asterisk (*) tells REORG PLUS to use the TASKMAX value.
  • n tells REORG PLUS to start a maximum of n tasks (where n is a positive integer from 1 through 32767).
  • n% tells REORG PLUS that the maximum number of tasks that it can start is n% of the number of CPUs on the system (where n is a positive integer from 1 through 32768).

Regardless of the value that you specify, REORG PLUS will not start more than 16 tasks for this phase.

Note

For REORG PLUS to use BILDMAX, you must specify SMAX=0, and either not use MAXSORTS or specify MAXSORTS 0.

For information about using the multitasking options, see Multitasking installation options.

BMCHIST=YES

The BMCHIST option enables you to choose whether to insert a utility history row into the BMC Software BMCHIST table when the reorganization successfully completes. REORG PLUS updates the BMCHIST table in the UTILTERM phase.

  • YES tells REORG PLUS to perform the insert.
  • NO tells REORG PLUS to bypass the insert.

You can use the TERMEXIT option and user exit to dynamically control the processing of updates to BMCHIST, BMCSTATS, real-time statistics, and UPDATEDB2STATS at execution time. See the TERMEXIT option for more information. For information about the TERMEXIT user exit, see Using-TERMEXIT-to-control-BMCHIST-and-statistics-updates.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the BMCHIST command option.

CBUFFS=30

The CBUFFS option specifies a multiple of 32 KB to use to define the amount of buffer pool storage that is allocated for each copy data set (full and incremental). If you are making multiple copies, the same set of buffers is used, not an additional set. For more information, see Copy data sets.

CONDEXEC=NO

The CONDEXEC option specifies whether REORG PLUS should consider performing a conditional reorganization. For a description of how the installation and command options interact, see Conditional-reorganization. For more information about conditional execution using the DASD MANAGER PLUS tables, see Conditional-reorganizations-using-the-DASD-MANAGER-PLUS-exceptions-table.

Valid values are YES, NO, and BMC:

  • NO tells REORG PLUS to ignore the limit installation options (OFFPOSLM, INDREFLM, and LEAFDSLM) and perform the reorganization unless you override this option with the CONDEXEC or limit command options.
  • YES tells REORG PLUS to examine the values of the limit command options (if specified) and the limit installation options in conjunction with the values in the Db2 catalog to determine whether to perform the reorganization and to issue a report with the information.
  • BMC tells REORG PLUS to issue a report and reorganize the object of the current job if an exception for the object exists in the DASD MANAGER PLUS exceptions table. REORG PLUS issues one of the following return codes after examining the DASD MANAGER PLUS exceptions table:
    • 1, which indicates that no calculated value exceeded an exception value. REORG PLUS does not perform a reorganization.
    • 2, which indicates that a calculated value exceeded an exception value. REORG PLUS performs a reorganization. If REORG PLUS issues any return code greater than 2 during processing, that return code supersedes return code 2.

Restrictions

The following restrictions apply to CONDEXEC:

  • CONDEXEC=BMC is available only if you are using REORG PLUS as a component of the BMC AMI Performance or Database Performance for DB2 solution.
  • If CONDEXEC=BMC or CONDEXEC=YES is in effect, REORG PLUS terminates if you are reorganizing a LOB table space.

Additional considerations

The following additional considerations apply to CONDEXEC:

  • When invoking DSNUTILB, REORG PLUS ignores CONDEXEC=BMC.
  • To obtain the report that recommends objects for reorganization without performing any reorganizations, specify REPORTONLY in the command.

Overriding this option

You can override the value for this option by using the CONDEXEC command option.

COPYDDN=(BCPY, BCPZ)

The COPYDDN option specifies default ddnames or ddname prefixes for the local copy data sets that receive an image copy or DSN1COPY-type copy of the table space or partitions that you are reorganizing. If you are registering the copies, the first name is the local primary, and the second name is the local backup.

When using this name as a prefix for a ddname for a partitioned table space, ensure that you allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). In addition, if you change the default ddnames that BMC supplied, you must also change the names in your JCL. For more information, see Copy data sets.

When invoking DSNUTILB, REORG PLUS passes this option to the IBM Db2 REORG utility for processing.

Overriding this option

You can override the value for this option by using the COPYDDN command option.

COPYLVL=PART

The COPYLVL option specifies how REORG PLUS is to assign copy data sets when reorganizing partitioned data sets. You can specify one of the following values:

  • COPYLVL=PART tells REORG PLUS to allocate individual full copy data sets and incremental copy data sets (if created) for each partition that you are reorganizing. If you also specify a tape device for the UNIT option, REORG PLUS allocates a tape unit for each partition.

    REORG PLUS appends the partition number to the ddname prefixes that you specify in the COPYDDN, ICDDN, RCVYDDN, and RCVICDDN options. The values that you specify for these options plus the highest partition number must not exceed eight characters.

    When invoking DSNUTILB, REORG PLUS changes COPYLVL PART to COPYLVL FULL when you specify COPY YES.

  • COPYLVL=FULL tells REORG PLUS to assign a single full copy data set to contain all of the partitions that you are reorganizing in either of the following cases:

    • You are reorganizing all partitions.
    • You are reorganizing a subset of contiguous partitions (specified on the PART command option) and you specify a value of YES for the COPYSUBSET installation option.

    If incremental copy data sets are created, REORG PLUS also allocates a single incremental copy data set to contain all of the partitions that you are reorganizing.

Additional considerations

The following considerations apply to the COPYLVL option:

  • If you change ICTYPE in the options module to UPDATE, leave the COPYLVL installation option set to FULL, and do not specify either option on the command, REORG PLUS changes COPYLVL to PART to prevent the job from terminating.
  • If you anticipate reorganizing a large number of partitions, consider specifying COPYLVL FULL.

Overriding this option

You can override the value for this option by using the COPYLVL command option.

COPYMAX=*

The COPYMAX option indicates the maximum number of tasks to start during the image copy process. You can specify any of the following values:

  • 0 to have REORG PLUS determine the number of tasks to start
  • Asterisk (*) to use the TASKMAX value
  • n to specify that REORG PLUS can start a maximum of n tasks (where n is a positive integer from 1 through 32767)
  • n% to specify that the maximum number of tasks that REORG PLUS can start is n% of the number of CPUs on the system (where n is a positive integer from 1 through 32768)

For information about using the multitasking options, see Multitasking installation options.

COPYSUBSET=NO

The COPYSUBSET option tells REORG PLUS whether to use a single copy data set for a subset of partitions.

COPYSUBSET=NO does not allow this single copy data set. If COPYLVL FULL is in effect in this case, REORG PLUS changes it to COPYLVL PART.

COPYSUBSET=YES enables a single copy data set. You must also meet the following requirements:

  • Specify a single subset of physically contiguous partitions with the PART command option.
  • For the primary local image copy, either activate dynamic allocation or allocate a single copy data set in your JCL.
  • If you dynamically allocate your copy data sets, specify FULL for the COPYLVL installation or command option.

CPYRFAIL=TERM

This option applies to the UTILTERM phase of a SHRLEVEL REFERENCE or SHRLEVEL CHANGE reorganization only.

The CPYRFAIL option specifies the action that REORG PLUS takes if the image copies cannot be registered in SYSIBM.SYSCOPY:

  • CPYRFAIL=TERM tells REORG PLUS to terminate and back out the renames, if necessary so that the original data sets are restored. The condition of your objects is the same as if the reorganization had never run.

    REORG PLUS changes TERM to COPYPEND when any of the following conditions exist:

    • Pending definition changes exist on the object and REORG PLUS can materialize those changes
    • You are rebalancing partitions (using either the REBALANCE option or a DDLIN data set)

  • CPYRFAIL=COPYPEND tells REORG PLUS to leave the newly reorganized data sets in use, but set the COPY (copy pending) status and end with RC=4.

    REORG PLUS changes COPYPEND to TERM and continues terminating the job when you are reorganizing a catalog object. This value change ensures that REORG PLUS can return the table space to its original state.

DATACAP=NO

This option applies to SHRLEVEL CHANGE only.

The DATACAP option determines whether REORG PLUS turns on the Data Capture Changes flag.

  • NO tells REORG PLUS not to turn on the Data Capture Changes flag. Using DATACAP= NO decreases the possibility that contention will occur between REORG PLUS and the user’s application. Therefore, BMC recommends that you always use NO as the value for the DATACAP option.

  • YES tells REORG PLUS to turn on the Data Capture Changes flag when you are performing a table space or index space reorganization and any one of the table space partitions is compressed.

    If you specify YES and do not specify KEEPDICTIONARY, you can improve performance. However, these settings increase the possibility that contention will occur between REORG PLUS and the user’s application.

DDLDDN=DDLIN

The DDLDDN option allows you to specify the default ddname of the DDLIN data set. For information about using a DDLIN data set in your REORG PLUS jobs, see page DDLIN data sets.

Overriding this option

You can also specify the DDLIN data set name by using the DDLDDN command option.

DEADLINE=NONE

This option applies to SHRLEVEL CHANGE only.

The DEADLINE option specifies the time by which the LOGFINAL phase should finish applying log records. You can specify NONE or a time:

  • NONE indicates no deadline.
  • You can specify a time in hh:mm:ss format as the deadline, using a 24-hour clock. REORG PLUS replaces the time portion of the current system timestamp with the specified time to create a new timestamp. If the calculated timestamp time has already passed, REORG PLUS updates the date to the next day. Then, it uses this new timestamp to determine when the LOGFINAL phase should stop applying log records.

Additional considerations

The following considerations apply to the DEADLINE option:

  • If REORG PLUS calculates timestamps for LOGFINAL and DEADLINE, the DEADLINE timestamp must be later than the LOGFINAL timestamp.
  • You can use the XBM Utility Monitor function or the MVS operator console to dynamically change the DEADLINE values while the reorganization is in progress.
  • The DEADLINE option interacts with other options to control the log apply process. For information, see Controlling-the-log-apply-process.

Overriding this option

You can override the value for this option by using the DEADLINE command option.

DELAY=1200

This option applies to SHRLEVEL CHANGE only.

The DELAY option specifies the number of seconds, as a positive integer (0 or greater), that are to elapse from the time REORG PLUS detects a longlog condition until the time it performs the action specified on the LONGLOG option. If the longlog condition no longer exists at the end of the time period specified by DELAY, the DELAY value is reset.

During the window provided by the DELAY option, you can use the XBM Utility Monitor or the MVS operator console to terminate the reorganization or change the criteria that determines when LOGFINAL processing begins.

This option interacts with other options to control the log apply process. For information, see Controlling-the-log-apply-process.

Overriding this option

You can override the value for this option by using the DELAY command option.

DELFILES=YES

The DELFILES option tells REORG PLUS whether to delete your work files after the reorganization.

  • If you specify DELFILES=YES, the response from REORG PLUS depends on whether the reorganization completes successfully:
    • If a non-DSNUTILB reorganization completes successfully, DELFILES=YES tells REORG PLUS to delete all physical sequential data sets whose ddnames match the SYSREC, SYSUT1, and SORTWK ddnames or ddname prefixes.
    • For successful DSNUTILB reorganizations, REORG PLUS deletes the following data sets:
      • The SYSREC and SYSUT1 data sets that were used during the reorganization
      • All SYSREC, SYSUT1, and SORTWK data sets allocated in your JCL

    • If a non-DSNUTILB reorganization completes unsuccessfully, DELFILES=YES tells REORG PLUS to delete any unregistered full and incremental copy data sets (as well as the SYSREC, SYSUT1, and SORTWK data sets) when either of the following conditions exists:

      • You specify ON FAILURE phase TERMINATE UTILITY, where phase is UNLOAD, RELOAD, LOGAPPLY, or UTILTERM, and REORG PLUS terminates in the phase that you specified.
      • A drain timeout occurs and you specified TIMEOUT TERM as a command or installation option.

      In contrast, REORG PLUS does not delete the data sets if

      • You did not specify ON FAILURE or TIMEOUT TERM.
      • REORG PLUS ends with a STOP status.
    • If a DSNUTILB reorganization completes unsuccessfully, REORG PLUS does not perform DELETEFILES processing.
  • DELFILES=NO tells REORG PLUS not to delete any files after either a successful or unsuccessful reorganization.

If you are running the reorganization job in a worklist environment, REORG PLUS ignores the value that you set in the installation option and processes the job as if you had specified DELFILES=NO. REORG PLUS does this so that the data sets will exist for subsequent executions in the job. If you want to delete the data sets, you must specify DELETEFILES YES on the REORG command in the worklist.

Overriding this option

You can override the value for this option by using the DELETEFILES command option.

DESCCDE=(3,7)

The DESCCDE option specifies the descriptor codes to control how write-to-operator (WTO) messages are displayed on a console. You can specify up to six descriptor codes. The values (3,7) specify the eventual action required and retain the action message for life-of-task. REORG PLUS uses this option only for WTOs that require action.

For a complete listing of valid values, see the appropriate IBM reference manual.

DRAINTYP=ALL

This option applies to SHRLEVEL CHANGE only.

The DRAINTYP option determines the type of drain that REORG PLUS issues when it enters the LOGFINAL phase, after reaching the MAXRO threshold.

You can specify one of the following values:

  • ALL (the default) tells REORG PLUS to drain all readers and writers.

    BMC recommends DRAINTYP=ALL if either of the following conditions exists:

    • SQL queries might be running that do not commit often enough to allow a drain of the readers to complete successfully in a timely fashion.
    • SQL updaters might be running that require a minimum possible outage, and these updaters might time out if they are all held while awaiting the readers to be drained.
  • WRITERS tell REORG PLUS to drain only writers.

Overriding this option

You can override the value for this option by using the DRAIN command option.

DRNDELAY=1

After a drain times out, the DRNDELAY option specifies the minimum number of seconds that you want REORG PLUS to wait before it tries again to obtain the drain. The number of seconds can range from 1 through 1800.

Overriding this option

You can override the value for this option by using the RETRY_DELAY command option.

DRNRETRY=255

The DRNRETRY option specifies the maximum number of times to attempt to obtain a drain before terminating the job. The number of retry attempts can range from 0 through 255.

Overriding this option

You can override the value for this option by using the RETRY command option.

DRNWAIT=NONE

The DRNWAIT option specifies the drain timeout value to use. Specify one of the following values:

  • NONE, which means that the drain request issued by REORG PLUS times out immediately if the drain cannot acquire the lock

    NONE prevents any application transactions from being queued during the drain process. BMC recommends that you specify NONE in high-transaction environments.

  • UTIL, which tells REORG PLUS to use the standard Db2 utility timeout value defined in DSNZPARMs for your site (IRLMRWT multiplied by UTIMOUT)

    The wait time applies to each object involved in the reorganization.

  • SQL, which tells REORG PLUS to use the standard SQL timeout value (IRLMRWT) as the drain timeout value

    The wait time applies to each object involved in the reorganization.

  • Any integer value from 0 through 1800.
    • 0 is equivalent to the value UTIL.
    • 1 through 1800 specifies the number of seconds to wait to obtain the drain for each drain retry before timing out.

If REORG PLUS cannot drain all of the objects within the time period specified by DRNWAIT, REORG PLUS completes the following process:

  1. Releases the drains that it has obtained so far
  2. Waits the length of time that you specify in the DRNDELAY installation option (or RETRY_DELAY command option)
  3. Tries again to drain the objects for the number of times that you specify in the DRNRETRY installation option (or RETRY command option)

Note

The FORCE and FORCE_AT options tell REORG PLUS whether to cancel Db2 threads that might prevent a successful drain and, if so when to cancel them. The value that you specify for the FORCE and FORCE_AT options might affect the drain process described here. For more information, see the descriptions of these options.

DSNUTILB reorganizations

When invoking DSNUTILB, REORG PLUS converts the DRNWAIT option based on the DSNZPARM settings, and passes this option to the IBM Db2 REORG utility as DRNWAIT= integer, where integer is defined as follows:

  • For DRNWAIT=UTIL, integer equals the product of SPRTMTOUT multiplied by SPRMUTO.
  • For DRNWAIT=NONE, integer equals 1 (one second).
  • For DRNWAIT=SQL, integer equals SPRTMTOU1T.

Overriding this option

You can override the value for this option by using the DRAIN_WAIT command option. 

DROPPBGPARTS=YES

When DROP_PART option is not specified, the REORG PLUS utility checks the DROPPBGPARTS user option. When DROPPBGPARTS user option is YES the system parameter REORG_DROP_PBG_PARTS setting is honored. When DROPPBGPARTS user option is NO the system parameter REORG_DROP_PBG_PARTS setting is ignored and the drop part is not performed. For a description of system parameter REORG_DROP_PBG_PARTS, see DB2 Installation and Migration documentation.

DSNUEXIT=(NONE,ASM)

The DSNUEXIT option specifies the name of a user-defined exit that creates data set name patterns and the programming language in which the exit is written. This user exit provides the user-defined variables for constructing name patterns for data sets that REORG PLUS dynamically allocates with either the DSNPAT or SPILDSNP installation option or the DSNPAT or SPILLDSNPAT command option.

The possible values for the language are

  • ASM
  • COBOL2
  • LE_COBOL
  • C
  • LE_C

When invoking DSNUTILB, REORG PLUS ignores this option.

For more information about the DSNUEXIT user exit, see Using-DSNUEXIT-to-construct-data-set-name-patterns-in-REORG-PLUS.

Overriding this option

You can override the value for this option by using the DSNUEXIT command option.

DSNUTILB=YES

The DSNUTILB option tells REORG PLUS whether to invoke DSNUTILB to pass processing to the IBM Db2 REORG utility. REORG PLUS uses this option to enable support for certain features. For the list of features, see Reorganization-jobs-that-invoke-DSNUTILB.

Note

REORG PLUS invokes DSNUTILB to enable new features quickly. REORG PLUS generally provides native support for these features (without invoking DSNUTILB) in a later version of the product or via PTF. You cannot use the DSNUTILB option (or any other option) to request that REORG PLUS invoke DSNUTILB for a feature that REORG PLUS supports natively.

You can specify one of the following values:

  • YES tells REORG PLUS to invoke DSNUTILB when DSNUTILB is required to support the object type that is involved in the reorganization. For a table space reorganization, REORG PLUS invokes DSNUTILB for the job if any table in or index on the table space that you are reorganizing uses a feature that REORG PLUS supports via DSNUTILB.
  • NO tells REORG PLUS to not invoke DSNUTILB. If the type of reorganization job that you are running requires DSNUTILB, REORG PLUS issues message BMC50178E and terminates.

For requirements and restrictions when REORG PLUS invokes DSNUTILB, see Reorganization-jobs-that-invoke-DSNUTILB.

Overriding this option

You can override the value for this option by using the DSNUTILB command option.

DSPLOCKS=DRNFAIL

The DSPLOCKS option tells REORG PLUS what action to take regarding displaying claims and locks if a drain attempt times out:

  • DRNFAIL tells REORG PLUS to display the claims and locks once, after the final attempt to obtain the drain times out.
  • NONE tells REORG PLUS not to display any claims or locks.
  • RETRY tells REORG PLUS to display the claims and locks after each drain timeout.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the DSPLOCKS command option.

DSRSEXIT=(NONE,REXX)

The DSRSEXIT option specifies the name of a user-defined exit for managing the redefinition of Db2 VSAM data sets, and the programming language in which the exit is written. This exit must be written in REXX.

You can use this user exit to

  • Change the primary and secondary quantities of the object that you are reorganizing

    Unless you indicate otherwise, this exit also updates the Db2 catalog with the changed values for use with subsequent allocations.

  • Selectively tell REORG PLUS to specify REDEFINE NO for an object

  • Specify the order of the storage group volumes to use for each object

    You can also restrict the volume list to a subset of the original storage group volume list.

  • Add SMS classes

    If no SMS classes exist in the DSNZPARMs or storage-group definition, you can add the classes by using the DSRSEXIT user exit. However, you cannot change existing specified SMS classes by using the DSRSEXIT user exit.

For more information about the DSRSEXIT user exit, see REORG-PLUS-user-exits.

Overriding this option

You can override the value for this option by using the DSRSEXIT command option.

EXCLDUMP=(X37,X22,X06)

The EXCLDUMP option enables you to limit the conditions under which REORG PLUS generates a system dump when the SDUMP option contains values other than NO. The EXCLDUMP option tells REORG PLUS to exclude the listed abend codes when generating the dump.

Specify a three-digit abend code, such as 806 or 222, or prefix an 'X' to a two-digit abend code to exclude all abend codes that end in those two digits. For example, if you specify X37, REORG PLUS will not generate a system dump for all abend codes that end in 37 (such as B37 or E37). You can specify up to 10 abend codes with the EXCLDUMP option.

Specify EXCLDUMP=0 (without parentheses) if you want all abend codes to be candidates for a system dump.

FASTSWITCH=NO

This option applies to SHRLEVEL REFERENCE or SHRLEVEL CHANGE only.

The FASTSWITCH option determines the action that REORG PLUS takes in the UTILTERM phase regarding the staging data sets.

When invoking DSNUTILB, REORG PLUS passes this option to the IBM Db2 REORG utility for processing.

Additional considerations

Consider the following information about the FASTSWITCH process:

  • You can use the FSFALLBACK and FSTHRESHOLD options to control whether REORG PLUS performs FASTSWITCH or rename processing under particular conditions.
  • BMC recommends specifying FASTSWITCH YES when you are reorganizing objects with more than 200 data sets, such as a segmented table space that contains many tables that each have an index.
  • The FASTSWITCH process requires updates to the Db2 catalog and directory. In some environments, REORG PLUS might have difficulty acquiring the necessary locks, which results in contention or deadlocks. Minimizing the use of the FASTSWITCH process can reduce this contention and allow the process to be more effective when it is needed. Frequently reorganizing the Db2 catalog and directory can also help prevent contention.
  • BMC recommends that you do not specify FASTSWITCH YES when your staging data sets are named according to the STAGEDSN=BMC method.

You can specify one of the following values:

  • NO tells REORG PLUS to rename the staging data sets to the original data set names. This value can help to prevent potential contention issues between the Db2 catalog and the directory.

    If FASTSWITCH NO is in effect, REORG PLUS does not materialize any pending definition changes.

  • YES tells REORG PLUS to bypass the VSAM rename process and directly update the Db2 catalog to use the staging data set names.

    When reorganizing either of the following types of objects, REORG PLUS changes FASTSWITCH=YES to FASTSWITCH=NO:

    • Clone objects
    • Catalog objects

  • ZPARM tells REORG PLUS to use the value that is set in IBM DSNZPARM for FASTSWITCH. FASTSWITCH=ZPARM enables you to use Db2 parameters to manage the FASTSWITCH setting without changing your REORG PLUS installation options module.

    When reorganizing clone objects, REORG PLUS changes this value to NO if the value of the DSNZPARM for FASTSWITCH is YES.

For more information about FASTSWITCH processing, see Staging-data-sets-and-the-FASTSWITCH-process.

Overriding this option

You can override the value for this option by using the FASTSWITCH command option.

FILECHK=FAIL

The FILECHK option specifies the action that REORG PLUS should take when encountering a work file that has been allocated in one of the following ways:

Specify one of the following options:

  • FAIL tells REORG PLUS to terminate.
  • WARN tells REORG PLUS to issue a warning message and continue processing.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

FORCE=NONE

The FORCE option specifies whether to cancel Db2 threads that might prevent a drain process from completing. Specify one of the following options:

  • NONE tells REORG PLUS not to cancel Db2 threads.
  • READERS tells REORG PLUS to cancel read claimers at the point specified by the FORCE_AT option.
  • ALL tells REORG PLUS to cancel both read and write claimers at the point specified by the FORCE_AT option.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the FORCE command option. The FORCE command option provides an additional option, REPORTONLY, that tells REORG PLUS to display a report of the threads that would have been canceled if you had specified FORCE ALL.

FORCE_AT=(START,3)

The FORCE_AT option tells REORG PLUS when to cancel Db2 threads which might prevent the drain process from completing. This option is applicable only when FORCE READERS, FORCE ALL, or FORCE REPORTONLY is in effect.

The first parameter of this option indicates at which point during the drain process to begin canceling threads. The second parameter indicates how long to delay the start of the cancelation process from the specified point in the drain process.

To obtain the same behavior as the FORCE option of the IBM Db2 REORG TABLESPACE utility, specify FORCE_AT=(LASTRETRY,0).

For the first parameter of this option, specify one of the following values:

  • START tells REORG PLUS to start canceling threads when the drain request begins.
  • RETRY tells REORG PLUS to start canceling threads the first time the drain process times out and REORG PLUS attempts to retry the drain.
  • LASTRETRY tells REORG PLUS to start canceling threads at the beginning of the last retry attempt following a drain process timeout. You can control the number of drain retry attempts with the RETRY command option or DRNRETRY installation option.

Note

The cancelation process includes a small amount of time to issue the cancel commands, plus any time that Db2 needs to roll back the canceled transactions. If the drain wait time (controlled by the DRNWAIT option) is shorter than the total cancelation process time, the drain fails. The START and RETRY values allow for additional drain attempts after the start of the cancelation process; therefore, these values increase the likelihood that the drain will succeed when a short drain wait time is in effect. (Alternatively, you can increase the drain wait time.)

For the second parameter of this option, specify an integer value to indicate the hundredths of a second. For example, specify 7 to tell REORG PLUS to wait .07 seconds. Specify an integer value of 0 or greater. The default, 0, tells REORG PLUS to start the cancelation process immediately upon reaching the point specified by the FORCE_AT option.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for the first parameter of this option by using the FORCE_AT suboption of the FORCE command option. You can override the value for the second parameter by using the FORCE_DELAY suboption of the FORCE command option.

FORCE_RPT=NO

The FORCE_RPT option tells REORG PLUS whether to display a report of the canceled threads.

Specify one of the following values for this option:

  • YES tells REORG PLUS to display the report. This value is applicable only when FORCE READERS or FORCE ALL is in effect.

    If your JCL includes a BMCFORCE DD statement, REORG PLUS sends the canceled threads report to that data set. Otherwise, the report is displayed in the REORG PLUS SYSPRINT.

  • NO tells REORG PLUS not to display the report.

Restrictions

REORG PLUS ignores this option when either of the following conditions exists:

  • REORG PLUS is invoking DSNUTILB.
  • You specify FORCE REPORTONLY on the REORG command.

Overriding this option

You can override the value for this option by using the FORCE_RPT suboption of the FORCE command option.

FSFALLBACK=NO

This option applies to SHRLEVEL REFERENCE or SHRLEVEL CHANGE.

The FSFALLBACK option tells REORG PLUS whether to perform rename processing of your staging data sets when FASTSWITCH processing fails:

  • NO tells REORG PLUS to terminate instead of falling back to rename processing if FASTSWITCH processing fails.
  • YES tells REORG PLUS to fall back to rename processing if FASTSWITCH processing fails.

Restrictions

The following restrictions apply to FSFALLBACK:

  • For the following types of reorganizations, REORG PLUS falls back to rename processing only after successfully backing out the FASTSWITCH changes:
    • An index reorganization
    • A partial table space reorganization with a participating nonpartitioned index
  • REORG PLUS ignores this option when any of the following conditions exist:
    • FASTSWITCH NO is in effect.
    • Pending definition changes exist on the object that you are reorganizing.
    • You are rebalancing partitions.
    • REORG PLUS is invoking DSNUTILB.
    • REORG PLUS is converting objects from BRF to RRF.
    • REORG PLUS is converting RBA or LRSN format.

Overriding this option

You can override the value for this option by using the FSFALLBACK command option.

FSTHRESHOLD=0

This option applies to SHRLEVEL REFERENCE or SHRLEVEL CHANGE.

The FSTHRESHOLD option provides a threshold above which REORG PLUS performs FASTSWITCH processing. If the number of staging data sets used in a single reorganization is greater than this value, REORG PLUS performs FASTSWITCH processing. Otherwise, REORG PLUS performs rename processing.

You can specify a value from 0 through 32767. A value of 0 tells REORG PLUS to always perform FASTSWITCH processing.

Restrictions

REORG PLUS ignores this option when either of the following conditions exists:

  • FASTSWITCH NO is in effect.
  • Pending definition changes exist on the object that you are reorganizing.

Overriding this option

You can override the value for this option by using the FSTHRESHOLD command option.

HASHAX (obsolete)

In REORG PLUS versions earlier than 11.2, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) a table space that contained a table that was defined as ORGANIZE BY HASH.

Beginning with version 11.2, REORG PLUS no longer requires or supports the HASHAX installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

ICDDN=(BICY, BICZ)

This option applies to SHRLEVEL CHANGE only.

The ICDDN option specifies the ddnames or ddname prefixes for the local copy data sets that receive an incremental image copy of the table space or partitions that you are reorganizing. The first name is the local primary, and the second name is the local backup. You must define a corresponding incremental data set for each copy data set that you specify if the value of ICTYPE is INCREMENTAL.

When using this name as a prefix for a ddname for a partitioned table space, ensure that you allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). In addition, if you change the default ddname that BMC supplied, you must also change the names in your JCL. For more information, see Incremental-copy-data-sets-for-SHRLEVEL-CHANGE.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the ICDDN command option.

ICTYPE=AUTO

This option applies to SHRLEVEL CHANGE only.

The ICTYPE option tells REORG PLUS to update the full image copy data sets or to create incremental image copy data sets during a SHRLEVEL CHANGE reorganization. Updating only full copies gives the best performance; REORG PLUS does not have to create the incremental copies during the LOGFINAL phase, thus reducing the time that application updates are prevented.

You can specify AUTO, UPDATE, or INCREMENTAL:

  • A value of AUTO tells REORG PLUS to decide whether to update the full copy data sets or to create incremental copy data sets. BMC recommends that you use AUTO to allow REORG PLUS to decide which type of copy is best.

    REORG PLUS updates full copies when either of the following conditions exists:

    • You specify INLINECP=YES in the installation options or INLINE YES on the REORG command.
    • All of the full copy data sets are on DASD, and one full copy data set exists for each partition that you are reorganizing.

    If neither statement is true, REORG PLUS creates incremental copy data sets. You must define or dynamically allocate these incremental copy data sets.

    When invoking DSNUTILB, REORG PLUS ignores ICTYPE=AUTO and DSNUTILB uses ICTYPE UPDATE.

  • If you specify UPDATE (or you specify AUTO and REORG PLUS chooses UPDATE), REORG PLUS always updates the full copy data sets.

    If you specify INLINECP=YES or INLINE YES, REORG PLUS appends the updated pages to the full copy data sets. With INLINE or INLINECP set to YES, the copy data sets can be on tape.

    If you specify UPDATE and the value of the INLINECP installation option or INLINE command option is NO, REORG PLUS updates the full copy data sets in place. If you specify INLINE NO and any of the following statements are true, REORG PLUS terminates:

    • Any of the data sets are not on DASD.
    • The incremental copy data sets are defined as striped data sets.
    • You are attempting to create a single image copy for multiple partitions, as in the following scenarios:
      • You allocate a single copy data set in your JCL but specify multiple partitions.
      • You specify COPYLVL FULL and COPYSUBSET=YES.

  • If you specify INCREMENTAL (or you specify AUTO and REORG PLUS chooses INCREMENTAL), REORG PLUS creates incremental copy data sets. You must define or dynamically allocate these data sets. If the data sets do not exist, REORG PLUS terminates.

    If you specify SHRLEVEL CHANGE and ICTYPE=INCREMENTAL, REORG PLUS behaves as if you specified INLINE NO, regardless of the value that you specified for INLINE or INLINECP.

    When invoking DSNUTILB, REORG PLUS ignores ICTYPE=INCREMENTAL and DSNUTILB uses ICTYPE UPDATE.

If your installation allows SMS data sets to go to tape for the SMS classes that you specify for dynamically allocated copy data sets, you must specify ICTYPE=INCREMENTAL if all of the following statements are true:

  • You specify SHRLEVEL CHANGE.
  • You specify SMS YES.
  • The value of the SMSUNIT installation or command option is NO.
  • The value of the INLINE command or INLINECP installation option is NO.

Note

REORG PLUS supports updating SMS-managed striped data sets for the copy data sets when you specify ICTYPE AUTO or UPDATE and INLINE YES (or INLINECP=YES).

Overriding this option

You can override the value for this option by using the ICTYPE command option.

IDCACHE=10000

The IDCACHE option allows you to specify the size of the cache that REORG PLUS uses when populating document ID columns. Specify the size as the number of values to reserve. REORG PLUS reserves this cache in SYSIBM.SYSSEQUENCES and reserves at least one cache for each unload and log apply task that requires it. The valid values for this option are 1 through 2147483647.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the IDCACHE command option.

INDREFLM=10

This option does not apply to an index-only reorganization.

If the value of the CONDEXEC command or installation option is YES, REORG PLUS issues a report recommending which objects in a table space should be reorganized, and uses the value in the INDREFLM option to conditionally perform the reorganization. Valid values are 0 through 100 or NONE.

For the table space named in the REORG command, REORG PLUS performs the following calculation. The calculation applies to the specified partitions in SYSIBM.SYSTABLEPART for the table space.

(NEARINDREF + FARINDREF) * 100 / CARDF=<integer>

If any calculated integer value exceeds the INDREFLM value, REORG PLUS reorganizes the object.

If the value of the CONDEXEC command or installation option is YES and you specify NONE in the INDREFLM installation option, REORG PLUS performs a conditional reorganization based on the values of the other limit options but not the value of INDREFLM.

Overriding this option

You can override the value for this option by using the INDREFLIMIT command option. If you specify the INDREFLIMIT command option with no value, REORG PLUS uses the value in this installation option as the value for that command option. For more information about the interaction between the limit installation and command options, see Conditional-reorganization.

Tip

You can obtain the report that recommends objects for reorganization without performing any reorganizations. To do so, specify REPORTONLY in the command.

INLINECP=YES

The INLINECP option tells REORG PLUS whether to create inline copies. You can specify YES or NO:

  • INLINECP=YES (the default) specifies that REORG PLUS should create an inline image copy while reloading the table space. This requires that you also specify COPY YES on the REORG command.

    If any of the following conditions exists for a particular reorganization, REORG PLUS behaves as if you specified NO, regardless of the value that you specify for INLINECP or for the INLINE command option:

    • The copy data sets are on a stacked tape.
    • The size of the table space page is greater than 4 KB, you are reorganizing multiple partitions, and you have a single image copy data set.
    • You specify SHRLEVEL CHANGE and ICTYPE INCREMENTAL.
    • You restart a SHRLEVEL NONE or SHRLEVEL REFERENCE table space reorganization and all of the following statements are true:
      • The table space is partitioned.
      • You have a single image copy data set.
      • At least one (but not all) of the partitions was reloaded before the failure.

    If you specify INLINECP=YES for a SHRLEVEL CHANGE reorganization, REORG PLUS uses more memory than it would with INLINECP=NO because it keeps all of the image copy data sets open until the LOGFINAL phase completes processing.

    When invoking DSNUTILB, REORG PLUS passes INLINECP=YES to the IBM Db2 REORG utility, which creates inline, single data set copies.

  • INLINECP=NO specifies that REORG PLUS should not make an inline image copy while reloading the table space, but should create an image copy after reloading the table space.

    REORG PLUS terminates if you also specify ICTYPE UPDATE and you attempt to create a single image copy for multiple partitions, as in the following scenarios:

    • You allocate a single copy data set in your JCL but specify multiple partitions.
    • You specify COPYLVL FULL and COPYSUBSET=YES.

Overriding this option

You can override the value for this option by using the INLINE command option.

INLOB (obsolete)

In REORG PLUS version 10.2 and earlier, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) a table space that contains an inline LOB column.

Beginning with version 11.1, REORG PLUS reorganizes table spaces that contain inline LOB columns natively in most cases and, therefore, no longer uses this option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

INVALIDATECACHE=YES

(SPE2010) The INVALIDATECACHE option indicates whether the SQL Statements in the Dynamic Cache should be invalidated for the processing object.

  • (Default) INVALIDATECACHE=YES tells REORG PLUS to invalidate the SQL Statements in the Dynamic Statement Cache. 
  • INVALIDATECACHE=NO tells REORG PLUS not to invalidate the SQL Statements in the Dynamic Statement Cache.
  • REORG PLUS changes NO to YES when any of the following conditions exist:
    • Pending definition changes exist on the object and REORG PLUS can materialize those changes.
    • You are rebalancing partitions (using either the REBALANCE option or a DDLIN data set)
    • One of the indexes is in a restrictive state when REORG TABLESPACE is executed.
  • When INVALIDATECACHE=NO changes to YES, REORG PLUS also changes UPDATEDB2STATS NO to YES.

Additional considerations

Note the following additional information for INVALIDATECACHE=YES:

  • When invoking DSNUTILB, and UPDATEDB2STATS YES is specified on Db2 version 12, REORG PLUS passes this option to the IBM DB2 REORG utility for processing.

IXONEX (obsolete)

In REORG PLUS versions earlier than 11.2, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) indexes that contained a key derived from certain expressions or table spaces that contained this type of index.

Beginning with version 11.2, REORG PLUS no longer requires or supports the IXONEX installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

IXRANDOM (obsolete)

In REORG PLUS versions earlier than 11.2, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) indexes that contained a key with random ordering or table spaces that contained this type of index.

Beginning with version 11.2, REORG PLUS no longer requires or supports the IXRANDOM installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

KEEPDICTIONARY=NO

This option applies to a table space reorganization only.

The KEEPDICTIONARY option tells REORG PLUS whether to keep the existing compression dictionary. For more information about how REORG PLUS handles compression dictionaries, see Table-space-compression.

  • KEEPDICTIONARY=NO tells REORG PLUS to build a new compression dictionary, even if one already exists. REORG PLUS builds the dictionary and compresses the data during the UNLOAD phase.

  • KEEPDICTIONARY=YES tells REORG PLUS to keep the existing compression dictionary. If a dictionary does not exist, REORG PLUS builds one.

    REORG PLUS ignores KEEPDICTIONARY=YES and operates as if you had specified KEEPDICTIONARY=NO when

    • You are performing partition rebalancing.
    • You are reorganizing a partition-by-growth table space.

When invoking DSNUTILB, REORG PLUS passes KEEPDICTIONARY=YES to the IBM Db2 REORG utility as KEEPDICTIONARY, and ignores KEEPDICTIONARY=NO.

Restrictions

The following restrictions apply to the KEEPDICTIONARY option:

  • The KEEPDICTIONARY option is valid only if the table space or partition that you are reorganizing has the COMPRESS YES attribute.
  • If a table space is compressed and a REORG PLUS job would convert the row format from BRF to RRF, REORG PLUS builds a new dictionary except when both of the following options are in effect:
    • The value of the REORG PLUS KEEPDICTIONARY option is YES.
    • The value of the Db2 subsystem parameter HONOR_KEEPDICTIONARY is YES.

Overriding this option

You can override the value for this option by using the KEEPDICTIONARY command option.

LEAFDSLM=200

This option applies to index-only reorganizations.

If the value of the CONDEXEC command or installation option is YES, REORG PLUS issues a report recommending which objects in a table space should be reorganized. REORG PLUS then uses the value in the LEAFDSLM option to conditionally perform the reorganization. Valid values are any positive integer (0 or greater) or NONE.

For the partitions that you are reorganizing for the specified index, REORG PLUS compares the specified LEAFDSLM value to the value of LEAFDIST in SYSIBM.SYSINDEXPART. If any LEAFDIST value exceeds the LEAFDSLM value, REORG PLUS reorganizes the index.

If the value of the CONDEXEC command or installation option is YES and you specify NONE in the LEAFDSLM installation option, REORG PLUS performs a conditional reorganization based on the values of the other limit options but not the value of LEAFDSLM.

Overriding this option

You can override the value for this option by using the LEAFDISTLIMIT command option. If you specify the LEAFDISTLIMIT command option with no value, REORG PLUS uses the value in this installation option as the value for that command option. For more information about the interaction between the limit installation and command options, see Conditional-reorganization.

Tip

You can obtain the report that recommends objects for reorganization without performing any reorganizations. To do so, specify REPORTONLY in the command.

LOB (obsolete)

In REORG PLUS versions earlier than 11.2, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) table spaces that contained a LOB column, LOB table spaces, or both when a DSNUTILB reorganization was required.

Beginning with version 11.2, REORG PLUS no longer requires or supports the LOB installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

LOCKROW=YES

The LOCKROW option tells REORG PLUS which serialization method to use when updating the BMCSYNC and BMCUTIL tables:

  • YES tells REORG PLUS to use MVS enqueues instead of the SQL LOCK TABLE statements for serialization. Using LOCKROW=YES should prevent most SQL-911 return codes that occur when multiple BMC products concurrently update the BMCSYNC and BMCUTIL tables.
  • NO tells REORG PLUS to use the SQL LOCK TABLE statements for serialization when updating the BMCSYNC and BMCUTIL tables.

Additional considerations

The following considerations apply to the LOCKROW option:

  • Using LOCKROW=YES requires row-level locking. You must define the BMCSYNC and BMCUTIL tables with LOCKSIZE ROW to achieve row-level locking.
  • The following BMC products must use the same LOCKROW value within a subsystem: CHECK PLUS, COPY PLUS, LOADPLUS, RECOVER PLUS, REORG PLUS, and UNLOAD PLUS. Regardless of the value assigned for LOCKROW, COPY PLUS and RECOVER PLUS always behave as if LOCKROW=YES.
  • In a future version, REORG PLUS will no longer require or support the LOCKROW installation option.

LOGFINAL=NONE

This option applies to SHRLEVEL CHANGE only.

The LOGFINAL option specifies when you want REORG PLUS to start the LOGFINAL phase. Through this option, you can control when updates are prevented to the table space or index space that you are reorganizing. You can specify NONE or a time:

  • NONE indicates no set time, and the other log apply options will control the process. For information, see Controlling-the-log-apply-process.
  • You can specify a time in hh:mm:ss format as the value, using a 24-hour clock. REORG PLUS replaces the time portion of the current system timestamp with the time specified to create a new timestamp. If the calculated timestamp time has already passed, REORG PLUS updates the date to the next day. Then, it uses this new timestamp to determine when it will begin the LOGFINAL phase.

Additional considerations

The following considerations apply to the LOGFINAL option:

  • REORG PLUS does not check the LOGFINAL value until the LOGAPPLY phase begins. At that point, if the current time is greater than the time specified on the LOGFINAL option, REORG PLUS immediately begins the LOGFINAL phase.
  • You can use the XBM Utility Monitor function or the MVS operator console to dynamically change LOGFINAL values while the reorganization is in progress.
  • When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the LOGFINAL command option.

LOGMEM=0

This option applies to SHRLEVEL CHANGE only.

The LOGMEM option specifies the amount of data space memory (in kilobytes) needed to hold the internal structures that REORG PLUS uses to store the log records (data and index components). The number must be 0 or a positive integer.

BMC strongly recommends that you use the value 0. A value of 0 tells REORG PLUS to automatically compute the amount of data space memory that it needs. To do so, REORG PLUS uses the formula described in Sizing-memory-for-log-records.

If you specify a nonzero value for LOGMEM, during execution REORG PLUS first ensures that your specified value is sufficient to satisfy the minimum memory requirements. If the value is not sufficient, REORG PLUS issues message BMC50864I and change the value for LOGMEM to the minimum required memory amount.

If you specify a nonzero positive integer, REORG PLUS allocates up to that amount of data space memory.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the LOGMEM command option.

LOGSPIL=(20000,10000)

This option applies to SHRLEVEL CHANGE only.

The LOGSPIL option specifies the primary and secondary space allocation (in kilobytes) for the spill data sets that hold the log records. The number must be a nonzero positive integer. REORG PLUS uses these data sets when the memory allocated with LOGMEM becomes full.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the LOGSPILL command option.

LOGTHRSH=0

This option applies to SHRLEVEL CHANGE only.

The LOGTHRSH option specifies the number of log records as a positive integer (0 or greater). When the number of log records remaining to be applied is less than or equal to this value, REORG PLUS begins the LOGFINAL phase. The LOGFINAL phase prevents updates to the objects and applies the remaining log records.

This option interacts with other options to control the log apply process. For information, see Controlling-the-log-apply-process.

Overriding this option

You can override the value for this option by using the LOGTHRESHLD command option.

LONGLOG=CONTINUE

This option applies to SHRLEVEL CHANGE only.

The LONGLOG option specifies the action to take if REORG PLUS determines that the Db2 subsystem is generating log records for the objects that you are reorganizing faster than REORG PLUS is applying them:

  • CONTINUE tells REORG PLUS to continue performing the reorganization, even if it detects a longlog condition after the time specified by the DELAY option expires.
  • TERM tells REORG PLUS to terminate the reorganization.
  • DRAIN tells REORG PLUS to begin the LOGFINAL phase, prevent updates to the objects that you are reorganizing, and apply the remaining log records.

This option interacts with other options to control the log apply process. For information, see Controlling-the-log-apply-process.

Overriding this option

You can override the value for this option by using the LONGLOG command option.

LONGNAMETRUNC=MIDDLE

The LONGNAMETRUNC option tells REORG PLUS where to truncate names that are longer than the area that is available in a REORG PLUS report-style message. The following table describes the valid values and the symbol that appears in the message based on that value.

Value

Description

Symbol

MIDDLE (or M)

Truncates outward from the middle of the name

><

BEGINNING (or B)

Truncates from the beginning of the name

<<

END (or E)

Truncates from the end of the name

>>

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the LONGNAMETRUNC command option.

MAPTEXIT=(NONE,REXX)

The MAPTEXIT option allows you to specify the name of a user-written exit that creates mapping objects for use with a DSNUTILB reorganization. This exit also drops the mapping objects after DSNUTILB processing completes successfully.

For details about the MAPTEXIT user exit, see Using-MAPTEXIT-to-create-mapping-objects.

Restrictions

The following restrictions apply to the MAPTEXIT option and the MAPTEXIT user exit:

  • REORG PLUS terminates if you also specify the MAPPINGDATABASE option.
  • REORG PLUS uses this exit only when invoking DSNUTILB for a SHRLEVEL CHANGE reorganization.
  • REORG PLUS ignores this option when any of the following conditions exist:
    • You also specify the MAPPINGTABLE command option.
    • You specify REORG INDEX.

Overriding this option

You can override the value for this option by using the MAPTEXIT command option.

MAXNEWPARTS=2

This option applies to partition-by-growth table spaces only.

The MAXNEWPARTS option specifies the following limits:

  • The maximum number of partitions that REORG PLUS can add during a reorganization

    Partition extension is also constrained by the Db2 MAXPARTITIONS value with which the table space was created.

  • The maximum number of partitions added by Db2 that REORG PLUS can support (only applies to a SHRLEVEL CHANGE reorganization of a table space or an index defined on the table)

    If Db2 adds more partitions than the value specified for MAXNEWPARTS, REORG PLUS terminates and issues the message BMC53025E.

You can specify any integer from 0 through 4096 for MAXNEWPARTS. However, BMC recommends that you specify only the number of new partitions that you expect the table space to require. A smaller MAXNEWPARTS value helps you to avoid performance problems and reduces the number of additional partition-level data sets that you must allocate. For information about data set requirements, see Copy data sets and SYSREC data sets.

REORG PLUS ignores this option when either of the following conditions exists:

  • REORG PLUS is invoking DSNUTILB.
  • You are reorganizing a catalog object.

Overriding this option

You can override the value for this option by using the MAXNEWPARTS command option.

MAXRO=300

This option applies to SHRLEVEL CHANGE only.

The MAXRO option specifies the maximum number of seconds that REORG PLUS spends applying log records in the LOGFINAL phase. This estimate does not include the time spent producing incremental image copies and running the UTILTERM phase. Specify the value as a positive integer (0 or greater). When the estimated number of seconds required to apply the remaining log records is less than this value, REORG PLUS ends the LOGAPPLY phase and begins the LOGFINAL phase.

Alternatively, you can specify MAXRO=DEFER, which tells REORG PLUS to continue applying log records indefinitely. The LOGFINAL phase will not begin unless one of the following conditions occurs:

  • You specify a value for the DEADLINE option and the value is reached.
  • You change DEFER to a number of seconds using the XBM Utility Monitor or the MVS operator console.

This option interacts with other options to control the log apply process. For information, see Controlling-the-log-apply-process.

Overriding this option

You can override the value for this option by using the MAXRO command option.

MAXSORTMEMORY=0

The MAXSORTMEMORY option specifies the maximum amount of memory, in kilobytes, that REORG PLUS can allocate to each sort task. The shipped value is 0, which tells REORG PLUS to automatically compute the maximum amount of memory that is needed to perform each sort task. BMCSORT might increase the amount of memory that REORG PLUS allocates if necessary, to successfully complete the sort (if additional memory is available).

In addition to 0, you can specify any number of kilobytes between the value that you specify for the MINSORTMEMORY installation or command option and 2097152.

Note

BMC recommends that you use a value of 0.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the MAXSORTMEMORY command option.

MAXTAPE=3

The MAXTAPE option specifies the maximum number of tape devices to dynamically allocate at one time. The value must be greater than 0.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the MAXTAPE command option.

MGEXTENT=CONTINUE

The MGEXTENT option specifies how to allocate the extents of a Db2 object when creating a new data set during extend processing. Specify one of the following options:

  • CONTINUE tells REORG PLUS to allocate the extents as follows:
    • Allocate the primary extent with the greater of the original primary quantity or the last secondary quantity of the previous data set.
    • Allocate the first secondary extent with the last secondary quantity of the previous data set.
  • RESET tells REORG PLUS to allocate the primary and first secondary extents by using the original values from the Db2 object allocation.

With the exception of this option, REORG PLUS allocates secondary extents in the same way that Db2 does. REORG PLUS uses a sliding-scale calculation for secondary extents, if applicable, that is similar to the method that Db2 uses. For more information, see the Db2 documentation that describes the sliding-scale algorithm.

MINSORTMEMORY=0

The MINSORTMEMORY option specifies the minimum amount of memory, in kilobytes, that REORG PLUS should allocate to each sort task. The shipped and BMC-recommended value is 0, which tells REORG PLUS to automatically compute the minimum amount of memory that is needed to optimally perform each sort task. In addition to 0, you can specify any number of kilobytes between 1024 and the value that you specify for the MAXSORTMEMORY installation or command option.

For information about how this option interacts with the SMCORE installation option, see the description of the SMCORE option.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the MINSORTMEMORY command option.

MSGLEVEL=1

The MSGLEVEL option controls which messages are returned to the user in the SYSPRINT and SYSPRIN2 data sets. MSGLEVEL=0 returns minimal messages. MSGLEVEL=1 returns additional messages to help you diagnose problems and fine-tune performance.

Overriding this option

You can override the value for this option by using the MSGLEVEL parameter on the EXEC statement.

OFFPOSLM=10

This option does not apply to an index-only reorganization.

If the value of the CONDEXEC command or installation option is YES, REORG PLUS issues a report that recommends which objects in a table space should be reorganized. REORG PLUS then uses the value in the OFFPOSLM option to conditionally perform the reorganization. Valid values are 0 through 100, or NONE.

For every table in the table space named in the REORG command, REORG PLUS performs the following calculation. The calculation applies to the specified partitions in SYSIBM.SYSINDEXPART for the table’s explicit clustering index.

(NEAROFFPOSF + FAROFFPOSF) * 100 / CARDF=integer

If any calculated integer value exceeds the OFFPOSLM value, REORG PLUS reorganizes the object.

If the value of the CONDEXEC command or installation option is YES and you specify NONE in the OFFPOSLM installation option, REORG PLUS performs a conditional reorganization based on the values of the other limit options but not the value of OFFPOSLM.

Overriding this option

You can override the value for this option by using the OFFPOSLIMIT command option. If you specify the OFFPOSLIMIT command option with no value, REORG PLUS uses the value in this installation option as the value for that command option. For more information about the interaction between the limit installation and command options, see Conditional-reorganization.

Tip

You can obtain the report that recommends objects for reorganization without performing any reorganizations. To do so, specify REPORTONLY in the command.

OPNDB2ID=YES

The OPNDB2ID option tells REORG PLUS whether to use the Db2 RACF ID or the user’s RACF ID.

  • YES tells REORG PLUS to use the Db2 RACF ID (instead of the RACF ID of the user running REORG PLUS) when opening or performing Access Method Services (AMS) functions on Db2 data sets.
  • NO tells REORG PLUS to use the RACF ID of the user running REORG PLUS. If you specify NO, the user must have the appropriate RACF authority.

For any security system other than RACF, specify OPNDB2ID=NO to have REORG PLUS use the security authorization ID of the user who is running REORG PLUS.

For more information, see Setting-REORG-PLUS-authorizations.

Tip

Using OPNDB2ID=NO can improve performance depending on the size of your data set profiles and the number of VSAM data sets that are involved in this reorganization.

ORIGDISP=DELETE

The ORIGDISP option specifies the action that REORG PLUS should take after it has successfully renamed the staging data sets and completed a SHRLEVEL REFERENCE or SHRLEVEL CHANGE reorganization:

  • DELETE tells REORG PLUS to delete the original data sets.

  • RENAME tells REORG PLUS to rename the original data sets to the staging data set names.

    RENAME enables you to preserve the space that was initially allocated for the original data sets by renaming them to the staging data set names. As a result, the staging data sets are ready to be used in a subsequent reorganization.

    REORG PLUS ignores a value of RENAME if FASTSWITCH YES is in effect. In this case, no rename is needed. The data sets keep their original names, and the space is preserved for use in a subsequent reorganization.

For information about the naming conventions and a description of how the names are changed, see Staging-data-sets.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the ORIGINALDISP command option.

PENDDDL (obsolete)

In REORG PLUS versions earlier than 11.2, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) table spaces or indexes that contained pending DDL changes.

Beginning with version 11.2, REORG PLUS no longer requires or supports the PENDDDL installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

PLAN=ARU1120

The PLAN option specifies the name of the product plan. This plan contains the packages that provide the various capabilities of REORG PLUS.

PREFORMAT=NO

The PREFORMAT option tells REORG PLUS whether to preformat unused data set pages.

  • NO tells REORG PLUS not to preformat unused pages in a data set.
  • YES tells REORG PLUS to write full pages initialized with zeros up to the high-allocated RBA of the table space and index spaces that it just reorganized.

Considerations

The following considerations apply to the PREFORMAT option:

  • When reorganizing a catalog object, REORG PLUS changes PREFORMAT YES to PREFORMAT NO.
  • When invoking DSNUTILB, REORG PLUS passes PREFORMAT=YES to the IBM Db2 REORG utility as PREFORMAT and ignores PREFORMAT=NO.

Overriding this option

You can override the value for this option by using the PREFORMAT command option.

RCVICDDN=(BIRY, BIRZ)

This option applies to SHRLEVEL CHANGE only.

The RCVICDDN option specifies the ddnames or ddname prefixes for the remote copy data sets that receive an incremental image copy of the table space or partitions that you are reorganizing. The first name is the remote primary, and the second name is the remote backup. You must define the corresponding incremental data set for each copy data set that you specify if the value of ICTYPE is INCREMENTAL.

When using this name as a prefix for a ddname for a partitioned table space, ensure that you allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). In addition, if you change the default ddnames that BMC supplies, you must also change the names in your JCL. For more information, see Incremental-copy-data-sets-for-SHRLEVEL-CHANGE.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the RECOVERYICDDN command option.

RCVYDDN=(BRCY, BRCZ)

The RCVYDDN option specifies default ddnames or ddname prefixes for remote copy data sets. These are the data sets that receive an image copy or a DSN1COPY-type copy of the table space or partitions that you are reorganizing. If you are registering the copies, the first name is the remote primary copy, and the second name is the remote backup copy.

When using this name as a prefix, ensure that you allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). In addition, if you change the default ddnames, you must change the names in your JCL. For more information, see Copy data sets.

When invoking DSNUTILB, REORG PLUS passes this option to the IBM Db2 REORG utility for processing.

Overriding this option

You can override the value for this option by using the RECOVERYDDN command option.

REDEFINE=YES

The REDEFINE option tells REORG PLUS whether to delete and redefine the VSAM data sets for the table space or index space as part of the reorganization. REORG PLUS can delete and redefine both user-defined (VCAT-defined) data sets and data sets defined in Db2 storage groups (storage-group-defined).

  • For SHRLEVEL NONE or SHRLEVEL REFERENCE UNLOADONLY, REDEFINE=YES tells REORG PLUS to delete and redefine the VSAM data sets for the space before reloading it. For SHRLEVEL REFERENCE or SHRLEVEL CHANGE, REORG PLUS deletes and defines the staging data sets.
  • REDEFINE=NO tells REORG PLUS not to delete and redefine the existing VSAM data sets for the table space or indexes. Instead, REORG PLUS issues message BMC50391I, reuses the existing data sets, and resets the high-used relative byte address (HURBA).

Additional considerations

The following considerations apply to the REDEFINE option:

  • If you are reorganizing a large number of partitions, consider specifying REDEFINE NO. This value minimizes the time that REORG PLUS requires to delete and redefine the existing VSAM data sets for the table space or indexes.
  • When invoking DSNUTILB, REORG PLUS passes REDEFINE=NO to the IBM Db2 REORG utility as REUSE and ignores REDEFINE=YES.

Overriding this option

You can override the value for this option by using the REDEFINE command option. The command section also contains information about using the REDEFINE option with the DSRSEXIT user exit, the SYSIDCIN data set, and the UNLOAD command.

RENMMAX=30

The RENMMAX option indicates the maximum number of tasks to start during the rename and delete process for SHRLEVEL REFERENCE and SHRLEVEL CHANGE. You can specify any of the following values:

  • 0 to have REORG PLUS determine the number of tasks to start
  • Asterisk (*) to use the TASKMAX value
  • n to specify that REORG PLUS can start a maximum of n tasks (where n is a positive integer from 1 through 32767)
  • n% to specify that the maximum number of tasks that REORG PLUS can start is n% of the number of CPUs on the system (where n is a positive integer from 1 through 32768)

When invoking DSNUTILB, REORG PLUS ignores this option.

For information about using the multitasking options, see Multitasking installation options.

RIDMDSSZ=2097152

This option applies to SHRLEVEL CHANGE only.

The RIDMDSSZ option specifies the maximum size (in kilobytes) for each data space that REORG PLUS uses to store the RID maps. The number must be greater than or equal to 20480 KB (20 megabytes) and not greater than 2097152 KB (2 gigabytes).

RIDMMAXD=1

This option applies to SHRLEVEL CHANGE only.

The RIDMMAXD option specifies the maximum number of data spaces that REORG PLUS can use to store the RID maps. The number must be a nonzero positive integer.

BMC recommends that you use as few data spaces as possible for RIDMMAXD, increasing instead the size of the data space (RIDMDSSZ), especially when spilling occurs. If you specify too many data spaces in RIDMMAXD, performance problems and system degradation can occur.

RMAPMEM=0

This option applies to SHRLEVEL CHANGE only.

The RMAPMEM option specifies the amount of data space memory (in kilobytes) that REORG PLUS can use to store the RID translation maps. The number must be 0 or a positive integer.

BMC strongly recommends that you use the value 0. The value 0 tells REORG PLUS to automatically calculate the RMAPMEM value for you. To determine the value, REORG PLUS multiplies the value of the installation option RIDMMAXD by the value of the installation option RIDMDSSZ. The result is the maximum amount of storage that REORG PLUS can allocate. However, REORG PLUS uses only as much memory as needed to hold the RID map, up to the calculated value.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

Additional considerations

The following considerations apply to the RMAPMEM option:

  • If you specify a nonzero value for RMAPMEM, during execution REORG PLUS first ensures that your specified value is sufficient to satisfy the minimum storage requirements. If the value is not sufficient, REORG PLUS issues a message BMC50887I and changes the value for RMAPMEM to the minimum required storage amount.
  • To calculate the RMAPMEM value, use the formula described in Using formulas for the calculations. However, if you specify a value greater than the result of multiplying the RIDMMAXD value by the RIDMDSSZ value, REORG PLUS reduces the value that you specify to the product of those two installation options.
  • During execution, REORG PLUS allocates memory only as needed, up to the current value of RMAPMEM. If RMAPMEM is insufficient, REORG PLUS issues message BMC50885I and spills to the spill data set.

Overriding this option

You can override the value for this option by using the RIDMAPMEM command option.

RORGMAX=300%

The RORGMAX option indicates the maximum number of tasks to start for the REORG phase. You can specify any of the following values:

  • 0 to have REORG PLUS determine the number of tasks to start
  • Asterisk (*) to use the TASKMAX value
  • n to specify that REORG PLUS can start a maximum of n tasks (where n is a positive integer from 1 through 32767)
  • n% to specify that the maximum number of tasks that REORG PLUS can start is n% of the number of CPUs on the system (where n is a positive integer from 1 through 32768)

Regardless of the value that you specify, REORG PLUS will not start more than 16 tasks for this phase.

Note

For REORG PLUS to use RORGMAX, you must specify SMAX=0, and either not use MAXSORTS or specify MAXSORTS 0.

For information about using the multitasking options, see Multitasking installation options.

ROUTCDE=(11,1)

The ROUTCDE option specifies the routing codes to route write-to-operator (WTO) messages to the designated console. The first subparameter is the code for informational WTOs. The second subparameter is the code for WTOs that require action. The values (11,1) route informational WTOs to programmer information (11) and WTOs requiring action to the master console (1).

For a complete listing of valid values, see the appropriate IBM reference manual.

SCPYMAX=8

The SCPYMAX option indicates the maximum number of tasks to start during the nonpartitioned index copy process for a SHRLEVEL REFERENCE or SHRLEVEL CHANGE partial reorganization. You can specify any of the following values:

  • 0 to have REORG PLUS determine the number of tasks to start
  • Asterisk (*) to use the TASKMAX value
  • n to specify that REORG PLUS can start a maximum of n tasks (where n is a positive integer from 1 through 32767)
  • n% to specify that the maximum number of tasks that REORG PLUS can start is n% of the number of CPUs on the system (where n is a positive integer from 1 through 32768)

For information about using the multitasking options, see Multitasking installation options.

SDUMP=(ALLPSA,CSA,RGN,SQA,LSQA,SUM,TRT,IO)

The SDUMP option tells REORG PLUS to generate a system dump, using the information listed in the option, if the job abnormally terminates. The values listed provide diagnostic information to BMC Customer Support. Although you can specify any values that IBM allows for the SDATA parameter on the SDUMPX macro, BMC recommends that you do not change the values that were shipped with the product. For a complete list and description of the values that you can specify for this option, see the IBM SDUMPX macro description.

REORG PLUS uses the system-defined dump data set to hold the data. In cases where multiple abends occur, REORG PLUS generates the dump for only the first abend. The SDUMP option allows you to generate a system dump, regardless of your access to storage keys 0 through 7.

You can also specify SDUMP=NO (without parentheses) to tell REORG PLUS not to generate a system dump.

Note

REORG PLUS displays SDUMP=YES in message BMC50471I in the SYSPRINT list of options when SDUMP contains one or more values.

To limit the conditions under which REORG PLUS generates the system dump, you can exclude selected abend codes by using the EXCLDUMP option.

SHORTMEMORY=CONTINUE

The SHORTMEMORY option controls the action that REORG PLUS takes when one of the following memory shortages exists during sort processing:

  • The system contains insufficient available pages of memory for REORG PLUS to perform an optimal sort
  • The region contains insufficient memory for REORG PLUS to perform a minimum number of tasks, given the amount of memory required to perform an optimal sort. However, the region does contain at least 1024 KB of memory, or the minimum amount of memory specified by the MINSORTMEMORY option. If the region contain at least 1024 KB of memory and the amount of memory specified by the MINSORTMEMORY option is available, REORG PLUS uses the greater amount of memory.

You can specify one of the following values for the SHORTMEMORY option:

  • CONTINUE, the shipped value indicates that, when a memory shortage exists, REORG PLUS should issue message BMC50364I and continue sort processing.

  • FAIL indicates that REORG PLUS should fail when a memory shortage exists.

    Be aware when specifying FAIL that sufficient memory might exist to sort during the UNLOAD phase of a two-phase reorganization or the REORG phase of a single-phase reorganization. However, because of other system conditions, insufficient available pages might exist during the index build process, which occurs during the RELOAD process (two-phase reorganization) or following the REORG process (single-phase reorganization).

The following table shows the relationship between SHORTMEMORY values and the following conditions:

  • Memory data obtained from the system
  • Memory in the region
  • Value specified for the SMCORE installation option
  • Value specified for the MINSORTMEMORY installation or command option

Memory shortage location

Memory shortage condition

SHORTMEMORY=CONTINUE

SHORTMEMORY=FAIL

Memory in the system

Insufficient to run one optimal sort task based on the amount of data to be sorted

REORG PLUS runs one task with 1024 KB of memory or the amount of memory that you specified with MINSORTMEMORY, whichever is greater.

REORG PLUS fails.

Insufficient as specified by MINSORTMEMORY

Virtual memory in the region

Insufficient to run one optimal sort task based on the amount of data to be sorted

but

sufficient as specified by MINSORTMEMORY or at least 1024 KB, whichever is greater

REORG PLUS runs one task with the available memory.

Insufficient as specified by MINSORTMEMORY or less than 1024 KB, whichever is greater

REORG PLUS fails.

Insufficient as specified by the first parameter of SMCORE

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the SHORTMEMORY command option.

SIXSNAP=NO

This option applies to a SHRLEVEL REFERENCE or SHRLEVEL CHANGE partial table space reorganization only.

The SIXSNAP option determines whether REORG PLUS uses the Instant Snapshot technology of the EXTENDED BUFFER MANAGER (XBM) product or the SNAPSHOT UPGRADE FEATURE (SUF) of XBM to create a copy of storage-group-defined nonpartitioned indexes. Using Instant Snapshot can improve performance because Instant Snapshot makes a hardware-based copy of the entire index at one time. To use Instant Snapshot, you must have the supported intelligent storage devices available.

  • NO tells REORG PLUS to use the software-based copy method to copy each nonpartitioned index.

  • AUTO tells REORG PLUS to use Instant Snapshot.

    If the Instant Snapshot copy fails, REORG PLUS copies the index using the software copy method.

  • YES tells REORG PLUS to use only Instant Snapshot technology.

    If the Instant Snapshot copy fails, REORG PLUS terminates.

Although using SIXSNAP can improve the performance of the reorganization, SIXSNAP can cause the application to time out. The order of volumes allocated can differ from the order in your list, depending on the hardware vendor. For more information, see Considerations for SIXSNAP use.

For detailed information about the SIXSNAP function, see Instant-Snapshot-with-nonpartitioned-indexes. For a list of the supported devices, see the EXTENDED BUFFER MANAGER for DB2 documentation.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the SIXSNAP command option.

SMAX=0

The SMAX option specifies the number of sort tasks that can run concurrently during a reorganization. If sorting is required to perform the reorganization, SMAX also limits the number of concurrent sorts. Limiting the number of concurrent sorts can have a significant impact on performance because sorting requires a substantial amount of system resources.

If you specify a value for SMAX, REORG PLUS starts only one task per CPU. If you want to improve performance by starting more than one task per CPU, use the default of SMAX=0, and use the multitasking options. For more information about using the multitasking options, see Multitasking installation options.

For information about the hierarchy of the SMAX, MAXSORTS, and multitasking options, see Multitasking options. For more information, see Controlling the number of sort processes.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the MAXSORTS command option.

SMCORE=(0K,0K)

The SMCORE option specifies the amount of memory that you want each invocation of BMCSORT to use. BMC strongly recommends that you use the values 0K and 0K for this option. The values 0K and 0K indicate that REORG PLUS is to determine the appropriate amount of memory to use for each sort process. However, other valid values are:

  • For the first parameter, 4096K through 65536K (or 0M or 4M through 64M)

    The first value specifies the total amount of memory to use both above and below the 16-megabyte line for each sort.

  • For the second parameter, 256K through 4096K (or 0M or 1M through 4M)

    The second value specifies the amount of memory to use below the 16-megabyte line for each sort.

When invoking DSNUTILB, REORG PLUS ignores this option.

For more information about how REORG PLUS uses SMCORE and the other sort optimization options, see Controlling memory usage.

SORTDEVT=(,SYSALLDA)

The SORTDEVT option specifies the device type for the sort work files that are allocated dynamically.

The first parameter of this option is the device type to use for non-DSNUTILB jobs. This parameter overrides the first parameter of the BMCSORT DYNALOC installation option. If the value of the third parameter in the BMCSORT DYNALOC installation option is OFF, specifying a value for this parameter turns BMCSORT dynamic allocation on.

The second parameter of this option is the device type to use for DSNUTILB jobs. When invoking DSNUTILB, REORG PLUS passes this option to the IBM Db2 REORG utility for processing.

Overriding this option

You can override the values for both parameters of this option by using the SORTDEVT command option.

SORTNUM=32

The SORTNUM option affects the allocation of sort work files in the following cases. The shipped value is 32, and you can specify any integer value from 0 through 255.

DSNUTILB reorganization jobs

When invoking DSNUTILB, REORG PLUS passes this value to the IBM Db2 REORG utility as the number of sort work files to allocate dynamically. For this type of reorganization, the value must be 2 or greater.

All other reorganization jobs

This value is in effect when BMCSORT is allocating your sort work files dynamically. The following table describes the action that BMCSORT takes for each value that you can specify for this option. The table also provides any additional considerations for these values.

Value

Description

Additional considerations

0

BMCSORT honors the value of the third parameter of the BMCSORT DYNALOC installation option. (This parameter tells BMCSORT whether to dynamically allocate sort work files.)

For more information about how this parameter affects dynamic allocation, see Dynamically allocating SORTWK data sets. For more information about the parameter itself, see DYNALOC-installation-option.

1-32

BMCSORT dynamically allocates the number of sort work files that it needs, up to 32 minus any preallocated sort work files. This number is per sort task.

Preallocated sort work files include sort work files that are allocated in your JCL and any sort work files that REORG PLUS dynamically allocates.

33-255

BMCSORT dynamically allocates the number of sort work files that it needs, up to the number that you specified minus any preallocated sort work files. This number is per sort task.

If the value of the third parameter in the BMCSORT DYNALOC installation option is OFF, specifying a value greater than 0 for the SORTNUM option turns BMCSORT dynamic allocation on and BMCSORT allocates sort work files as needed. For information about when BMCSORT allocates your sort work files dynamically, see SORTWK data sets.

Overriding this option

You can override the value for this option with the SORTNUM command option.

SPILDSNP=&&UID

This option applies to SHRLEVEL CHANGE only.

The SPILDSNP option tells REORG PLUS to use a particular pattern of variables and text to create a prefix for the spill data set names. The spill data sets hold the log records and RID maps when they overflow memory. REORG PLUS dynamically allocates the spill data sets as needed. The spill data sets are VSAM objects.

The pattern must resolve to a prefix that is 22 bytes or less and does not end in a period. You can use text or any of the symbolic variables listed in the following table to construct your pattern. You can also provide user-defined variables from a user exit (specified with the DSNUEXIT installation or command option). When specifying a pattern in your installation options, you must precede each REORG variable with an additional ampersand (&) in your pattern.

REORG PLUS removes any trailing blanks in the result.

Symbolic variable

Definition

Length of result

&DATE

Current date (in the form MMDDYY)

6 bytes

&DATEJ

Current Julian date (in the form YYYYDDD)

7 bytes

&DB

Database containing the space for this data set allocation

8 bytes maximum

&GRPNM

Db2 data-sharing group name

In a non-data-sharing environment, GRPNM contains the DB2 SSID.

4 bytes

&JDATE

Current Julian date (in the form YYDDD)

5 bytes

&JOBNAME

JOB name in the JCL

8 bytes maximum

&RTYPE

REORG type (TS or IX)

2 bytes maximum

&SSID

Db2 subsystem ID

4 bytes

&STEPNAME

STEP name used in the JCL

REORG PLUS ignores PROC names.

8 bytes maximum

&TIME

Current time (in the form HHMMSS)

6 bytes

&TIME4

Current time (in the form HHMM)

4 bytes

&TSIX

Table space or index space specified in your REORG command

8 bytes maximum

&USERID or &UID

Job user ID

You must have a security package to use the job user ID variable.

8 bytes maximum

&UTIL

BMC utility ID

8 bytes maximum

REORG PLUS truncates longer utility IDs to eight characters.

&UTILPFX

BMC utility ID prefix

8 bytes maximum

&UTILSFX

BMC utility ID suffix

8 bytes maximum

&VCAT

VCATNAME specified in the Db2 catalog for the table space that you are reorganizing; or, if the table space is partitioned, the VCAT name from the first partition that you are reorganizing

8 bytes

For more information and guidelines for specifying data set name patterns, see SPILLDSNPAT. User exits are discussed in REORG-PLUS-user-exits.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the SPILLDSNPAT command option.

SPILSCLS=NONE

This option applies to SHRLEVEL CHANGE only.

The SPILSCLS option specifies the SMS storage class that REORG PLUS uses to allocate spill data sets. You can specify a valid SMS storage class name not exceeding eight characters, or NONE. The spill data sets are VSAM objects.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the SPILLSTORCLAS command option.

SPILUNIT=WORK

This option applies to SHRLEVEL CHANGE only.

The SPILUNIT option specifies the DASD unit to which REORG PLUS can allocate spill data sets. The unit name must be a valid DASD unit name not exceeding eight characters, or NONE. The spill data sets are VSAM objects.

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the SPILLUNIT command option.

SQLDELAY=3

The SQLDELAY option specifies the number of seconds that REORG PLUS should wait between retry attempts after receiving an SQL -911 return code. This interval is in addition to the time that elapses when Db2 waits for a timeout or deadlock. The number of seconds can range from 1 through 655.

SQLRETRY=100

The SQLRETRY option specifies the number of times that REORG PLUS should retry an SQL statement after it receives an SQL -911 return code. The number of retry attempts can range from 1 through 255.

STAGEDSN=BMC

The STAGEDSN option tells REORG PLUS which naming convention you want it to use for the staging data sets. STAGEDSN=BMC tells REORG PLUS to allocate staging data sets with the second node of BMCDBC and BMCDBD for the cluster and data nodes.

STAGEDSN=DSN tells REORG PLUS to allocate staging data sets with the second node of DSNDBC and DSNDBD and the fifth node of I or J (whichever letter is not in the original data set name).

If FASTSWITCH YES is in effect, REORG PLUS changes STAGEDSN=BMC to STAGEDSN=DSN.

For more information about staging data sets and their naming conventions, see Staging-data-sets.

STOP@CMT=YES

This option applies to SHRLEVEL NONE and SHRLEVEL REFERENCE only.

The STOP@CMT option specifies whether to add the 'AT (COMMIT)' parameter to all Db2 STOP commands that REORG PLUS issues. YES adds the parameter and NO does not.

Considerations

BMC recommends that you specify the value for STOP@CMT based on your environment and your availability goals. Under certain circumstances, using STOP@CMT=N might result in the object being placed in stop pending status (STOPP) and failure of the reorganization. REORG PLUS issues the following message in this case:

BMC50266E SPACE '<databaseName>.<spaceName>' CANNOT BE STOPPED. IT MAY BE IN USE

This situation might result when one of the following conditions exists:

  • You are reorganizing one partition of a partitioned table space while an application thread is using other partitions of the same table space.
  • You are reorganizing an index while an application thread is using the table space.

By using STOP@CMT=YES, you might avoid this problem, but application threads might be affected. When a thread performs a commit, Db2 might stop the object, although the thread continues to run. For details and implications of the 'AT(COMMIT)' parameter, see the IBM Db2 command reference manual.

STOPDELAY=1

The STOPDELAY option specifies the number of seconds that REORG PLUS waits before it checks again to see if Db2 has stopped the object. The number of seconds can be any nonzero positive integer.

STOPRETRY=300

The STOPRETRY option specifies the number of times that REORG PLUS checks to see if Db2 has changed the status of an object from stop pending (STOPP) to stopped (STOP). The number of checks can be any nonzero positive integer.

TAPEDISP=DELETE

The TAPEDISP option specifies the final disposition of tape data sets when you specify YES for the DELFILES installation or DELETEFILES command option. TAPEDISP=DELETE specifies that each tape file will have a disposition of OLD,DELETE,DELETE when the tape is deallocated.

If you specify TAPEDISP=UNCATLG, each tape file will have a disposition of OLD,UNCATLG,UNCATLG when the tape is deallocated. Depending on your tape management environment, using UNCATLG can prevent a tape remount.

TASKMAX=1000%

The TASKMAX option sets the default for all of the other multitasking options. TASKMAX does not directly provide the number of tasks to use. Instead, TASKMAX provides a default value for any option that refers to it. You can specify any of the following values:

  • 0 to specify that REORG PLUS determines the number of tasks to start
  • n to specify that REORG PLUS can start a maximum of n tasks (where n is a positive integer from 1 through 32767)
  • n% to specify that the maximum number of tasks that REORG PLUS can start is n% of the number of online CPUs on the system (where n is a positive integer from 1 through 32768)

For more information about using the multitasking options, see Multitasking installation options.

TERMEXIT=(NONE,REXX)

The TERMEXIT option allows you to specify the name of a user-written exit that gives you dynamic control over several options at termination time. Use the TERMEXIT user exit to dynamically control processing of updates to BMCHIST, BMCSTATS, real-time statistics, and UPDATEDB2STATS. This exit must be written in REXX.

For details about the TERMEXIT user exit, see Using-TERMEXIT-to-control-BMCHIST-and-statistics-updates.

Restrictions

The following restrictions apply to the TERMEXIT option and to using a TERMEXIT user exit:

  • When invoking DSNUTILB, REORG PLUS ignores this option.
  • You cannot use a user exit supplied by the TERMEXIT option to override BMCSTATS NO or UPDATEDB2STATS NO to YES.
  • REORG PLUS always updates Db2 statistics after materializing pending definition changes. If you have a TERMEXIT user exit that changes UPDATEDB2STATS to NO in this case, REORG PLUS changes that specification to UPDATEDB2STATS YES.

Overriding this option

You can override the value for this option by using the TERMEXIT command option.

TIMEOUT=TERM

The TIMEOUT option specifies the action that REORG PLUS should take after it has exhausted all retry attempts to obtain a drain.

  • If you specify TIMEOUT=TERM (or TERM, rc) and a timeout condition occurs, REORG PLUS
    • Issues messages BMC50020I and BMC50285E
    • Leaves the objects in their original state
    • Terminates the utility
    • (non-DSNUTILB reorganizations only) Ends with the return code you specified
      • When you specify an integer of 31 or less, REORG PLUS issues the return code.
      • When you specify an integer that is 32 or greater, REORG PLUS issues a user abend that is equal to the specified integer.
    • Deletes the work files and unregistered copy data sets if you set the value for the DELFILES installation option to YES, or you specify DELETEFILES YES on the command

  • If you specify TIMEOUT=ABEND and a timeout condition occurs, REORG PLUS

    • Abnormally ends (abends) with user code 3200
    • Leaves the objects in their original state
    • Leaves an entry in the BMCUTIL table

    If this condition occurs when you are running a SHRLEVEL CHANGE reorganization, you must resubmit the job with TERM instead of NEW on the EXEC statement.

The value of the return code depends on the value that you specified for the TIMEOUT installation option and the ON FAILURE command option, as described in the following table.

TIMEOUT installation option with TERM

ON FAILURE with RETCODE specified

Return code is returned from

TERM

Yes

ON FAILURE: return code that you specified with RETCODE

TERM

No

TIMEOUT: return code 8

TERM, rc

Does not matter

TIMEOUT: return code that you specified with TERM

No value specified

No

REORG: return code 8

Overriding this option

You can override the value for this option by specifying the TIMEOUT command option.

TOTALPAGEPCT=0

The TOTALPAGEPCT option controls memory above the 16-MB line that REORG PLUS allocates to BMCSORT for concurrent sort processing. TOTALPAGEPCT specifies the maximum percentage of total 4-KB pages, as obtained from the system, that REORG PLUS can allocate. You can specify any integer from 0 through 100.

Note

REORG PLUS defines total pages as pages that are underutilized and are available for use. Available pages (which you can control with the AVAILPAGEPCT option), are pages that have not been used.

A value of 0 tells REORG PLUS to ignore the number of total pages when allocating sort memory.

A value of 1 through 100 tells REORG PLUS to use up to the specified percentage of total pages when allocating sort memory. For example, TOTALPAGEPCT 50 tells REORG PLUS to use no more than 50 percent of the total pages.

Additional considerations

The following additional information applies to the TOTALPAGEPCT option:

  • When you specify values greater than 0 for both TOTALPAGEPCT and AVAILPAGEPCT, REORG PLUS uses the lesser of the two calculated results as the maximum amount of memory for sort processing.
  • If REORG PLUS is unable to start any tasks because of restraints on sort memory caused by a low number of total or available pages, the SHORTMEMORY installation option or command option controls the action that REORG PLUS takes.
  • When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by specifying the TOTALPAGEPCT command option.

TSSAMPLEPCT=100

This option applies to a table space reorganization only.

The TSSAMPLEPCT option enables you to specify a percentage of table space pages that you want REORG PLUS to sample when gathering statistics. The following values are valid:

  • 1 through 50 tells REORG PLUS to sample the specified percentage of the table space pages.
  • 100 tells REORG PLUS to read all table space pages instead of sampling.

Note

Values 51 through 99 are not valid.

Restrictions

REORG PLUS ignores the TSSAMPLEPCT option for either of the following types of reorganizations:

  • A DSNUTILB reorganization
  • An index reorganization

Overriding this option

You can override the value for this option by using the TSSAMPLEPCT command option.

UBUFFS=20

The UBUFFS option specifies a multiple of 32 KB to use to define the amount of buffer pool storage that is allocated for the unload (SYSREC) data sets. For more information, see SYSREC data set.

UNLDDN=SYSREC

The UNLDDN option specifies the default ddname or ddname prefix for the output data set that contains the unloaded rows to be reorganized.

When using this name as a prefix for a ddname for a partitioned table space, ensure that you allow sufficient bytes for the partition number to be added and still have a valid ddname (eight bytes or less). In addition, if you change the default ddname that BMC supplies, you must also change the name in your JCL. For information about specifying and using this data set, see SYSREC data sets.

DSNUTILB reorganization jobs

When invoking DSNUTILB, REORG PLUS uses this option only to pass a value for the &DDNAME variable for the data set name pattern. REORG PLUS includes this information in the TEMPLATE control statement that it builds for the IBM Db2 REORG utility.

Overriding this option

You can override the value for this option by using the UNLDDN command option.

UNLDMAX=300%

The UNLDMAX option indicates the maximum number of tasks to start per CPU for the UNLOAD phase. You can specify any of the following values:

  • 0 to have REORG PLUS determine the number of tasks to start
  • Asterisk (*) to use the TASKMAX value
  • n to specify that REORG PLUS can start a maximum of n tasks (where n is a positive integer from 1 through 32767)
  • n% to specify that the maximum number of tasks that REORG PLUS can start is n% of the number of CPUs on the system (where n is a positive integer from 1 through 32768)

Regardless of the value that you specify, REORG PLUS will not start more than 16 tasks for this phase.

Note

For REORG PLUS to use UNLDMAX, you must specify SMAX=0, and either not use MAXSORTS or specify MAXSORTS 0.

For information about using the multitasking options, see Multitasking installation options.

UNLOAD=RELOAD

The UNLOAD option tells REORG PLUS whether to use single-phase or two-phase processing. You can specify either RELOAD or CONTINUE. For more information about these options, see UNLOAD.

  • RELOAD (the default) tells REORG PLUS to use single-phase processing. Single-phase processing is usually much faster than two-phase processing. However, if the job fails, you might not be able to restart the job. For more information, see Single-phase-reorganization.

  • CONTINUE tells REORG PLUS to continue the reorganization with two-phase processing after the UNLOAD phase has unloaded the data. If the reorganization fails during two-phase processing, you can restart the job.

    Note

    REORG PLUS changes UNLOAD CONTINUE to UNLOAD RELOAD when you are reorganizing a LOB table space and SHRLEVEL REFERENCE is in effect.

Overriding this option

You can override the value for this option by using the UNLOAD command option. An additional value is available with the command option.

UTILB_COLCCSID (obsolete)

In REORG PLUS versions earlier than 11.2, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) a table space that contained columns defined with a CCSID specification.

Beginning with version 11.2, REORG PLUS no longer requires or supports the UTILB_COLCCSID installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

UTILB_NULLIX (obsolete)

In REORG PLUS versions earlier than 11.2, this option told REORG PLUS whether to reorganize (by invoking DSNUTILB) table spaces that contained indexes that were defined with EXCLUDE NULL KEYS.

Beginning with version 11.2, REORG PLUS no longer requires or supports the UTILB_NULLIX installation option. If your installation options module contains this option, the module compiles successfully but completes with return code 4 and a message indicating that this option is obsolete.

UXSTATE=SUP

The UXSTATE option tells REORG PLUS how to invoke Db2 user exits:

  • SUP specifies that REORG PLUS should call EDITPROCs in supervisor state (and PSW key=7).
  • PROB tells REORG PLUS to call EDITPROCs in problem state and PSW key=7.

The requirements of the exits dictate the UXSTATE setting. Check with the exit author (or vendor) before changing the value of this option.

WBUFFS=(20,10)

The WBUFFS option specifies a multiple of 32 KB to use to define the amount of buffer pool storage that is allocated for each work (SYSUT1) data set. For more information, see SYSUT1 data set.

Note

REORG PLUS now ignores the second parameter of this option.

WORKDDN=SYSUT1

The WORKDDN option specifies the default ddname or ddname prefix for the index work data set that contains the unloaded index keys and serves as input for BMCSORT.

When using this name as a prefix, allow sufficient bytes for the number of indexes to be added and still have a valid ddname (eight bytes or less). In addition, if you change the default ddname that BMC supplies, you must also change the name in your JCL. For information about specifying and using this data set, see SYSUT1 data sets.

DSNUTILB reorganization jobs

When invoking DSNUTILB, REORG PLUS uses this option only to pass a value for the &DDNAME variable for the data set name pattern. REORG PLUS includes this information in the TEMPLATE control statement that it builds for the IBM DB2 REORG utility.

Overriding this option

You can override the value for this option by using the WORKDDN command option.

WORKUNIT=SYSALLDA

The WORKUNIT option specifies the unit to use for a temporary work data set. VIO is an acceptable value for this option.

WRLOG=NO (PTF BQU2911 applied)

This feature is supported only for Db2 V12 with APAR PH11871 applied.  

The WRLOG option specifies whether to write Db2 diagnostic log records to indicate that a refresh is required for replicated objects. These records are written regardless of whether the object is replicated or not.

The default is NO. 

The default is NO. Specifying YES writes Db2 diagnostic log records and specifying NO does not.

(BMC.DB2.SPE2401)When the BMCSYSADM user option parameter is present, REORG PLUS uses it for DSNUTILB REPAIR when WRLOG=YES is specified.

When SmartSwitch with the BMCSYSADM switches to a BMC AMI Utility, BMCSYSADM and WRLOG are not passed to the BMC AMI Utility product. The BMC AMI +SQLID and +WRLOG(YES) global parameters are used instead.

Overriding this option

There is no command to override WRLOG option.

XBMID=

The XBMID option specifies the XBM subsystem (SSID) that REORG PLUS accesses when it uses XBM or SUF. Specify a value for this option if you want to use a specific XBM subsystem for snapshot processing and zIIP processing in REORG PLUS.

The SSID is the unique identifier that was specified when XBM or SUF was installed. If you are using XBM or SUF in a Db2 data sharing environment, you can use the value of the XBMGROUP parameter instead of the XBM SSID. The XBMGROUP name is the name of the cross-system coupling facility (XCF) group that is defined to the XBM subsystem, and its default value is XBMGROUP.

If you specify an XBM subsystem, it must be:

  • Available
  • At a supported maintenance level
  • Enabled for the required function

If you do not specify an XBM subsystem (either here or with the XBMID installation option), REORG PLUS automatically searches for an XBM subsystem that meets the same criteria. If you have multiple subsystems that meet these criteria, REORG PLUS can use any one of these subsystems.

For more information about using XBM or SUF with REORG PLUS, see SUF (also known as XBM) considerations. For more information about XBM and SUF, see the EXTENDED BUFFER MANAGER for DB2 documentation.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the XBMID command option.

ZIIP=ENABLED

The ZIIP option tells REORG PLUS whether to attempt to use IBM z Integrated Information Processors (zIIPs). REORG PLUS can use enclave service request blocks (SRBs) to enable zIIP processing automatically while running jobs. Using zIIP processing can reduce the overall CPU time for REORG PLUS jobs.

You can specify one of the following values:

  • ENABLED tells REORG PLUS to attempt to offload eligible processing to an available zIIP. If the zIIP is busy or not available, normal processing continues on a general-purpose processor.
  • DISABLED tells REORG PLUS to not attempt to use zIIP processing.

To enable and use zIIP processing with REORG PLUS, you must

  • Have an installed authorized version of XBM or SUF

  • Start and maintain an XBM subsystem in your environment

    Note

    You can specify a particular XBM subsystem to use by specifying a value for the XBMID installation or command option.

  • Have a zIIP available in your environment

For more information about the XBM component that enables the use of zIIPs, see the EXTENDED BUFFER MANAGER for DB2 documentation.

Restriction

When invoking DSNUTILB, REORG PLUS ignores this option.

Overriding this option

You can override the value for this option by using the ZIIP command option.

Related topic

Basic-REORG-PLUS-installation-options

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*