SERVSIZE parameter - Revision history

RPuszewski at 02:05, 26 January 2021

2021-01-26T02:05:40Z

← Older revision		Revision as of 02:05, 26 January 2021
Line 5:		Line 5:
	<dt>Default value		<dt>Default value
	<dd>65536 as of version 7.7 (and zap maintenance in 7.6, 7.5, and 7.4); formerly, 0		<dd>65536 as of version 7.7 (and zap maintenance in 7.6, 7.5, and 7.4); formerly, 0
			<dd>0 as of version 7.9
	<dt>Parameter type		<dt>Parameter type
	<dd>Server		<dd>Server
Line 18:		Line 19:
	<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 example, an Online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</p>		The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for example, an Online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</p>
			<p> Under 7.9, if the entire server is placed above the bar using <var>[[SERVGA parameter\|SERVGA]]</var> and/or <var>[[SERVNSA parameter\|SERVNSA]]</var>, this parameter should be omitted (or set to zero) in order to avoid below the bar allocation.</p>
	<p>		<p>
	<var>SERVSIZE</var> must not be a negative number. If the default value 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 <var>[[FIXSIZE parameter\|FIXSIZE]]</var> (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>		<var>SERVSIZE</var> must not be a negative number. If the default value 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 <var>[[FIXSIZE parameter\|FIXSIZE]]</var> (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>

DCameron: /* Handling SQL statements greater than 32K bytes */

2017-05-30T13:50:11Z

Handling SQL statements greater than 32K bytes

← Older revision		Revision as of 13:50, 30 May 2017
Line 36:		Line 36:
	====Handling SQL statements greater than 32K bytes====		====Handling SQL statements greater than 32K bytes====
	<p>		<p>
	When handling an SQL statement that is greater than 32K, you must consider the <var>SERVSIZE</var> parameter: If its value is not large enough, the error message invoked includes the name of the relevant parameter whose value needs to be increased (<var>LSTBL</var>, <var>LNTBL</var>, etc.).</p>		When handling an SQL statement that is greater than 32K, you must consider the <var>SERVSIZE</var> parameter: If its value is not large enough, the error message invoked includes the name of the relevant parameter whose value needs to be increased (<var>[[LSTBL_parameter\|LSTBL]]</var>, <var>[[LNTBL_parameter\|LNTBL]]</var>, etc.).</p>

	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Summary */

2017-05-30T13:39:26Z

Summary

← Older revision		Revision as of 13:39, 30 May 2017
Line 12:		Line 12:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V6.1</var> or earlier		<dd><var class="product">Model 204 V2.1</var> or earlier
	</dl>		</dl>

JAL: typo

2016-08-10T23:04:29Z

typo

← Older revision		Revision as of 23:04, 10 August 2016
Line 17:		Line 17:
	==Description==		==Description==
	<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 example, an ~~online~~ with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</p>		The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for example, an Online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</p>
	<p>		<p>
	<var>SERVSIZE</var> 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 <var>[[FIXSIZE parameter\|FIXSIZE]]</var> (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>		<var>SERVSIZE</var> must not be a negative number. If the default value 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 <var>[[FIXSIZE parameter\|FIXSIZE]]</var> (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>		<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>		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>
	<ul>		<ul>
	<li>When a CKD device is used for swapping, server size is limited to the device's cylinder size. </li>		<li>When a CKD device is used for swapping, server size is limited to the device's cylinder size. </li>

JAL: /* Handling SQL statements greater than 32K bytes */ add small clarification

2016-08-10T22:56:20Z

Handling SQL statements greater than 32K bytes: add small clarification

← Older revision		Revision as of 22:56, 10 August 2016
Line 36:		Line 36:
	====Handling SQL statements greater than 32K bytes====		====Handling SQL statements greater than 32K bytes====
	<p>		<p>
	When handling an SQL statement that is greater than 32K, you must consider the <var>SERVSIZE</var> parameter: If its value is not large enough, the error message invoked includes the name of the relevant parameter.</p>		When handling an SQL statement that is greater than 32K, you must consider the <var>SERVSIZE</var> parameter: If its value is not large enough, the error message invoked includes the name of the relevant parameter whose value needs to be increased (<var>LSTBL</var>, <var>LNTBL</var>, etc.).</p>

	[[Category:Parameters]]		[[Category:Parameters]]

JAL: /* Summary */ typo

2016-08-10T22:46:28Z

Summary: typo

← Older revision		Revision as of 22:46, 10 August 2016
Line 4:		Line 4:
	<dl>		<dl>
	<dt>Default value		<dt>Default value
	<dd>65536 as of version 7.7 (and zap maintenance in 7.6, 7.5, and 7.4~~. Formerly~~, ~~the default was~~ 0.		<dd>65536 as of version 7.7 (and zap maintenance in 7.6, 7.5, and 7.4); formerly, 0
	<dt>Parameter type		<dt>Parameter type
	<dd>Server		<dd>Server

JAL: /* Summary */ new default

2016-08-10T22:44:42Z

Summary: new default

← Older revision		Revision as of 22:44, 10 August 2016
Line 4:		Line 4:
	<dl>		<dl>
	<dt>Default value		<dt>Default value
	<dd>0		<dd>65536 as of version 7.7 (and zap maintenance in 7.6, 7.5, and 7.4. Formerly, the default was 0.
	<dt>Parameter type		<dt>Parameter type
	<dd>Server		<dd>Server

JAL: add links

2016-08-10T19:26:04Z

add links

← Older revision		Revision as of 19:26, 10 August 2016
Line 8:		Line 8:
	<dd>Server		<dd>Server
	<dt>Where set		<dt>Where set
	<dd>View only; set on first NSERVS user's parameter lines		<dd>View only; set on first <var>[[NSERVS parameter\|NSERVS]]</var> user's parameter lines
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All
Line 19:		Line 19:
	The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for example, an online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</p>		The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for example, an online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</p>
	<p>		<p>
	<var>SERVSIZE</var> 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 <var>FIXSIZE</var> (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>		<var>SERVSIZE</var> 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 <var>[[FIXSIZE parameter\|FIXSIZE]]</var> (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>		<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>		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>
Line 34:		Line 34:
	For a description of how the sizes of the fixed table and the variable table are calculated, see [[Defining the runtime environment (CCAIN)#Sizing user server areas\|Sizing user server areas]].</p>		For a description of how the sizes of the fixed table and the variable table are calculated, see [[Defining the runtime environment (CCAIN)#Sizing user server areas\|Sizing user server areas]].</p>

	====Handling SQL statements greater than ~~32k~~ bytes====		====Handling SQL statements greater than 32K bytes====
	<p>		<p>
	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.</p>		When handling an SQL statement that is greater than 32K, you must consider the <var>SERVSIZE</var> parameter: If its value is not large enough, the error message invoked includes the name of the relevant parameter.</p>

	[[Category:Parameters]]		[[Category:Parameters]]

JAL: remove Category:Server Parameters

2015-01-15T22:09:36Z

remove Category:Server Parameters

← Older revision		Revision as of 22:09, 15 January 2015
Line 38:		Line 38:
	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.</p>		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.</p>

	~~[[Category:Server parameters]]~~
	[[Category:Parameters]]		[[Category:Parameters]]

JAL: remove Sys Man guide

2014-10-30T23:15:24Z

remove Sys Man guide

← Older revision		Revision as of 23:15, 30 October 2014
Line 16:		Line 16:

	==Description==		==Description==
	<p>The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for example, an online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</p>		<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>		The size of the server area to be allocated, rounded up to a multiple of the smallest operating system page size. So, for example, an online with servers set to 750000 will show 753664 (the next highest multiple of the 4096 page size) under z/OS.</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>
			<var>SERVSIZE</var> 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 <var>FIXSIZE</var> (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>
	<ul>		<ul>
	<li>		<li>When a CKD device is used for swapping, server size is limited to the device's cylinder size. </li>
	When a CKD device is used for swapping, server size is limited to the device's cylinder size. </li>
	<li>		<li>When an FBA device is used, server size is limited by the amount of virtual memory available to <var class="product">Model 204</var>.</li>
	When an FBA device is used, server size is limited by the amount of virtual memory available to <var class="product">Model 204</var>.</li>
	<li>		<li>All servers defined for the run, along with many other blocks of storage, must fit in virtual memory.</li>
	All servers defined for the run, along with many other blocks of storage, must fit in virtual memory.</li>
	<li>		<li>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.</li>
	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.</li>
	</ul>		</ul>
	<p>For a description of how the sizes of the fixed table and the variable table are calculated, see ~~<var>Rocket Model 204 System Manager's Guide</var> in the chapter for defining~~ the runtime environment (CCAIN).</p>		<p>
			For a description of how the sizes of the fixed table and the variable table are calculated, see [[Defining the runtime environment (CCAIN)#Sizing user server areas\|Sizing user server areas]].</p>

	====Handling SQL statements greater than 32k bytes====		====Handling SQL statements greater than 32k bytes====
	<p>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.</p>		<p>
			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.</p>

	[[Category:Server parameters]]		[[Category:Server parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]