MAXBUF parameter: Difference between revisions
m (Automatically generated page update) |
(Automatically generated page update) |
||
Line 24: | Line 24: | ||
</p> | </p> | ||
<p>The prefetch feature is described in the <var>Model 204 User Language Manual</var> and in the <var>Model 204 System Manager's Guide</var>. </p> | <p>The prefetch feature is described in the <var>Model 204 User Language Manual</var> and in the <var>Model 204 System Manager's Guide</var>. </p> | ||
[[Category:System | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] |
Revision as of 14:38, 19 April 2013
Summary
- Default value
- 256
- Parameter type
- System
- Where set
- On User 0's parameter line
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
The maximum number of in-memory file page buffers that can be allocated during Model 204 initialization
The actual number of pages allocated to the disk buffer pool can be identified by viewing the parameter NUMBUF.
If NLRUQ is set greater than 1, then the value of MAXBUF is rounded up to a multiple of NLRUQ. The maximum setting is 300000. Also, you must set XMEMOPT=X'02' to get more than about 15000-18000 or so actually allocated to NUMBUF.
If MAXBUF is set to a value less than MINBUF, MAXBUF is automatically reset to the value of MINBUF and the following message is issued:
M204.1190: MAXBUF SET TO SAME VALUE AS MINBUF -%C
You can use the MONITOR DISKBUFF command to display, from each table of each file, the number of pages that are currently located in the disk buffers.
If the prefetch feature is enabled (SEQOPT=1), then the MAXBUF parameter must be resized based on the following formula:
MAXBUF = NUSERS * (4 + 2 * (Maximum FOR EACH RECORD loop nest level))
The prefetch feature is described in the Model 204 User Language Manual and in the Model 204 System Manager's Guide.