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 High-speed Apply Engine 13.1.

Positional requirements for ObjectPartition parameters

The position of the [ObjectPartition] parameters is significant. If the parameters are out of order, the High-speed Apply Engine issues message number BMCAPT0060E, and apply processing terminates.

You must specify the parameters in the following order. For an example of the parameter order, see Example, [ObjectPartition] parameters for Db2 mainframe target.

  1. A Table parameter must be the first parameter in the section.
  2. The Column parameter set follows the Table parameter. The Column parameters must also be ordered so that they correspond to their associated Value parameters in each definition that starts with a Partition parameter.
  3. If you specify the Order parameter, it must directly follow its associated Column parameter. The Order parameter is valid only for Db2 targets on a mainframe.
  4. The first Partition parameter follows all of the Column parameters specified for the table.
  5. A set of Value parameters or a LimitKey parameter must come after a Partition parameter. The LimitKey parameter is valid only for Db2 targets on a mainframe. You cannot include both a set of Value parameters and a LimitKey parameter after the same Partition parameter (the two are mutually exclusive).

Related topic

ObjectPartition-parameters

 

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