Automatic limits
A rule can include customizable limits that control many aspects of your configuration including queries, connections, and sessions.
Rules are configured in the Data Virtualization Manager configuration member
that is shipped in data set member hlq.SAVZEXEC(AVZSIN00).
You can view rules by selecting E (AVZ Admin.) > 2 (AVZ
Parms) from the Primary Option Menu. To
modify a rule, locate the parameter, change its value, and press Enter.
This modifies the parameter for the existing Data Virtualization Manager session. To make the change
permanent, modify the parameter in the AVZSIN00 configuration member.
During installation, a default value is specified for each of the
following limits.
- Overall per session CPU limit
- When this limit is reached, the session is automatically terminated. The security product or a product parameter can provide the limit.
- Per DB2® connection CPU limit
- When this limit is reached, the current Db2 connection is automatically terminated, and all associated Db2 resources are released.
- Per SQL query CPU limit
- When this limit is reached, the current SQL query is automatically terminated, and all associated Db2 resources are released.
- Inactivity time-out
- This limit automatically terminates the session of any user that is inactive for the specified period. Use this limit to minimize security exposures and release resources that are held by inactive users.
- Maximum timer-on limit
- This limit prevents the execution of any SQL statement that exceeds a specified value. The limit prevents excessive resource utilization.
- Maximum rows limit
- This limit restricts the number of rows that a query returns.
- RPC maximum rows limit
- This limit restricts the number of rows that an RPC can generate. This limit is set as a host parameter and is enforced on the host (Data Virtualization Manager server).
- Dropped connection detection
- This mechanism detects clients that failed or are no longer connected to the network. When a dropped connection is detected, the host session is terminated, and all resources are released.
- Lock control facility
- This mechanism detects clients that are holding a Db2 lock (share, update, or exclusive) for an excessive period. When the limit is reached, the session is terminated, and the lock is released.
- Dynamic SQL control facility
- This mechanism allows dynamic SQL to be rejected on the host. Use this mechanism to enforce the use of static SQL.
- Maximum concurrent users
- This limit controls the maximum number of concurrent users and is enforced on the host.