The document discusses page fixing and DB2 bufferpools. It explains that fixing a page means it cannot be removed from central storage, avoiding I/O operations. It recommends fixing DB2 bufferpool pages permanently to save CPU cycles spent on fixing and freeing buffers for I/O, potentially saving over 20% of DB2 CPU time. Monitoring central storage indicators is advised after enabling permanent page fixing.

1. DB2 V8 Bufferpool Pagefixing For saving money in software fees.

4. GETMAIN Macro GETMAIN LC,LA=length addr,A=addr LU,LA=length addr,A=addr VC,LA=length addr,A=addr VU,LA=length addr,A=addr EC,LV=length value,A=addr EU,LV=length value,A=addr VRU,LV=(maximum length value, minimum length value) SP=subpool nmbr

5. IEARV64 Macro IARV64 REQUEST=GETSTOR ,COND=NO ,COND=YES ,SEGMENTS=segments ,FPROT=YES ,FPROT=NO ,SVCDUMPRGN=YES ,SVCDUMPRGN=NO

7. DB2 Bufferpools DB2 Bufferpool is a set of same size I/O buffers in virtual storage. Each buffer contains a DB2 page. The full Bufferpool is contained in z/OS pages (confuse?). DB2 Bufferpools are used to avoid I/O operations in random accesses and to make them more efficient for sequential access. DB2 Bufferpool can be located in the three private areas in an AS or Dataspaces or Hiperspaces (not recommended). Buffers from the Bufferpool must be fixed before any I/O operation and free after the I/O operation end. Those functions consumes lots of CPU cycles.