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 BMC AMI Recover for Db2 13.1.

Recommendations for a large number of concurrent sorts

BMC AMI Recover

 automatically checks the available memory in the system (total and in use) and estimates the amount of memory needed to do each sort.

If enough memory is available without impacting the system, BMC AMI Recover starts up to MAXKSORT and MAXLSORT sorts concurrently.

If not enough memory is available, BMC AMI Recover automatically reduces the values for MAXKSORT and MAXLSORT to the maximum number of sorts that can run concurrently with the available memory. BMC AMI Recover first reduces MAXLSORT as far as necessary until the value of MAXLSORT is 2. If too many sorts for available memory are still indicated, BMC AMI Recover then reduces MAXKSORT until a manageable number of sorts is reached.

BMC AMI Recover does not reduce MAXLSORT to favor MAXKSORT if no indexes are being rebuilt.

In almost all cases, BMC AMI Recover optimizes the number of sorts automatically.

In the rare case that too many sorts are running and performance is degrading, you can

  • Reduce the number of sorts by setting MAXKSORT
  • Control the amount of memory used by each sort using SMCORE

Important

You can set the SMCORE and MAXKSORT options in the $AFROPTS installation macro or you can code them in the OPTIONS statement in the SYSIN for each BMC AMI Recover job.


Related topic

Sort-performance


 

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