LIBUFF parameter: Difference between revisions
m (Automatically generated page update) |
(Added clarification on what LIBUFF is used for - all parameter lines in CCAIN) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:LIBUFF parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 8: | Line 9: | ||
<dd>On User 0's parameter line or in: | <dd>On User 0's parameter line or in: | ||
<ul> | <ul> | ||
<li> | <li>PARM field in the JCL EXEC statement (z/OS) | ||
PARM field in the JCL EXEC statement (z/OS) | <p class="note"><b>Note:</b> The value set for <var>LIBUFF</var> takes effect immediately, so you must set <var>LIBUFF</var> large enough to accommodate all of the parameter lines in CCAIN; each line is 80 bytes in length.</p></li> | ||
<p class="note"><b>Note:</b> The value set for LIBUFF takes effect immediately, so you must set LIBUFF large enough to accommodate CCAIN.</p> | |||
</li> | <li>EXEC that issues all the FILEDEFs (z/VM)</li> | ||
<li> | |||
EXEC that issues all the FILEDEFs (z/VM)</li> | <li>JCL OPTION statement (z/VSE)</li> | ||
<li> | |||
JCL OPTION statement (z/VSE)</li> | |||
</ul> | </ul> | ||
<dt>Related products | <dt>Related products | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V2.2</var> or earlier | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p> | <p> | ||
<p>The input buffer must be at least three characters longer than the longest anticipated input line. (Long lines are rejected.) LIBUFF also specifies the maximum length allowed for string arguments to Host Language Interface calls from user programs. </p> | <var>LIBUFF</var> specifies the length of the input buffer used for input lines from <var>[[Defining the runtime environment (CCAIN)|CCAIN]]</var> or a user's terminal.</p> | ||
<p>If User 0's parameter line is longer than 255 characters, set LIBUFF with the parameters passed by the operating system when <var class="product">Model 204</var> is invoked. LIBUFF must not exceed 32767.</p> | <p> | ||
<p>The value of LIBUFF affects the setting of the User 0 parameter IFAMBS. For the algorithm expressing their relationship, see [[IFAMBS parameter | The input buffer must be at least three characters longer than the longest anticipated input line. (Long lines are rejected.) <var>LIBUFF</var> also specifies the maximum length allowed for string arguments to Host Language Interface calls from user programs. </p> | ||
<p>Under z/VSE, you can abbreviate LIBUFF when setting it in the SYSPARM field of the OPTION statement in the JCL. Abbreviating it to LIB allows you to enter a LIBUFF value up to four digits long. The JCL statement takes the form: </p> | <p> | ||
<p class="code">// OPTION SYSPARM='LIB=n' | If User 0's parameter line is longer than 255 characters, set <var>LIBUFF</var> with the parameters passed by the operating system when <var class="product">Model 204</var> is invoked. <var>LIBUFF</var> must not exceed 32767.</p> | ||
</p><p> where n must be a number greater than 0 and less than or equal to 9999. </p> | <p> | ||
[[Category:Utable | The value of <var>LIBUFF</var> affects the setting of the User 0 parameter <var>IFAMBS</var>. For the algorithm expressing their relationship, see [[IFAMBS parameter]].</p> | ||
<p> | |||
Under z/VSE, you can abbreviate <var>LIBUFF</var> when setting it in the SYSPARM field of the OPTION statement in the JCL. Abbreviating it to <var>LIB</var> allows you to enter a <var>LIBUFF</var> value up to four digits long. The JCL statement takes the form: </p> | |||
<p class="code">// OPTION SYSPARM='LIB=<i>n</i>' | |||
</p> | |||
<p>where <var class="term">n</var> must be a number greater than 0 and less than or equal to 9999. </p> | |||
[[Category:Utable parameters]] | |||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 19:27, 6 January 2017
Length of input buffer
Summary
- Default value
- 255
- Parameter type
- Utable
- Where set
- On User 0's parameter line or in:
- PARM field in the JCL EXEC statement (z/OS)
Note: The value set for LIBUFF takes effect immediately, so you must set LIBUFF large enough to accommodate all of the parameter lines in CCAIN; each line is 80 bytes in length.
- EXEC that issues all the FILEDEFs (z/VM)
- JCL OPTION statement (z/VSE)
- PARM field in the JCL EXEC statement (z/OS)
- Related products
- All
- Introduced
- Model 204 V2.2 or earlier
Description
LIBUFF specifies the length of the input buffer used for input lines from CCAIN or a user's terminal.
The input buffer must be at least three characters longer than the longest anticipated input line. (Long lines are rejected.) LIBUFF also specifies the maximum length allowed for string arguments to Host Language Interface calls from user programs.
If User 0's parameter line is longer than 255 characters, set LIBUFF with the parameters passed by the operating system when Model 204 is invoked. LIBUFF must not exceed 32767.
The value of LIBUFF affects the setting of the User 0 parameter IFAMBS. For the algorithm expressing their relationship, see IFAMBS parameter.
Under z/VSE, you can abbreviate LIBUFF when setting it in the SYSPARM field of the OPTION statement in the JCL. Abbreviating it to LIB allows you to enter a LIBUFF value up to four digits long. The JCL statement takes the form:
// OPTION SYSPARM='LIB=n'
where n must be a number greater than 0 and less than or equal to 9999.