QIBM_SYSTEM_LIMITS global variables
To prevent excess storage consumption within the SYS2/SYSLIMTBL table, DB2 for i will automatically delete (or prune) rows.
DB2 for i supplied global variables guide the pruning action. For each type of limit, there are two global variables. The pruning variable is used to choose how many of the most recently logged entries should be retained. The high point variable is used to choose how many of the highest consumption value entries should be retained.
The following are the names of the global variables and the limit that is shipped for each one. The schema is SYSIBMADM.
- QIBM_SYSTEM_LIMITS_PRUNE_BY_ASP
- 100
- QIBM_SYSTEM_LIMITS_PRUNE_BY_JOB
- 50
- QIBM_SYSTEM_LIMITS_PRUNE_BY_OBJECT
- 20
- QIBM_SYSTEM_LIMITS_PRUNE_BY_SYSTEM
- 100
- QIBM_SYSTEM_LIMITS_SAVE_HIGH_POINTS_BY_ASP
- 25
- QIBM_SYSTEM_LIMITS_SAVE_HIGH_POINTS_BY_JOB
- 5
- QIBM_SYSTEM_LIMITS_SAVE_HIGH_POINTS_BY_OBJECT
- 5
- QIBM_SYSTEM_LIMITS_SAVE_HIGH_POINTS_BY_SYSTEM
- 25
You can redefine any of the global variable values to change a limit on your system. After the variable is redefined, the new value takes effect after the next system IPL.
Use IBM
i Navigator to generate SQL for the global variable and use the OR
REPLACE option to recreate it with a different default. For example,
to keep 50 of the most recently logged rows for all system types of
limits, use the following SQL statement:
CREATE OR REPLACE VARIABLE SYSIBMADM.QIBM_SYSTEM_LIMITS_PRUNE_BY_SYSTEM
INTEGER
DEFAULT 50