Thread solution
The thread solution detects thread or connection shortages and increases the number of threads that are available.
How the solution works
The thread solution works in the following way:
- BMC AMI Ops monitors the following types of threads for Db2 thread shortage conditions:
- local
- remote
- TSO
- batch
- remote concurrent
- When a shortage is detected, BMC AMI Ops notifies BMC AMI OpsA to execute the thread solution.
BMC AMI OpsA issues an ALERT.
- If the operator replied YES to the ALERT or if you are running in REPAIR mode, the thread solution issues a MAXTHDS element command to increase the number of threads available. The increase is applied to the maximum thread count value for the type of ALERT that has been issued.
For example, if the ALERT is issued for remote threads, the maximum value for remote threads is increased but the maximum value for the other types of threads remains the same.
The number is increased by the percentage you specified in QDTINIT1.
For more information about the MAXTHDS element command, see MAXTHDS— Maximum number of threads.
What to customize in QDTINIT1
The Db2 Thread Solution section in QDTINIT1 contains two sets of variables that you can customize—global and subsystem.
The global variables are required. The subsystem variables are optional.
Customizing the global variables
The first set of variables in the Db2 Thread Solution section are the global variables. These variables are required and contain default values. The values that are specified
for the global variables affect all of the Db2 subsystems.
You can leave the values as they are, or you can change them. Thread solution variables describes each variable.
Customizing the subsystem variables
The second set of variables in the Db2 Thread Solution section are the subsystem variables. These variables are optional. If you specify them, they affect only the specified subsystem. Subsystem specific values override global values.
- To specify subsystem variables, replace #### in the variable names and REXX statements with the Db2 subsystem ID you want the values to affect.
- To specify values for additional subsystems, copy the variables and the REXX statements in the subsystem area, paste them after the existing statements, and change the Db2 subsystem ID.
Thread solution variables describes each variable.
Global and subsystem variable definitions
Thread solution variables lists and describes the variables that are used in the thread solution.
Thread solution variables
Variable name | Description | Default global value |
|---|---|---|
DT_MAXTHDS_MODE.* | Mode in which you want to run the solution Specify ADVISOR or REPAIR. For more information, see Available modes. | ADVISOR |
DT_MAXTHDS_LIMIT.* | Number of times the solution will run For example, if you set this to 5, the solution will execute the OPERTUNE MAXTHDS element command up to five times. The solution will not execute the command a sixth time. | 0 |
DT_MAXTHDS_PERCENT.* | Percentage by which the solution increases the number of threads Each time the solution runs, the maximum number of threads increases by this percentage of the current value. For example, you set the percentage to 10. Originally, there are 100 threads. The first time that the solution runs, 10 threads are added, making the value 110. The second time that the solution runs, 11 threads are added, making the value 121. The increase is applied to the maximum thread count value for the type of ALERT that is issued. For example, if the ALERT is for TSO threads, the maximum for TSO threads is increased but the maximum for the other types of threads remains the same. | 10 |
In the variable name, replace * with one of the following values:
- $ALL to specify global values
- a Db2 subsystem ID to specify subsystem variables
Related topic