Defining the runtime environment (CCAIN) - Revision history

ATitelbaum: /* ATB storage for procedure pages */

2022-03-25T21:20:10Z

ATB storage for procedure pages

← Older revision		Revision as of 21:20, 25 March 2022
Line 1,611:		Line 1,611:
	Procedure text pages, located in Table D, are also eligible to reside in the ATB buffer pool. Each SOUL procedure is stored in one or more procedure text pages, the initial page of which is pointed to by the procedure dictionary. (Pages from the procedure dictionary, which is also stored in Table D, are read into the BTB buffer pool.)</p>		Procedure text pages, located in Table D, are also eligible to reside in the ATB buffer pool. Each SOUL procedure is stored in one or more procedure text pages, the initial page of which is pointed to by the procedure dictionary. (Pages from the procedure dictionary, which is also stored in Table D, are read into the BTB buffer pool.)</p>

	<p>In a development environment where procedure page volume is high and where <var>NUMBUFG</var> is allocated, you might need to increase <var>NUMBUFG</var> to ~~accomodate~~ the procedure text pages. In this case, if BTB buffers are also being used (Model 204 version less than 7.7), you can reduce the <var>MAXBUF</var> parameter by the same amount you increased <var>NUMBUFG</var>.</p>		<p>In a development environment where procedure page volume is high and where <var>NUMBUFG</var> is allocated, you might need to increase <var>NUMBUFG</var> to accommodate the procedure text pages. In this case, if BTB buffers are also being used (Model 204 version less than 7.7), you can reduce the <var>MAXBUF</var> parameter by the same amount you increased <var>NUMBUFG</var>.</p>

	====ATB storage for screens and images====		====ATB storage for screens and images====

JAL: link repair

2017-07-11T19:56:16Z

link repair

← Older revision		Revision as of 19:56, 11 July 2017
Line 613:		Line 613:
	<li> Spare core (<var>SPCORE</var>) specification, the default is 8192 bytes		<li> Spare core (<var>SPCORE</var>) specification, the default is 8192 bytes

	<p>Increase the default, if you use deferred update, the FLOD exit (FLODXT) feature, directed output, or active subsystems. Additional memory is also required to open sequential data sets. The requirements for FLODXT are given under <var>SPCORE</var> in [[#~~Common runtime~~ parameters\|Common runtime parameters]]. </p></li>		<p>Increase the default, if you use deferred update, the FLOD exit (FLODXT) feature, directed output, or active subsystems. Additional memory is also required to open sequential data sets. The requirements for FLODXT are given under <var>SPCORE</var> in the [[#User 0 parameters\|"Common runtime parameters" table]]. </p></li>

	<li> Number of buffers used for each server		<li> Number of buffers used for each server

JAL: link repair

2017-06-05T23:14:12Z

link repair

← Older revision		Revision as of 23:14, 5 June 2017
Line 988:		Line 988:
	<tr><td><p><var>[[XMEMSVC parameter\|XMEMSVC]]</var></p></td>		<tr><td><p><var>[[XMEMSVC parameter\|XMEMSVC]]</var></p></td>
	<td>		<td>
	<p>SVC number of the <var class="product">Model 204</var> Cross-Memory Services module ([[~~Defining the user environment (CCAIN)~~#~~204xsvc~~\|M204XSVC]]). Installation of this module with an SVC is deprecated as of Model 204 7.5. <var>XMEMSVC</var> coordinates with <var>XMEMOPT</var>. The default is 0. </p>		<p>SVC number of the <var class="product">Model 204</var> Cross-Memory Services module ([[Cross-memory facilities CRAM and M204XSVC#M204XSVC\|M204XSVC]]). Installation of this module with an SVC is deprecated as of Model 204 7.5. <var>XMEMSVC</var> coordinates with <var>XMEMOPT</var>. The default is 0. </p>
	<p>		<p>
	M204XSVC is also used by:</p>		M204XSVC is also used by:</p>

ELowell: /* Calculating fixed table size */

2017-04-25T16:46:36Z

Calculating fixed table size

← Older revision		Revision as of 16:46, 25 April 2017
Line 1,793:		Line 1,793:
	+ (LOUTPB)dwr		+ (LOUTPB)dwr
	+ (((NGROUP + 12) * (NRMTFILE + NFILES + 1)) + (NRMTFILE + 1))dwr		+ (((NGROUP + 12) * (NRMTFILE + NFILES + 1)) + (NRMTFILE + 1))dwr
	+ (((NORQS*3) + 2)dwr		+ ((NORQS*3) + 2)dwr
	+ (3 * ERRMSGL)		+ (3 * ERRMSGL)
	</p>		</p>

ELowell: /* Calculating fixed table size */

2017-04-21T16:56:44Z

Calculating fixed table size

← Older revision		Revision as of 16:56, 21 April 2017
Line 1,788:		Line 1,788:
	<p class="code">Fixed table size = 2520		<p class="code">Fixed table size = 2520
	+ ((MAXINCL+6) * 80)dwr		+ ((MAXINCL+6) * 80)dwr
	+ ((LAUDPROC + 9) * MAXINCL-1)dwr		+ ((LAUDPROC + 9) * (MAXINCL-1))dwr
	+ (LIBUFF + 4)		+ (LIBUFF + 4)
	+ (LOBUFF + 5)dwr		+ (LOBUFF + 5)dwr

ELowell: /* Calculating fixed table size */

2017-04-19T22:55:42Z

Calculating fixed table size

← Older revision		Revision as of 22:55, 19 April 2017
Line 1,794:		Line 1,794:
	+ (((NGROUP + 12) * (NRMTFILE + NFILES + 1)) + (NRMTFILE + 1))dwr		+ (((NGROUP + 12) * (NRMTFILE + NFILES + 1)) + (NRMTFILE + 1))dwr
	+ (((NORQS*3) + 2)dwr		+ (((NORQS*3) + 2)dwr
	+ (3 * (ERRMSGL ~~- 80)~~)		+ (3 * ERRMSGL)
	</p>		</p>
	<p>		<p>

ELowell: /* Calculating fixed table size */

2017-04-18T17:06:59Z

Calculating fixed table size

← Older revision		Revision as of 17:06, 18 April 2017
Line 1,787:		Line 1,787:

	<p class="code">Fixed table size = 2520		<p class="code">Fixed table size = 2520
	+ ((LAUDPROC + 9) * 4)dwr		+ ((MAXINCL+6) * 80)dwr
			+ ((LAUDPROC + 9) * MAXINCL-1)dwr
	+ (LIBUFF + 4)		+ (LIBUFF + 4)
	+ (LOBUFF + 5)dwr		+ (LOBUFF + 5)dwr

ELowell: /* Calculating fixed table size */

2017-04-14T19:42:35Z

Calculating fixed table size

← Older revision		Revision as of 19:42, 14 April 2017
Line 1,876:		Line 1,876:
	<p>40</p></td>		<p>40</p></td>
	<td>		<td>
	<p>90+LAUDPROC bytes per ~~MAXINCL~~</p></td>		<p>90+LAUDPROC bytes per INCLUDE level</p></td>
	</tr>		</tr>

ELowell: /* Calculating fixed table size */

2017-04-14T19:37:08Z

Calculating fixed table size

@@ Line 1,866: / Line 1,866: @@
 <td>
 <p>Bytes</p></td>
 </tr>

ELowell: /* Sizing user server areas */ - fixed ONLINE monitoring link

2017-04-11T21:29:59Z

Sizing user server areas: - fixed ONLINE monitoring link

← Older revision		Revision as of 21:29, 11 April 2017
Line 1,749:		Line 1,749:
	The default size of all user server areas is set on User 0's parameter line. If the default is used, the allocated server area is exactly large enough to contain the tables for each user specified on each user's parameter line. If <var>[[SERVSIZE parameter\|SERVSIZE]]</var> is also specified on a particular user's parameter line, the default is overridden for that user.</p>		The default size of all user server areas is set on User 0's parameter line. If the default is used, the allocated server area is exactly large enough to contain the tables for each user specified on each user's parameter line. If <var>[[SERVSIZE parameter\|SERVSIZE]]</var> is also specified on a particular user's parameter line, the default is overridden for that user.</p>

	<p>The value of <var>SERVSIZE</var> must be as large as, or larger than, the user's aggregate table size. It is calculated by examining the user's server area requirements and monitoring the system statistics (described in [[~~Controlling system operations (CCAIN)#ONLINE monitoring\|~~ONLINE monitoring]]) that provide information about the installation work load. The following formula gives the approximate size:</p>		<p>The value of <var>SERVSIZE</var> must be as large as, or larger than, the user's aggregate table size. It is calculated by examining the user's server area requirements and monitoring the system statistics (described in [[ONLINE monitoring]]) that provide information about the installation work load. The following formula gives the approximate size:</p>

	<p class="syntax">SERVSIZE = <span class="term">fixed-table-size</span> + <span class="term">variable-table-size</span>		<p class="syntax">SERVSIZE = <span class="term">fixed-table-size</span> + <span class="term">variable-table-size</span>