SQLBUFSZ parameter: Difference between revisions
m (Automatically generated page update) |
m (Automatically generated page update) |
||
| Line 14: | Line 14: | ||
==Description== | ==Description== | ||
<p>The size of the <var class="product">Model 204</var> SQL Server buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer</p> | <p>The size of the <var class="product">Model 204</var> SQL Server buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer</p> | ||
<p>The SQLBUFSZ value defines the maximum length of an incoming SQL message. Since the largest incoming SQL message is likely to be a DDL transaction, set SQLBUFSZ large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the SQLBUFSZ parameter is 100000. </p> | <p>The SQLBUFSZ value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set SQLBUFSZ large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the SQLBUFSZ parameter is 100000. </p> | ||
<table> | <table> | ||
<tr><th>For...</th><th>Set SQLBUFSZ...</th></tr> | <tr><th>For...</th><th>Set SQLBUFSZ...</th></tr> | ||
<tr><th><var>A General Data Stream (GDS) passed from the conversation buffer to CMIS (SQL communications interface) receiving buffer and moved to the <var class="product">Model 204</var> SQL buffer</var></th><td>Greater than or equal to the maximum incoming SQL message length that can be received by the SQL server. </td></tr> | <tr><th><var>A General Data Stream (GDS) passed from the conversation buffer to CMIS (SQL communications interface) receiving buffer and moved to the <var class="product">Model 204</var> SQL buffer</var></th><td>Greater than or equal to the maximum incoming SQL message length that can be received by the SQL server. </td></tr> | ||
</table> | </table> | ||
<p><b> </b> </p> | |||
<p>Specify SQLBUFSZ on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see the <var>Rocket Model 204 System Manager's Guide.</var></p> | <p>Specify SQLBUFSZ on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see the <var>Rocket Model 204 System Manager's Guide.</var></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 that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set SQLBUFSZ=60000 to run a DDL statement that is 52K.</p> | <p>When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set SQLBUFSZ=60000 to run a DDL statement that is 52K.</p> | ||
<p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see <var>Model 204 System Manager's Guide.</var></p> | <p>You can also monitor the <var class="product">Model 204</var> SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see <var>Rocket Model 204 System Manager's Guide.</var></p> | ||
[[Category:User Parameters]] | [[Category:User Parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 00:56, 28 February 2013
Summary
- Default value
- 0
- Parameter type
- User
- Where set
- By any user
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
The size of the Model 204 SQL Server buffer that assembles incoming SQL messages from a Horizon, CRAM SQL, or IUCV SQL buffer
The SQLBUFSZ value defines the maximum length of an incoming SQL message. The incoming SQL message contains the SQL request in addition to the data. Since the largest incoming SQL message is likely to be a DDL transaction, set SQLBUFSZ large enough to accommodate your largest DDL transaction plus 50 bytes of overhead. The maximum value you can specify is slightly over two billion. The recommended initial value for the SQLBUFSZ parameter is 100000.
| For... | Set SQLBUFSZ... |
|---|---|
| A General Data Stream (GDS) passed from the conversation buffer to CMIS (SQL communications interface) receiving buffer and moved to the Model 204 SQL buffer | Greater than or equal to the maximum incoming SQL message length that can be received by the SQL server. |
Specify SQLBUFSZ on the first IODEV 19, 17, or 13 line. To define SQL and RCL IODEV threads on IODEV 49, see the Rocket Model 204 System Manager's Guide.
Handling SQL statements greater than 32k bytes
When handling an SQL statement that is greater than 32K, you must consider that the SQLBUFSZ parameter is the buffer to collect the entire SQL statement. It must be slightly greater than the maximum size of the largest SQL statement. For example, set SQLBUFSZ=60000 to run a DDL statement that is 52K.
You can also monitor the Model 204 SQLI since-last statistic to determine the size of the largest SQL input request. For more information about the SQLI statistic, see Rocket Model 204 System Manager's Guide.