SERVSIZE parameter: Difference between revisions
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
==Description== | ==Description== | ||
<p>The size of the server area to be allocated, rounded up to the smallest operating system page size. So, for instance, an online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under Z/OS.</p> | <p>The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for instance, an online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under Z/OS.</p> | ||
<p>SERVSIZE must not be a negative number. If the default value of zero is used, the server area allocated is exactly large enough to contain the tables for the user specified on the same parameter line. If a positive value less than FIXSIZE (user's fixed size) is specified, <var class="product">Model 204</var> increases the value so that the server area allocated is large enough to hold the user's fixed size. </p> | <p>SERVSIZE must not be a negative number. If the default value of zero is used, the server area allocated is exactly large enough to contain the tables for the user specified on the same parameter line. If a positive value less than FIXSIZE (user's fixed size) is specified, <var class="product">Model 204</var> increases the value so that the server area allocated is large enough to hold the user's fixed size. </p> | ||
<p>In a <var class="product">Model 204</var> run that uses server swapping (the typical case for online runs), the size of each server is likely to be limited by the physical device used for swapping. </p> | <p>In a <var class="product">Model 204</var> run that uses server swapping (the typical case for online runs), the size of each server is likely to be limited by the physical device used for swapping. </p> | ||
Revision as of 16:32, 29 October 2014
Maximum size of this server
Summary
- Default value
- 0
- Parameter type
- Server
- Where set
- View only; set on first NSERVS user's parameter lines
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for instance, an online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under Z/OS.
SERVSIZE must not be a negative number. If the default value of zero is used, the server area allocated is exactly large enough to contain the tables for the user specified on the same parameter line. If a positive value less than FIXSIZE (user's fixed size) is specified, Model 204 increases the value so that the server area allocated is large enough to hold the user's fixed size.
In a Model 204 run that uses server swapping (the typical case for online runs), the size of each server is likely to be limited by the physical device used for swapping.
- When a CKD device is used for swapping, server size is limited to the device's cylinder size.
- When an FBA device is used, server size is limited by the amount of virtual memory available to Model 204.
- All servers defined for the run, along with many other blocks of storage, must fit in virtual memory.
- In a run that does not use server swapping (the typical case for batch runs), the servers for all users in the run must fit in virtual memory.
For a description of how the sizes of the fixed table and the variable table are calculated, see Rocket Model 204 System Manager's Guide in the chapter for defining the runtime environment (CCAIN).
Handling SQL statements greater than 32k bytes
When handling an SQL statement that is greater than 32K, you must consider the SERVSIZE parameter: If its value is not large enough, the error message invoked includes the name of the relevant parameter.