Operational requirements
Related topics
Db2 authorizations for plans, packages, and collections
This topic describes requirements and considerations for using the High-speed Apply Engine. For information about installing High-speed Apply Engine, see Installing High-speed Apply Engine.
Authorization requirements
The following libraries must be APF-authorized:
- High-speed Apply load libraries
- Any libraries that you reference in the apply request (in the STEPLIB DD statements)
Also, the user ID that submits the apply request must have the appropriate authorizations to run the request. For more information, see DB2 authorizations.
Operating system requirements
If the input source for the apply request is a data set, the data set must be present in the ICF catalog of the operating system.
High-speed Apply Engine must be installed on the same operating system logical partition (LPAR) as the target Db2 subsystem.
Db2 thread requirements
To run an apply request, the High-speed Apply Engine updates the target tables through Db2. The database can continue to run while High-speed Apply Engine performs its updates, so you can update the target tables while they are online. The access method for Db2 is the Call Attach Facility (CAF). Because High-speed Apply Engine uses multiple connections to the database, the target Db2 subsystem must have enough threads available for the apply request (for more information, see Operational considerations).
at least two threads are available, or as many threads as the initial number of agents that High-speed Apply Engine specifies. For more information about setting the initial number of agents, see InitialAgents. For more information about the maximum number of agents, see MaxAgents.
Restart table requirements
A new installation of High-speed Apply creates a new restart table. High-speed Apply doesn't migrate restart tables from earlier versions. If you have an earlier version of High-speed Apply Engine installed, any restarts must be completed on the original version before switching to a new version.
The restart table for an apply request must reside on the same Db2 subsystem as the target tables.
LOADPLUS requirements
If High-speed Apply Engine is called by the LOADPLUS for DB2 product, then High-speed Apply Engine must be installed on the same Db2 subsystem as LOADPLUS, and must be available through the STEPLIB, JOBLIB, or LINKLIST when LOADPLUS is run.
Db2 authorization requirements
To run SQL or logical log input, the user ID that runs the High-speed Apply Engine must have the following Db2 authorizations:
- EXECUTE privilege for the plan that High-speed Apply Engine uses to access its own restart tables and the catalog (see PublicPlan).
- EXECUTE privilege for the restart package.
- Appropriate table privileges such as INSERT, UPDATE, or DELETE for the target tables. The specific privileges depend on the actions that the apply request performs.
Appropriate privileges to bind or administer plans, packages, and collections. High-speed Apply Engine provides several methods to grant these privileges. Some techniques avoid granting bind privileges to the user ID that runs High-speed Apply Engine. For more information, see Db2 authorizations for plans, packages, and collections.