Integrating


This topic provides information about integrating the product with other products and solutions. 

Solution integration

The High-speed Apply Engine is a component of BMC AMI Log Master for Db2. In turn, BMC AMI Log Master for Db2 (including High-speed Apply Engine) is a component of the BMC Recovery Management for Db2 solution.

Related topic

The BMC Recovery Management for Db2 solution integrates the features of:

  • BMC AMI Recovery Manager for Db2
  • BMC AMI Recover for Db2
  • BMC AMI Copy for Db2 
  • BMC AMI Log Master for Db2
  • SNAPSHOT UPGRADE FEATURE

When you acquire this solution, you benefit from all features of these individual products and from more features that are available when one Recovery Management component can rely on the presence of all others. For more information, see the Recovery Management for Db2 documentation.

LOADPLUS and High-speed Apply Engine

This section summarizes the relationship between the LOADPLUS for DB2 product from BMC and the High-speed Apply Engine product (which is also distributed with the BMC AMI Log Master for Db2 product).

For more information about LOADPLUS, see the LOADPLUS for DB2 documentation.

How LOADPLUS uses High-speed Apply Engine

LOADPLUS calls the High-speed Apply Engine to perform a load action that retains a Db2 object in read/write status and that does not replace data (LOAD RESUME YES SHRLEVEL CHANGE SQLAPPLY). This action is sometimes referred to as a SQLAPPLY load. When LOADPLUS calls High-speed Apply Engine, it has access to only the High-speed Apply Engine capabilities required for the load action.

LOADPLUS passes your load data to High-speed Apply Engine, which applies the load records to the Db2 object as if they were SQL INSERT statements. High-speed Apply Engine passes any error conditions that it encounters back to LOAD PLUS, which displays the error information in a LOADPLUS error message.

Requirements for using High-speed Apply Engine with LOADPLUS

To use the High-speed Apply Engine with LOADPLUS, ensure that:

  • LOADPLUS is installed correctly with a valid LOADPLUS password

    To perform an SQLAPPLY load action, BMC does not require a license (or password) for either the BMC AMI Log Master for Db2 product or High-speed Apply Engine.

  • High-speed Apply Engine is installed on the same Db2 subsystem as LOADPLUS and is available through the STEPLIB, JOBLIB, or LINKLIST when LOADPLUS is executed. (High-speed Apply Engine is installed automatically when you install LOADPLUS.)

LOADPLUS options and High-speed Apply Engine parameters

LOADPLUS provides several syntax options and passes the values of those options to the High-speed Apply Engine as configuration parameters.

For more information about the LOADPLUS options, see the LOADPLUS for DB2 documentation.


LOADPLUS syntax option

Corresponding High-speed Apply Engine configuration parameter

APCOLLECTION

CollectionID: specifies a collection name that High-speed Apply Engine uses in any BIND PACKAGE or FREE PACKAGE commands that it issues to execute SQL statements (CollectionID).

APCOMMIT

StatementCount: specifies the number of SQL statements that an apply agent processes before that agent issues a COMMIT statement (StatementCount-parameter).

APMAXAGENTS

MaxAgents: defines the maximum number of agents that High-speed Apply Engine can start for an apply request (MaxAgents).

APMULTIROW

MultiRowInsert: enables or disables High-speed Apply Engine’s processing of multiple row insert actions.

MaxRows: enables you to control how many rows High-speed Apply Engine includes in each multiple-row insert action of an apply request.

APOWNER

BindOwner: specifies an authorization ID that High-speed Apply Engine can use to bind the Db2 plan and packages for the apply request (BindOwner).

APRETRYLIM

RetryLimit: indicates the measurement type used for the RetryValue parameter (RetryLimit).

APRETRYVALUE

RetryValue: specifies the retry limit for each unit of recovery (transaction) in the request (RetryValue).

 

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