Select a buffer pool to define, or allocate to the active buffer pool from a list of undefined or inactive buffer pools. A buffer pool is named sequentially and for its page size.
Enter a number for the buffer pool size (VPSIZE) which indicates how many buffers are to be allocated to the active buffer pool.
Specifies that the buffer pool is to be allocated in the DB2 data base services address space (ADMF). This is the default. A subsystem can have a mix of buffer pools in primary and data spaces.
Specifies that the buffer pool is to be allocated in one or more DB2 associated data spaces. There are no associated hiperpools with buffer pools in data spaces. A subsystem can have a mix of buffer pools in primary and data spaces. The maximum size for a single data space buffer pool=8M buffers.
Type a number (HPSIZE) of buffers for the hiperpool:
This is an extension to the virtual buffer pool. Only one hiperpool can exist for each virtual buffer pool. The sum of all hiperpools must not exceed 8GB of storage.
Type a valid percentage of total buffer pool size (valid values=0 to 90). Default=50. This DWQT threshold is a percentage of the virtual buffer pool that might be occupied by unavailable pages, including both updated pages and pages in use.
Type a number that represents the amount of space needed that might be occupied by updated pages from a single data set. The default is 10% of the total buffer pool size (valid values=0 to 90). DB2 does not allow you to set VDWQT to a value greater than DWQT, since any buffers that count toward VDWQT also count toward DWQT.
Specifies that you want VDWQT expressed as a percentage of the total virtual buffer pool size.
Specifies that you want VDWQT expressed as an absolute number.
Type a percentage of total buffer pool size (valid values=0 to 100). This VPSEQT is a percentage of the virtual buffer pool that might be occupied by sequentially accessed pages. These pages can be in any state: updated, in-use, or available; any page might or might not count toward exceeding any other buffer pool threshold. Default value is 80%.
Type a percentage (HPSEQT) of the hiperpool that might be occupied by sequentially accessed pages. The default value is 80%. Valid values are 0% to 100%. Changed pages are not written to the hiperpool so this is the only threshold for hiperpools.
Type a valid percentage (VPPSEQT) of sequential steal threshold (0 to 100). 0 disables parallel processing. This is a portion of the virtual buffer pool that might be used to support parallel operations. It is measured as a percentage of the sequential steal threshold (VPSEQT). Default value is 50% of the sequential steal threshold (VPSEQT).
Type a valid percentage (VPXPSEQT) of parallel sequential threshold (0 to 100). 0 prohibits the buffer pool from assisting another DB2 with parallel processing. This is a threshold value that is valid only for data sharing systems. Otherwise, it is ignored. It is a portion of the buffer pool that might be used to assist with parallel operations initiated from another DB2 in the data sharing group. It is measured as a percentage of parallel sequential threshold (VPPSEQT).
Specifies that (CASTOUT) MVS discards data cached in hiperpool when a shortage of expanded storage arises. When this data is discarded, hiperspace backing expanded storage pages is released.
Specifies no CASTOUT. MVS tries to keep data cached in the hiperpool.
Specifies to manage the virtual buffer pool buffers using the least recently used (LRU) of page stealing algorithm. This is the default.
Specifies to manage the virtual buffer pool buffers using the first in first out (FIFO) page stealing algorithm.
Submits the data in the window and closes the window.
Displays the SQL statements that are generated by your choices in this notebook.
Cancels any unsaved changes and closes the notebook or window.
The buffer pool is long-term fixed in real storage. Page buffers are fixed when they are first used after the buffer pool is allocated or expanded, and remain fixed until the buffer pool is deallocated or contracted.
The buffer pool is not long-term fixed in real storage. Page buffers are fixed and unfixed in real storage for each I/O and GBP operation. This is the default behaviour.