MAXKSORT

This option specifies the maximum number of index key sorts that can run in parallel.

The value of MAXKSORT also determines the concurrency of index rebuilds. Thus, MAXKSORT can be used to improve recovery performance. (The KSORTSHARE-YES option also impacts index recovery.)

Important

When you rebuild the indexes of multi-data-set, nonpartitioned table space, the UNLOADs run serially in the main task, but the REBUILDs are multitasked.

Valid values are 1 to 999. The default value is given by the following formula:

minimum((2 × the number of CPUs), 12)

Related topics

BMC-AMI-Recover-installation-options

Examples-of-BMC-AMI-Recover-jobs

MAXKSORT option

MAXKSORT-integer

Data sets needed for parallel index sorts and rebuilds

Determining-sort-work-space-requirements

Important

Each sort requires about 256 KB of memory below the line. Values for MAXKSORT greater than 12 are not recommended.

You can override the MAXKSORT installation option by using the MAXKSORT parameter with the OPTIONS command. For more information, see UNLOADKEYS-and-BUILDINDEX-strategy.

When you specify MAXKSORT, the following files are dynamically allocated if you do not code them in JCL:

SYSOUnnn: sort message files
nnn is a number between 1 and the value that is specified for MAXKSORT.
SxxxWKnn: key sort work files
xxx is a number between 1 and the value that is specified for MAXKSORT. nn is a number between 1 and the value that is specified for the SORTNUM installation option or the OPTIONS SORTNUM parameter.

When you use dynamic allocation for these files, BMC AMI Recover determines the optimal number of files to use.

Important

When the value of MAXKSORT is greater than 1, BMC AMI Recover ignores the WORKDDN option on the REBUILD INDEX command and issues a warning message. To use the WORKDDN option, specify a value of 1 for MAXKSORT. For a description of WORKDDN, see WORKDDN-DDName.

MAXKSORT

BMC AMI Recover for Db2 13.1

On this page