MaxAgents

Usage

Specify a value representing the maximum number of agents.

Consider the following points about the MaxAgents parameter:

• High-speed Apply Engine starts with the number of agents specified by the InitialAgents parameter and then starts as many agents as it needs, up to the number specified by the MaxAgents parameter.
• Each started agent requires a connection to the target database. If there are not enough threads available to support the maximum number of agents, High-speed Apply Engine continues processing using the current number of agents, but it does not attempt to start up any more agents.
• The BMC LOADPLUS for DB2 passes the value of the APMAXAGENTS option to High-speed Apply Engine as the MaxAgents parameter during an SQLAPPLY load action. For more information, see Integrating.
• Use this parameter to prevent High-speed Apply Engine from using more database resources than you desire. For example, if your input comes from an ad hoc process, the amount can be greater than expected. Specify this parameter to ensure that High-speed Apply Engine does not use more database connections (and by extension, more resources) than your environment can tolerate.
• Under distribution by UR, High-speed Apply Engine is more likely to use the maximum number of agents available (especially if your input contains a large number of transactions with many dependencies between them). Use this parameter to limit the database connections.
• You can use this parameter to disable multi-threaded execution. If you specify MaxAgents as 1, High-speed Apply Engine does not use multiple agents. (You must specify MaxAgents as 1 if the value of the CommitOnDemand parameter is Yes.)
• There is a limitation with AIX on the amount of shared memory segments that any one process can have. For Db2 LUW on AIX, you can only have up to 8 agents.