StatementCount parameter

Usage

The High-speed Apply Engine ignores this parameter when it distributes work between multiple agents based on units of recovery (when the DistributionType parameter is UR).

Specify a value for StatementCount to indicate the number of SQL statements that each agent of a High-speed Apply Engine request processes before issuing a COMMIT statement.

If you specify zero, the High-speed Apply Engine commits all statements as a single transaction in most cases. There are, however, circumstances under which High-speed Apply Engine ignores the statement count and forces commits to occur. These circumstances include:

• Conflict rules
• Use of time as a commit trigger
• Internal resource shortages (see Note 1)
• Tables specified in the input, but nonexistent in target DBMS
• Partitioned tables where the partition key is not included in the SQL

Be aware of the following points about the StatementCount parameter:

• The value of the StatementCount parameter applies to each agent.

  Important

  An internal resource shortage can occur as High-speed Apply Engine runs, depending upon the number of agents and the amount of data that the SQL statements contain.

• If you specify both the StatementCount and Time parameters, High-speed Apply Engine issues a COMMIT statement when either parameter reaches its specified limit. Both counters are reset after a commit or rollback occurs. At the end of a request, High-speed Apply Engine issues a final COMMIT statement as part of termination processing.
• The value of this parameter affects checkpoint and restart processing. For more information, see Usage.
• The BMC LOADPLUS for DB2 passes the value of the APCOMMIT option to High-speed Apply Engine as the StatementCount parameter during an SQLAPPLY load action. For more information, see Integrating.