Product features and functions
High-speed Apply Engine runs on the following database management systems (DBMSs) and operating system platforms:
IBM DB2 LUW on mainframe operating systems (such as z/OS)
IBM DB2 LUW on UNIX
IBM DB2 LUW on Microsoft Windows
Oracle on UNIX
Oracle on Windows
As a component, High-speed Apply Engine provides the following functionality to BMC products:
The execution of generated SQL statements for Log Master for DB2.
The LOAD RESUME YES SHRLEVEL CHANGE SQLAPPLY load action (referred to as an SQLAPPLY load action) for LOADPLUS for DB2.
The High-speed Apply Engine provides many features in addition to those used by these products. To use any of these additional features, run High-speed Apply Engine independently of the accompanying product. When High-speed Apply Engine is distributed with BMC Software products, installation of the products includes installation of High-speed Apply Engine.
The High-speed Apply Engine accepts the following sources as input for an apply request:
SQL statements (including SQL generated by Log Master for DB2 or any standard SQL processor)
logical log files created by Log Master for DB2
High-speed Apply Engine provides the following advanced features to improve the performance of your apply request:
Multi-threaded execution: Use multiple agents to increase parallelism and improve performance.
Restart processing: If an apply request fails, continue processing from the point of failure. Avoid repeating transactions that have already been processed.
Conflict resolution rules: Use flexible parameters to define precise responses to SQL codes or database messages during execution. Customize the apply request to match your data with a variety of responses, including the ability to write a statement or unit of recovery to a separate file for subsequent examination or execution.
Using SQL or logical log input, you can use High-speed Apply Engine for the following tasks:
Apply changes to a database as part of an apply request
Migrate data between databases
(DB2 only) Include an apply request as part of a transaction recovery process for a DB2 database
The apply request runs as a batch job on the operating system. This implementation allows you to schedule requests as part of your normal recovery process. During the recovery process, you can use SQL to reverse (undo) the effects of incorrect transactions, or to re-apply (redo) correct transactions after performing a DB2 recovery.
When conflicts occur during the recovery process, you can use conflict resolution rules to specify a different resolution for each type of conflict that might occur.