Default language.

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 Load for Db2 13.1.

Allocation strategies

An allocation strategy is the implementation of your requirements for data set allocation. An allocation strategy includes:

  • Data set placement
  • Allocation values (primary quantity and secondary quantity)
  • Data set reuse
  • Updating the Db2 Catalog values

An allocation strategy also:

  • Determines how a product should allocate, and use the table spaces and indexes that are being processed
  • Includes where and how big the data sets should be defined, and whether the existing data set should be written over, or deleted and redefined

Important

Regardless of whether a data set is user-managed or Db2-managed (STOGROUP defined), BMC AMI Utilities delete and redefine the VSAM data set. Therefore, it is vital to review this information.

You can make the BMC AMI Utilities define data sets in the same way Db2 does, but that is not always the best way. The BMC AMI Utilities offer allocation features that enhance the process. For example, you can reclaim unused space in a table space as a normal part of a reorganization. A PQTY value that does not fit on a volume and would cause a Db2 utility to fail can be dynamically reduced to fit.

Important

This topic uses the terms priqty and secqty to refer to the VSAM allocation values for the data set. When referring specifically to the Db2 catalog values for these terms, PQTY and SQTY are used since these are the Db2 Catalog column names.

You can manage allocation at one of the following levels:

Related topics

Overview-of-BMC-AMI-Utilities-concepts

ALLO 

VOLUMES


 

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