SPCORE parameter - Revision history

DCameron: /* SPCORE for Application Subsystem control blocks */

2017-09-06T14:37:51Z

SPCORE for Application Subsystem control blocks

← Older revision		Revision as of 14:37, 6 September 2017
Line 44:		Line 44:
	where: </p>		where: </p>
	<ul>		<ul>
	<li><var>NRMTFILE</var> and <var>NRMTLOCS</var> are <var class="product">Model 204</var> parameters.</li>		<li><var>[[NRMTFILE_parameter\|NRMTFILE]]</var> and <var>[[NRMTLOCS_parameter\|NRMTLOCS]]</var> are <var class="product">Model 204</var> parameters.</li>

	<li><var class="term">filemembers</var> are the files that belong to the subsystem. </li>		<li><var class="term">filemembers</var> are the files that belong to the subsystem. </li>

DCameron: /* Description */

2017-09-06T14:35:06Z

Description

← Older revision		Revision as of 14:35, 6 September 2017
Line 27:		Line 27:
	</ul>		</ul>
	<p>		<p>
	<var>SPCORE</var> sets the minimum amount of reserved virtual storage. The actual amount of reserved storage available to you during the run is <var>SPCORE</var> bytes plus the number of [[Defining the runtime environment (CCAIN)#Calculating region size\|region size]] bytes that are unallocated after <var class="product">Model 204</var> initialization. This actual amount, which you can check with the <var>[[VIEW command\|VIEW]]</var> command, is often considerably greater than the CCAIN <var>SPCORE</var> value you specified. </p>		<var>SPCORE</var> sets the minimum amount of reserved virtual storage. The actual amount of reserved storage available to you during the run is <var>SPCORE</var> bytes plus the number of [[Defining the runtime environment (CCAIN)#Calculating region size\|region size]] bytes that are unallocated after <var class="product">Model 204</var> initialization has completed. This actual amount, which you can check with the <var>[[VIEW command\|VIEW]]</var> command, is often considerably greater than the CCAIN <var>SPCORE</var> value you specified. </p>
	<p>		<p>
	In z/OS, a number of bytes of virtual storage equal to your <var>SPCORE</var> setting is reserved above the line, and the same number is reserved below the line. The BTB amount is ignored in Model 204 7.7 and higher if the <var>[[NUMBUFG parameter\|NUMBUFG]]</var> parameter setting is greater than 0.</p>		In z/OS, a number of bytes of virtual storage equal to your <var>SPCORE</var> setting is reserved above the line, and the same number is reserved below the line. The BTB amount is ignored in Model 204 7.7 and higher if the <var>[[NUMBUFG parameter\|NUMBUFG]]</var> parameter setting is greater than 0.</p>

DCameron: /* Description */

2017-09-06T14:34:04Z

Description

← Older revision		Revision as of 14:34, 6 September 2017
Line 24:		Line 24:
	<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>		<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>
	<li>[[Application_Subsystem_development\|Application Subsystem]] control blocks</li>		<li>[[Application_Subsystem_development\|Application Subsystem]] control blocks</li>
	<li>Dynamically allocated files and printer control blocks</li>		<li>[[Allocating_and_directing_files_dynamically\|Dynamically allocated]] files and printer control blocks</li>
	</ul>		</ul>
	<p>		<p>

DCameron: /* Description */

2017-09-06T14:32:37Z

Description

← Older revision		Revision as of 14:32, 6 September 2017
Line 23:		Line 23:
	<li>Output buffers for directed output ([[USE_command:_Directing_output\|USE]]) data sets, [[Deferred_update_feature\|deferred update]] data sets, or [[Storing_diagnostic_information_(CCASNAP)\|CCASNAP]]</li>		<li>Output buffers for directed output ([[USE_command:_Directing_output\|USE]]) data sets, [[Deferred_update_feature\|deferred update]] data sets, or [[Storing_diagnostic_information_(CCASNAP)\|CCASNAP]]</li>
	<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>		<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>
	<li>Application Subsystem control blocks</li>		<li>[[Application_Subsystem_development\|Application Subsystem]] control blocks</li>
	<li>Dynamically allocated files and printer control blocks</li>		<li>Dynamically allocated files and printer control blocks</li>
	</ul>		</ul>

DCameron: /* Description */

2017-09-06T14:29:57Z

Description

← Older revision		Revision as of 14:29, 6 September 2017
Line 21:		Line 21:
	<ul>		<ul>
	<li>Small control blocks when files are opened</li>		<li>Small control blocks when files are opened</li>
	<li>Output buffers for directed output ([[USE_command:_Directing_output\|USE]]) data sets, [[Deferred_update_feature\|deferred update]] data sets, or CCASNAP</li>		<li>Output buffers for directed output ([[USE_command:_Directing_output\|USE]]) data sets, [[Deferred_update_feature\|deferred update]] data sets, or [[Storing_diagnostic_information_(CCASNAP)\|CCASNAP]]</li>
	<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>		<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>
	<li>Application Subsystem control blocks</li>		<li>Application Subsystem control blocks</li>

DCameron: /* Description */

2017-09-06T14:28:56Z

Description

← Older revision		Revision as of 14:28, 6 September 2017
Line 21:		Line 21:
	<ul>		<ul>
	<li>Small control blocks when files are opened</li>		<li>Small control blocks when files are opened</li>
	<li>Output buffers for directed output ([[USE_command:_Directing_output\|USE]]) data sets, deferred update data sets, or CCASNAP</li>		<li>Output buffers for directed output ([[USE_command:_Directing_output\|USE]]) data sets, [[Deferred_update_feature\|deferred update]] data sets, or CCASNAP</li>
	<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>		<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>
	<li>Application Subsystem control blocks</li>		<li>Application Subsystem control blocks</li>

DCameron: /* Description */

2017-09-06T14:27:04Z

Description

← Older revision		Revision as of 14:27, 6 September 2017
Line 21:		Line 21:
	<ul>		<ul>
	<li>Small control blocks when files are opened</li>		<li>Small control blocks when files are opened</li>
	<li>Output buffers for directed output (USE) data sets, deferred update data sets, or CCASNAP</li>		<li>Output buffers for directed output ([[USE_command:_Directing_output\|USE]]) data sets, deferred update data sets, or CCASNAP</li>
	<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>		<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>
	<li>Application Subsystem control blocks</li>		<li>Application Subsystem control blocks</li>

DCameron: /* Summary */

2017-09-06T14:22:42Z

Summary

← Older revision		Revision as of 14:22, 6 September 2017
Line 11:		Line 11:
	<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: add 7.7 change

2016-08-25T18:46:35Z

add 7.7 change

← Older revision		Revision as of 18:46, 25 August 2016
Line 16:		Line 16:
	==Description==		==Description==
	<p>		<p>
	~~The~~ minimum amount of storage to leave unallocated at the end of <var class="product">Model 204</var> initialization</p>		<var>SPCORE</var> specifies the minimum amount of storage to leave unallocated at the end of <var class="product">Model 204</var> initialization. </p>
	<p>		<p>
	After initialization, <var class="product">Model 204</var> uses for this spare core include: </p>		After initialization, <var class="product">Model 204</var> uses for this spare core include: </p>
Line 27:		Line 27:
	</ul>		</ul>
	<p>		<p>
	<var>SPCORE</var> sets the minimum amount of reserved virtual storage. The actual amount of reserved storage available to you during the run is <var>SPCORE</var> bytes plus the number of region size bytes that are unallocated after <var class="product">Model 204</var> initialization. This actual amount, which you can check with the VIEW command, is often considerably greater than the CCAIN <var>SPCORE</var> value you specified. </p>		<var>SPCORE</var> sets the minimum amount of reserved virtual storage. The actual amount of reserved storage available to you during the run is <var>SPCORE</var> bytes plus the number of [[Defining the runtime environment (CCAIN)#Calculating region size\|region size]] bytes that are unallocated after <var class="product">Model 204</var> initialization. This actual amount, which you can check with the <var>[[VIEW command\|VIEW]]</var> command, is often considerably greater than the CCAIN <var>SPCORE</var> value you specified. </p>
	<p>		<p>
	In z/OS, a number of bytes of virtual storage equal to your <var>SPCORE</var> setting is reserved above the line, and the same number is reserved below the line. </p>		In z/OS, a number of bytes of virtual storage equal to your <var>SPCORE</var> setting is reserved above the line, and the same number is reserved below the line. The BTB amount is ignored in Model 204 7.7 and higher if the <var>[[NUMBUFG parameter\|NUMBUFG]]</var> parameter setting is greater than 0.</p>
	<p>		<p>
	You can use the <var>[[STORCUR parameter\|STORCUR]]</var>, <var>[[STORINIT parameter\|STORINIT]]</var>, and <var>[[STORMAX parameter\|STORMAX]]</var> <var class="product">Model 204</var> parameters to help you determine your site's storage requirements. For more information about storage allocation, see [[Performance monitoring ~~and_tuning~~#Dynamic storage allocation tracking\|Dynamic storage allocation tracking]].</p>		You can use the <var>[[STORCUR parameter\|STORCUR]]</var>, <var>[[STORINIT parameter\|STORINIT]]</var>, and <var>[[STORMAX parameter\|STORMAX]]</var> <var class="product">Model 204</var> parameters to help you determine your site's storage requirements. For more information about storage allocation, see [[Performance monitoring and tuning#Dynamic storage allocation tracking\|Dynamic storage allocation tracking]].</p>
	~~<p>~~
	~~<b>~~SPCORE for Application Subsystem control blocks~~</b></p>~~		====SPCORE for Application Subsystem control blocks====
	<p>		<p>
	Control blocks are allocated from spare core for use by active subsystems. Use the following calculation to determine the number of bytes required for one subsystem, which can include Parallel Query Option/204 remote file subsystem members: </p>		Control blocks are allocated from spare core for use by active [[Application Subsystem development\|subsystems]]. Use the following calculation to determine the number of bytes required for one subsystem, which can include [[PQO: Overview of Parallel Query Option/204\|Parallel Query Option/204]] remote file subsystem members: </p>
	<p class="code">228 + NRMTFILE + NFILES + (40 * <i>SCLASSes</i>) + NRMTLOCS		<p class="code">228 + NRMTFILE + NFILES + (40 * <i>SCLASSes</i>) + NRMTLOCS
	+ (93 * <i>filemembers</i>)		+ (93 * <i>filemembers</i>)
Line 64:		Line 64:
	</ul>		</ul>
	<p>		<p>
	For information on external access to VSAM clusters, see ~~"External file identification" in <var>~~[[DEFINE DATASET command\|~~DEFINE DATASET~~]]~~</var>~~. </p>		For information on external access to VSAM clusters, see [[DEFINE DATASET command##External file identification\|External file identification]]. </p>

	====SPCORE for FLOD exits====		====SPCORE for FLOD exits====
	<p>		<p>
	You must allocate additional working storage space to use the FLOD exit feature. Set the <var>SPCORE</var> parameter to allow 100 bytes per FLOD exit program. </p>		You must allocate additional working storage space to use the [[FLOD exits\|FLOD exit]] feature. Set the <var>SPCORE</var> parameter to allow 100 bytes per FLOD exit program. </p>

	====Calculating increase to SPCORE for MQ/204 statistics====		====Calculating increase to SPCORE for MQ/204 statistics====
	<p>		<p>
	To calculate the additional bytes of <var>SPCORE</var> required to accommodate the MQ/204 statistics, use the following formula:</p>		To calculate the additional bytes of <var>SPCORE</var> required to accommodate the [[MQ/204 overview\|MQ/204]] statistics, use the following formula:</p>
	<p class="code">60 + (NUSERS * 120) = bytes of additional SPCORE required		<p class="code">60 + (NUSERS * 120) = bytes of additional SPCORE required
	</p>		</p>

JAL: remove Sys Man guide

2014-10-30T23:36:20Z

remove Sys Man guide

← Older revision		Revision as of 23:36, 30 October 2014
Line 13:		Line 13:
	<dd><var class="product">Model 204 V6.1</var> or earlier		<dd><var class="product">Model 204 V6.1</var> or earlier
	</dl>		</dl>

	==Description==		==Description==
	<p>The minimum amount of storage to leave unallocated at the end of <var class="product">Model 204</var> initialization</p>		<p>
	<p>After initialization, <var class="product">Model 204</var> uses for this spare core include: </p>		The minimum amount of storage to leave unallocated at the end of <var class="product">Model 204</var> initialization</p>
			<p>
			After initialization, <var class="product">Model 204</var> uses for this spare core include: </p>
	<ul>		<ul>
	<li>		<li>Small control blocks when files are opened</li>
	Small control blocks when files are opened</li>		<li>Output buffers for directed output (USE) data sets, deferred update data sets, or CCASNAP</li>
	<li>		<li>Host Language Interface IFAM1 or IFAM4 application program storage</li>
	Output buffers for directed output (USE) data sets, deferred update data sets, or CCASNAP</li>		<li>Application Subsystem control blocks</li>
	<li>		<li>Dynamically allocated files and printer control blocks</li>
	Host Language Interface IFAM1 or IFAM4 application program storage</li>
	<li>
	Application Subsystem control blocks</li>
	<li>
	Dynamically allocated files and printer control blocks</li>
	</ul>		</ul>
	<p>SPCORE sets the minimum amount of reserved virtual storage. The actual amount of reserved storage available to you during the run is SPCORE bytes plus the number of region size bytes that are unallocated after <var class="product">Model 204</var> initialization. This actual amount, which you can check with the VIEW command, is often considerably greater than the CCAIN SPCORE value you specified. </p>		<p>
	<p>In z/OS, a number of bytes of virtual storage equal to your SPCORE setting is reserved above the line, and the same number is reserved below the line. </p>		<var>SPCORE</var> sets the minimum amount of reserved virtual storage. The actual amount of reserved storage available to you during the run is <var>SPCORE</var> bytes plus the number of region size bytes that are unallocated after <var class="product">Model 204</var> initialization. This actual amount, which you can check with the VIEW command, is often considerably greater than the CCAIN <var>SPCORE</var> value you specified. </p>
	<p>You can use the <var>[[STORCUR parameter\|STORCUR]]</var>, <var>[[STORINIT parameter\|STORINIT]]</var>, and <var>[[STORMAX parameter\|STORMAX]]</var> <var class="product">Model 204</var> parameters to help you determine your site's storage requirements. For more information about ~~dynamic~~ storage allocation ~~tracking~~, see ~~the <var class="book">Model 204 System Manager's Guide~~.~~</var>~~</p>		<p>
	<p><b>SPCORE for Application Subsystem control blocks</b></p>		In z/OS, a number of bytes of virtual storage equal to your <var>SPCORE</var> setting is reserved above the line, and the same number is reserved below the line. </p>
	<p>Control blocks are allocated from spare core for use by active subsystems. Use the following calculation to determine the number of bytes required for one subsystem, which can include Parallel Query Option/204 remote file subsystem members: </p>		<p>
	<p class="code">228 + NRMTFILE + NFILES + (40 * SCLASSes) + NRMTLOCS		You can use the <var>[[STORCUR parameter\|STORCUR]]</var>, <var>[[STORINIT parameter\|STORINIT]]</var>, and <var>[[STORMAX parameter\|STORMAX]]</var> <var class="product">Model 204</var> parameters to help you determine your site's storage requirements. For more information about storage allocation, see [[Performance monitoring and_tuning#Dynamic storage allocation tracking\|Dynamic storage allocation tracking]].</p>
	+ (93 * filemembers)		<p>
	+ ((36 + (7 + SCLASSes) / 8) * (procedures + 1))		<b>SPCORE for Application Subsystem control blocks</b></p>
			<p>
			Control blocks are allocated from spare core for use by active subsystems. Use the following calculation to determine the number of bytes required for one subsystem, which can include Parallel Query Option/204 remote file subsystem members: </p>
			<p class="code">228 + NRMTFILE + NFILES + (40 * <i>SCLASSes</i>) + NRMTLOCS
			+ (93 * <i>filemembers</i>)
			+ ((36 + (7 + <i>SCLASSes</i>) / 8) * (<i>procedures</i> + 1))
	+ 40 bytes for each stopped file or group		+ 40 bytes for each stopped file or group
	</p>		</p>
	<p>where: </p>		<p>
			where: </p>
	<ul>		<ul>
	<li>		<li><var>NRMTFILE</var> and <var>NRMTLOCS</var> are <var class="product">Model 204</var> parameters.</li>
	<var>NRMTFILE</var> and <var>NRMTLOCS</var> are <var class="product">Model 204</var> parameters.</li>
	<li>		<li><var class="term">filemembers</var> are the files that belong to the subsystem. </li>
	filemembers are the files that belong to the subsystem. </li>
	<li>		<li><var class="term">SCLASSes</var> is the number of subsystem user privilege classes.</li>
	<var>SCLASSes</var> is the number of subsystem user privilege classes.</li>
	<li>		<li>40 bytes for each stopped file or group is the number of bytes returned to spare core if the subsystem is stopped or the file or group is started. </li>
	40 bytes for each stopped file or group is the number of bytes returned to spare core if the subsystem is stopped or the file or group is started. </li>
	</ul>		</ul>

	====SPCORE for VSAM clusters====		====SPCORE for VSAM clusters====
	<p>External access to VSAM clusters increases the requirements for dynamically allocated storage available at execution time. The amount of such storage is controlled by SPCORE in the z/OS version of <var class="product">Model 204</var>. z/VSE users can refer to the discussion of ~~the SPCORE parameter in~~ the <var ~~class="book"~~>~~Rocket Model 204 System Manager's Guide~~</var> for further information.</p>		<p>
	<p>SPCORE size requirements for VSAM clusters depend on the following factors: </p>		External access to VSAM clusters increases the requirements for dynamically allocated storage available at execution time. The amount of such storage is controlled by <var>SPCORE</var> in the z/OS version of <var class="product">Model 204</var>. z/VSE users can refer to the discussion of the <var>SPCORE</var> parameter in [[Accessing BSAM and VSAM files#VSAM I/O processing\|VSAM I/O processing]] for further information.</p>
			<p>
			<var>SPCORE</var> size requirements for VSAM clusters depend on the following factors: </p>
	<ul>		<ul>
	<li>		<li>Where the VSAM access method modules are to be loaded. If they are not loaded in the public system area (LPA for z/OS, SVA for z/VSE), approximately 280K bytes are required to load the VSAM modules.</li>
	Where the VSAM access method modules are to be loaded. If they are not loaded in the public system area (LPA for z/OS, SVA for z/VSE), approximately 280K bytes are required to load the VSAM modules.</li>
	<li>		<li>The number of strings (<var>STRNO</var>) for each VSAM file and the <code>BUFFER SPACE</code> parameter defined in the VSAM cluster definition. The product of these parameters determines the amount of storage required for each open VSAM file. </li>
	The number of strings (STRNO) for each VSAM file and the BUFFER SPACE parameter defined in the VSAM cluster definition. The product of these parameters determines the amount of storage required for each open VSAM file. </li>
	</ul>		</ul>
	<p>For information on external access to VSAM clusters, see "External file identification" in <var>[[DEFINE DATASET command\|DEFINE DATASET]]</var>. </p>		<p>
			For information on external access to VSAM clusters, see "External file identification" in <var>[[DEFINE DATASET command\|DEFINE DATASET]]</var>. </p>

	====SPCORE for FLOD exits====		====SPCORE for FLOD exits====
	<p>You must allocate additional working storage space to use the FLOD exit feature. Set the SPCORE parameter to allow 100 bytes per FLOD exit program. </p>		<p>
			You must allocate additional working storage space to use the FLOD exit feature. Set the <var>SPCORE</var> parameter to allow 100 bytes per FLOD exit program. </p>

	====Calculating increase to SPCORE for MQ/204 statistics====		====Calculating increase to SPCORE for MQ/204 statistics====
	<p>To calculate the additional bytes of SPCORE required to accommodate the MQ/204 statistics, use the following formula:</p>		<p>
			To calculate the additional bytes of <var>SPCORE</var> required to accommodate the MQ/204 statistics, use the following formula:</p>
	<p class="code">60 + (NUSERS * 120) = bytes of additional SPCORE required		<p class="code">60 + (NUSERS * 120) = bytes of additional SPCORE required
	</p>		</p>
	<p>The initial 60 bytes are required for the system statistics block (60 bytes for MQ/204 statistics). The 120 bytes for each user includes 60 bytes for the user statistics block and 60 bytes for the since-last statistics block for MQ/204 statistics.</p>		<p>
			The initial 60 bytes are required for the system statistics block (60 bytes for MQ/204 statistics). The 120 bytes for each user includes 60 bytes for the user statistics block and 60 bytes for the since-last statistics block for MQ/204 statistics.</p>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]