Alternate buffer pools can be defined only during MUF startup. They are defined with a new MUF startup option of BUFFER_POOL_DEF. One BUFFER_POOL_DEF statement is used to define each alternate buffer pool.
During MUF startup or after MUF is enabled, by using various console-like APIs, you can define areas that are to use an alternate pool instead of the four standard pools. The statement is:
BUFFER_POOL_CONTENT pool-name,item
Both parameters on this statement are required.
The pool-name matches a pool name specified on the MUF startup option BUFFER_POOL_DEF.
At MUF startup, the item is a single entry or a list of entries separated by a comma. Each entry can be an area name and DBID (examples are IXX2 and PAY5000), or it can be a DBID (such as 400), or it can be a range of bases (for example, 300-800). If the area name is not provided, all areas of that type for the DBID or DBIDs specified are placed in the defined pool.
If the content is changed after the MUF is up, the ‘item’ can only be specified as a single item or a DBID range. A database cannot be open at the time the BUFFER_POOL_CONTENT statement is processed. The pairing of the buffer pool with the area occurs during an open of the database where it is not currently open. The open fails if the block size needed is larger than the defined pool size.
For an individual DBID for each buffer type, you can only specify an alternate buffer pool at the area level or at the DBID level, but not both. For example, specifying DATAnn,PAY001 and DATAnn,1 is not allowed.
Just as different data areas in a database can be defined for different buffer pools, multiple dataset index areas with the IXX can go in one pool, and a possible I22 in a second pool, and a possible I01 in a third pool.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|