Runtime environment for SQL processing - Revision history

Mlarocca: /* CCAIN parameters to support Model 204 SQL processing */

2017-11-09T19:17:35Z

CCAIN parameters to support Model 204 SQL processing

← Older revision		Revision as of 19:17, 9 November 2017
Line 60:		Line 60:

	<tr><td><var>[[LIBUFF parameter\|LIBUFF]]</var></td>		<tr><td><var>[[LIBUFF parameter\|LIBUFF]]</var></td>
	<td>Set to 5000; adjust to match <var>~~SQLBUFSZ~~</var></td></tr>		<td>Set to 5000; adjust to match <var>SQLIQBSZ</var></td></tr>

	<tr><td><var>[[LNTBL parameter\|LNTBL]]</var></td>		<tr><td><var>[[LNTBL parameter\|LNTBL]]</var></td>

ELowell at 23:59, 11 October 2016

2016-10-11T23:59:04Z

← Older revision		Revision as of 23:59, 11 October 2016
Line 322:		Line 322:
	<p>		<p>
	In Model 204, <var>DATALEN</var> has a maximum setting of 32K. It should be set to the average amount of data in any request in your network.</p>		In Model 204, <var>DATALEN</var> has a maximum setting of 32K. It should be set to the average amount of data in any request in your network.</p>

			==See also==
			{{Template:SQL connectivity topic list}}

	[[Category: SQL connectivity]]		[[Category: SQL connectivity]]

ELowell: /* SQL processing files */

2016-09-22T16:12:24Z

SQL processing files

← Older revision		Revision as of 16:12, 22 September 2016
Line 19:		Line 19:
	<tr>		<tr>
	<td>CATPROC</td>		<td>CATPROC</td>
	<td>Procedures and data: SOUL procedures to run [[SQL catalog reporting and querying\|CCACATREPT]] subsystem and to create the CCACAT file for initial installation and reorganizations; and Help files for CCACATREPT.</td>		<td>Procedures and data: SOUL procedures to run [[SQL catalog reporting and querying\|CCACATREPT]] subsystem and to create the CCACAT file for initial installation and reorganizations; and Help files for CCACATREPT.
			<p class="note"><b>Note:</b> As of Model 204 version 7.5, these procedures and data are contained in M204PROC, and CATPROC is no longer a valid file.</p></td>
	</tr>		</tr>
	<tr>		<tr>
Line 32:		Line 33:
	<tr>		<tr>
	<td>TSFPROC</td>		<td>TSFPROC</td>
	<td>Procedures and data: SOUL procedures to run CCATSF subsystem, and Help files for the TSF.</td>		<td>Procedures and data: SOUL procedures to run the CCATSF subsystem, and Help files for the TSF.
			<p class="note"><b>Note:</b> As of Model 204 version 7.5, these procedures and data are contained in M204PROC, and TSFPROC is no longer a valid file.</p></td>
	</tr>		</tr>
	</table>		</table>

ELowell: /* SQL processing files */

2016-09-21T22:19:56Z

SQL processing files

← Older revision		Revision as of 22:19, 21 September 2016
Line 23:		Line 23:
	<tr>		<tr>
	<td>CCACAT</td>		<td>CCACAT</td>
	<td>Required file. Model 204 SQL catalog for storage of all SQL DDL definitions.		<td>Required file. Model 204 [[SQL catalog]] for storage of all SQL DDL definitions.
	</td>		</td>
	</tr>		</tr>

ELowell: /* SQL processing files */

2016-09-13T19:59:05Z

SQL processing files

← Older revision		Revision as of 19:59, 13 September 2016
Line 19:		Line 19:
	<tr>		<tr>
	<td>CATPROC</td>		<td>CATPROC</td>
	<td>Procedures and data: SOUL procedures to run CCACATREPT subsystem and to create the CCACAT file for initial installation and reorganizations; and Help files for CCACATREPT.</td>		<td>Procedures and data: SOUL procedures to run [[SQL catalog reporting and querying\|CCACATREPT]] subsystem and to create the CCACAT file for initial installation and reorganizations; and Help files for CCACATREPT.</td>
	</tr>		</tr>
	<tr>		<tr>

ELowell: /* SQL processing files */

2016-09-13T19:53:10Z

SQL processing files

← Older revision		Revision as of 19:53, 13 September 2016
Line 28:		Line 28:
	<tr>		<tr>
	<td>TSFDATA</td>		<td>TSFDATA</td>
	<td>Model 204 file for work records that permit you to retain TSF (CCATSF subsystem) working data across sessions.</td>		<td>Model 204 file for work records that permit you to retain TSF ([[SQL DDL from the Table Specification Facility\|CCATSF]] subsystem) working data across sessions.</td>
	</tr>		</tr>
	<tr>		<tr>

JAL: misc formatting

2016-08-16T19:57:59Z

misc formatting

Show changes

JAL: /* Defining SQL and RCL IODEV threads */ add `s`

2016-08-10T19:20:19Z

Defining SQL and RCL IODEV threads: add <var>s

← Older revision		Revision as of 19:20, 10 August 2016
Line 162:		Line 162:
	You must define IODEV threads for all Connect<span class="superstar">★</span> configurations:</p>		You must define IODEV threads for all Connect<span class="superstar">★</span> configurations:</p>
	<ul>		<ul>
	<li><i>IODEV=19</i> defines a Model 204 TCP/IP SQL thread for TCP/IP. </li>		<li><code>IODEV=19</code> defines a Model 204 TCP/IP SQL thread for TCP/IP. </li>
	<li><i>IODEV=49</i> defines a Model 204 TCP/IP RCL thread for TCP/IP. </li>		<li><code>IODEV=49</code> defines a Model 204 TCP/IP RCL thread for TCP/IP. </li>
	</ul>		</ul>

	===Coding the IODEV line===		===Coding the IODEV line===
	Your definition of an IODEV 19 or 49 thread involves the specification or adjustment of the NOTHREAD, SQLBUFSZ, and LHEAP parameters described in this section. For examples, see [[#Runtime examples\|Runtime examples]].		Your definition of an IODEV 19 or 49 thread involves the specification or adjustment of the <var>NOTHREAD</var>, <var>SQLBUFSZ</var>, and <var>LHEAP</var> parameters described in this section. For examples, see [[#Runtime examples\|Runtime examples]].

	====RCL and SQL multithreaded environment====		====RCL and SQL multithreaded environment====
	When defining IODEV=49 (RCL) and IODEV=19 (SQL) threads:		When defining IODEV=49 (RCL) and IODEV=19 (SQL) threads:
	<ul>		<ul>
	<li>		<li>In the IODEV=49 line and in the IODEV=19, set the total number of concurrent threads (<var>NOTHREAD</var>) and identify the number of each thread.</li>
	In the IODEV=49 line and in the IODEV=19, set the total number of concurrent threads (NOTHREAD) and identify the number of each thread.</li>
	<li>		<li>In the IODEV=19, set other IODEV parameters such as <var>SQLBUFSZ</var>, <var>LHEAP</var>, <var>LIBUFF</var>, and <var>SQLIQBSZ</var>. The RCL thread uses these SQL thread settings as defaults. </li>
	In the IODEV=19, set other IODEV parameters such as SQLBUFSZ, LHEAP, LIBUFF, and SQLIQBSZ. The RCL thread uses these SQL thread settings as defaults. </li>
	</ul>		</ul>

	====NOTHREAD====		====NOTHREAD====
	You can insert one or more IODEV=19 or 49 lines in the CCAIN stream. On the first line defining the SQL or RCL thread, include the NOTHREAD parameter to indicate the number of threads to be allocated. The number of threads of types 19 and 49 is controlled by the CPUID zap and NOTHREAD must be less than the number of threads defined against the CPUID zap for your site.		You can insert one or more IODEV=19 or 49 lines in the CCAIN stream. On the first line defining the SQL or RCL thread, include the <var>NOTHREAD</var> parameter to indicate the number of threads to be allocated. The number of threads of types 19 and 49 is controlled by the CPUID zap, and <var>NOTHREAD<.var> must be less than the number of threads defined against the CPUID zap for your site.
	<p>		<p>
	Set NOTHREAD to the maximum number of concurrent Connect<span class="superstar">★</span> conversations to be supported. Make sure that your Model 204 NUSERS parameter setting accommodates these additional SQL and RCL threads.</p>		Set <var>NOTHREAD</var> to the maximum number of concurrent Connect<span class="superstar">★</span> conversations to be supported. Make sure that your Model 204 <var>NUSERS</var> parameter setting accommodates these additional SQL and RCL threads.</p>

	====SQLBUFSZ====		====SQLBUFSZ====
	SQLBUFSZ is a required user parameter that defines the maximum incoming SQL message length that can be presented to the SQL Server. The recommended initial value for this parameter is 100000. Specify it on the first IODEV 19 line.		<var>SQLBUFSZ</var> is a required user parameter that defines the maximum incoming SQL message length that can be presented to the SQL Server. The recommended initial value for this parameter is 100000. Specify it on the first IODEV 19 line.
	<p>For more information about sizing SQL buffers, see <var>[[SQLBUFSZ parameter\|SQLBUFSZ]]</var>.</p>		<p>
			For more information about sizing SQL buffers, see <var>[[SQLBUFSZ parameter\|SQLBUFSZ]]</var>.</p>

	====LHEAP====		====LHEAP====
	LHEAP specifies the size of HEAP, a dynamic storage area required for the processing of SQL C routines. HEAP is in the variable portion of the server area allocated to each user, and its size is added to the variable size calculation of the server area. An overall working space of 200,000 bytes is usually sufficient for SQL operations.		<var>LHEAP</var> specifies the size of HEAP, a dynamic storage area required for the processing of SQL C routines. HEAP is in the variable portion of the server area allocated to each user, and its size is added to the variable size calculation of the server area. An overall working space of 200,000 bytes is usually sufficient for SQL operations.
	<p>		<p>
	The recommended initial value is 200000 for SQL threads. Specify it on the first IODEV 19 line. Do not specify it with the User 0 parameters, because this wastes space. For non-SQL threads, which do not require HEAP space, you can set or reset LHEAP to zero, the default. </p>		The recommended initial value is 200000 for SQL threads. Specify it on the first IODEV 19 line. Do not specify it with the User 0 parameters, because this wastes space. For non-SQL threads, which do not require HEAP space, you can set or reset <var>LHEAP</var> to zero, the default. </p>
	<p>		<p>
	You can monitor the high-water mark for use of this storage area with the HEAP statistic, described in [[#HEAP and PDL high-water marks\|HEAP and PDL high-water marks]].</p>		You can monitor the high-water mark for use of this storage area with the HEAP statistic, described in [[#HEAP and PDL high-water marks\|HEAP and PDL high-water marks]].</p>
	<p>		<p>
	As the query complexity increases, you must increase the LHEAP value accordingly, as you encounter SQL error messages. Many SQL error messages offer specific advice. However, if you continue to get SQL error messages after increasing the LHEAP value, your query is too complex for RSQL to handle. You should rewrite your query into smaller, less complex parts.</p>		As the query complexity increases, you must increase the <var>LHEAP</var> value accordingly, as you encounter SQL error messages. Many SQL error messages offer specific advice. However, if you continue to get SQL error messages after increasing the <var>LHEAP</var> value, your query is too complex for RSQL to handle. You should rewrite your query into smaller, less complex parts.</p>

	==Runtime examples==		==Runtime examples==

ELowell: /* SQLBUFSZ */

2015-07-20T19:47:36Z

SQLBUFSZ

← Older revision		Revision as of 19:47, 20 July 2015
Line 185:		Line 185:
	====SQLBUFSZ====		====SQLBUFSZ====
	SQLBUFSZ is a required user parameter that defines the maximum incoming SQL message length that can be presented to the SQL Server. The recommended initial value for this parameter is 100000. Specify it on the first IODEV 19 line.		SQLBUFSZ is a required user parameter that defines the maximum incoming SQL message length that can be presented to the SQL Server. The recommended initial value for this parameter is 100000. Specify it on the first IODEV 19 line.
	<p>For more information about sizing SQL buffers, see [[SQLBUFSZ parameter]].</p>		<p>For more information about sizing SQL buffers, see <var>[[SQLBUFSZ parameter\|SQLBUFSZ]]</var>.</p>

	====LHEAP====		====LHEAP====

ELowell: /* Variable server area */

2015-07-20T19:46:41Z

Variable server area

← Older revision		Revision as of 19:46, 20 July 2015
Line 279:		Line 279:
	<td>C routine processing		<td>C routine processing
	</td>		</td>
	<td>LHEAP		<td><var>[[LHEAP parameter\|LHEAP]]</var></td>
	</td>
	</tr>		</tr>
	<tr>		<tr>
Line 287:		Line 286:
	<td>User pushdown list		<td>User pushdown list
	</td>		</td>
	<td>LPDLST		<td><var>[[LPDLST parameter\|LPDLST]]</var></td>
	</td>
	</tr>		</tr>
	<tr>		<tr>
Line 295:		Line 293:
	<td>Statement labels, list names, and variables		<td>Statement labels, list names, and variables
	</td>		</td>
	<td>LNTBL		<td><var>[[LNTBL parameter\|LNTBL]]</var></td>
	</td>
	</tr>		</tr>
	<tr>		<tr>
Line 303:		Line 300:
	<td>Statements in internal form (quadruples)		<td>Statements in internal form (quadruples)
	</td>		</td>
	<td>LQTBL		<td><var>[[LQTBL parameter\|LQTBL]]</var></td>
	</td>
	</tr>		</tr>
	<tr>		<tr>
Line 311:		Line 307:
	<td>Character strings		<td>Character strings
	</td>		</td>
	<td>LSTBL		<td><var>[[LSTBL parameter\|LSTBL]]</var>
	</td>		</td>
	</tr>		</tr>
Line 319:		Line 315:
	<td>Temporary work pages		<td>Temporary work pages
	</td>		</td>
	<td>LTTBL		<td><var>[[LTTBL parameter\|LTTBL]]</var>
	</td>		</td>
	</tr>		</tr>
Line 327:		Line 323:
	<td>		<td>
	Compiler variables</td>		Compiler variables</td>
	<td>LVTBL</td>		<td><var>[[LVTBL parameter\|LVTBL]]</var></td>
	</tr>		</tr>
	</table>		</table>

Runtime environment for SQL processing - Revision history

Mlarocca: /* CCAIN parameters to support Model 204 SQL processing */

ELowell at 23:59, 11 October 2016

ELowell: /* SQL processing files */

ELowell: /* SQL processing files */

ELowell: /* SQL processing files */

ELowell: /* SQL processing files */

JAL: misc formatting

JAL: /* Defining SQL and RCL IODEV threads */ add s

ELowell: /* SQLBUFSZ */

ELowell: /* Variable server area */

JAL: /* Defining SQL and RCL IODEV threads */ add `s`