Full-screen feature - Revision history

Dme: /* Screen item name variables */

2019-04-15T20:28:54Z

Screen item name variables

← Older revision		Revision as of 20:28, 15 April 2019
Line 448:		Line 448:
	</table>		</table>

	===<b ~~class~~="scrnItemNameVars"></b>Screen item name variables===		===<b id="scrnItemNameVars"></b>Screen item name variables===
	<p>		<p>
	Screen item name variables refer indirectly to screen item names, thereby allowing portions of a request, such as subroutines, to be generalized. A screen item name variable is indicated in the following format: </p>		Screen item name variables refer indirectly to screen item names, thereby allowing portions of a request, such as subroutines, to be generalized. A screen item name variable is indicated in the following format: </p>

Dme: /* Screen item name variables */

2019-04-15T20:28:03Z

Screen item name variables

← Older revision		Revision as of 20:28, 15 April 2019
Line 448:		Line 448:
	</table>		</table>

	===Screen item name variables===		===<b class="scrnItemNameVars"></b>Screen item name variables===
	<p>		<p>
	Screen item name variables refer indirectly to screen item names, thereby allowing portions of a request, such as subroutines, to be generalized. A screen item name variable is indicated in the following format: </p>		Screen item name variables refer indirectly to screen item names, thereby allowing portions of a request, such as subroutines, to be generalized. A screen item name variable is indicated in the following format: </p>
Line 465:		Line 465:
	<p>		<p>
	A screen item name variable and a menu or screen variable are actually the same variable. </p>		A screen item name variable and a menu or screen variable are actually the same variable. </p>

	==<b id="menuStmt"></b>Defining menus==		==<b id="menuStmt"></b>Defining menus==
	<p>		<p>

DCameron: /* Reserved cursor variables */

2018-08-08T09:30:11Z

Reserved cursor variables

← Older revision		Revision as of 09:30, 8 August 2018
Line 1,816:		Line 1,816:
	<p>		<p>
	After the execution of a READ, REREAD, or PRINT statement, the cursor variables contain values. These values are not reset by a PREPARE statement. It is the responsibility of the User Language request to reset the variables, if necessary, before the next READ, REREAD, or PRINT statement. </p>		After the execution of a READ, REREAD, or PRINT statement, the cursor variables contain values. These values are not reset by a PREPARE statement. It is the responsibility of the User Language request to reset the variables, if necessary, before the next READ, REREAD, or PRINT statement. </p>

	===Using cursor setting===		===Using cursor setting===
	<p>		<p>

JAL: mixed case for statements

2018-05-30T20:33:20Z

mixed case for statements

Show changes

JAL: /* Defining screens */ add `s`

2018-05-30T00:14:52Z

Defining screens: add <var>s

← Older revision		Revision as of 00:14, 30 May 2018
Line 945:		Line 945:
	==<b id="scrnStmt"></b>Defining screens==		==<b id="scrnStmt"></b>Defining screens==

	<p>The <~~var class="term"~~>Screen block</~~var~~> is used to define and format a screen. Formatting involves specifying a title and all prompts to be displayed on the screen, and describing input items to be entered by the terminal operator. </p>		<p>The <b>Screen block</b> is used to define and format a screen. Formatting involves specifying a title and all prompts to be displayed on the screen, and describing input items to be entered by the terminal operator. </p>

	<p>The <var>Screen</var> block must begin with <var>Screen</var> and end with <var>End Screen</var>. In between, you specify a series of <~~var class="term"~~>~~screenLine~~</~~var~~>s that describe the titles, prompts, input areas, and blank lines to appear on the screen.</p>		<p>
			The <var>Screen</var> block must begin with <var>Screen</var> and end with <var>End Screen</var>. In between, you specify a series of <b>screenLines</b> that describe the titles, prompts, input areas, and blank lines to appear on the screen. </p>
	<p>You must include a <var>Screen</var> block in a SOUL request for every screen to be displayed by that request.</p>		<p>
	<p>You can also use the <~~var class="term"~~>Screen statement</~~var~~> to define a <var>Common</var> name for a screen defined in an earlier <var>Screen</var> block.</p>		You must include a <var>Screen</var> block in a SOUL request for every screen to be displayed by that request. </p>
			<p>
			You can also use the <b>Screen statement</b> to define a <var>Common</var> name for a screen defined in an earlier <var>Screen</var> block. </p>

	===Screen block and statement syntax===		===Screen block and statement syntax===
Line 958:		Line 960:
	Where:		Where:
	<ul>		<ul>
	<li><var class="term">screenName</var> is a user-defined string from 1 to 255 characters in length. Every screen name defined in a request must be unique. The screen name specified in the Screen statement is assigned to the screen being defined; it subsequently can be referenced in screen manipulation statements.</li>		<li><var class="term">screenName</var> is a user-defined string from 1 to 255 characters in length. Every screen name defined in a request must be unique. The screen name specified in the <var>Screen</var> statement is assigned to the screen being defined; it subsequently can be referenced in screen manipulation statements. </li>

	<li><var>Declare</var> and <var>Common</var> are used if the screen is a common element in the request. Specifying <var>Common</var> (or specifying neither <var>Common</var> nor <var>Global</var>) results in the screen being stored in the default area (the FSCB) rather than in GTBL. Common elements, as well as Declare and Common, are discussed in detail in [[Subroutines#Sharing common elements\|Sharing common elements]].</li>		<li><var>Declare</var> and <var>Common</var> are used if the screen is a common element in the request. Specifying <var>Common</var> (or specifying neither <var>Common</var> nor <var>Global</var>) results in the screen being stored in the default area (the FSCB) rather than in GTBL. Common elements, as well as <var>Declare</var> and <var>Common</var>, are discussed in detail in [[Subroutines#Sharing common elements\|Sharing common elements]]. </li>

	<li>Global specifies that the screen is stored in GTBL. Global menus have an implied scope of Common (see above).		<li><var>Global</var> specifies that the screen is stored in GTBL. Global menus have an implied scope of <var>Common</var> (see above).

	<p class="note"><b>Note:</b>		<p class="note"><b>Note:</b>
	Do not specify the Global attribute for multi-page (logical pages) screens.</p>		Do not specify the <var>Global</var> attribute for multi-page (logical pages) screens.</p></li>
	</li>

	<li>Permanent (Perm) can only be used with global screens. Perm global screens persist across request boundaries (they are maintained in GTBL even after a request has been terminated).</li>		<li><var>Permanent</var> (<var>Perm</var>) can only be used with global screens. <var>Perm</var> global screens persist across request boundaries (they are maintained in GTBL even after a request has been terminated). </li>

	<li>Temporary (Temp) can only be used with global screens. Temp global screens are allocated in GTBL, but are deleted at request termination. ~~An example of using~~ a Temp global screen ~~would be~~ when you do not need to pass the screen to another request; using Temp global screens eliminates the need ~~for you~~ to explicitly delete globals that do not need to persist.		<li><var>Temporary</var> (<var>Temp</var>) can only be used with global screens. <var>Temp</var> global screens are allocated in GTBL, but they are deleted at request termination. You might use a <var>Temp</var> global screen when you do not need to pass the screen to another request; using <var>Temp</var> global screens eliminates the need to explicitly delete globals that do not need to persist. </li>
	</li>
	<li>You can include any number of screen lines in a screen definition.		<li>You can include any number of screen lines in a screen definition.
	<p>Each screen line normally corresponds to a single line on the [[#Logical and physical panels\|physical panel]]. The ~~User Language~~ compiler regards a <var class="term">screenLine</var> as a logical input line. If a screen line is longer than a single request input line, use a hyphen for continuation. </p></li>		<p>
			Each screen line normally corresponds to a single line on the [[#Logical and physical panels\|physical panel]]. The SOUL compiler regards a <var class="term">screenLine</var> as a logical input line. If a screen line is longer than a single request input line, use a hyphen for continuation. </p></li>

	<li>		<li>
	<p>		<p>
	A <var class="term">screenLine</var> can be one of the following: </p>		A <var class="term">screenLine</var> can be one of the following: </p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 1,019:		Line 1,022:
	</table>		</table>
	</li>		</li>
	<li>Comments or blank lines included in a screen definition (between <var>Screen</var> and <var>End Screen</var>) are ignored by <var class="product">Model 204</var>.</li>
	<li>Every screen statement must end with <var>End Screen</var>, which terminates the definition of the screen.</li>		<li>Comments or blank lines included in a screen definition (between <var>Screen</var> and <var>End Screen</var>) are ignored by <var class="product">Model 204</var>. </li>

			<li>Every screen statement must end with <var>End Screen</var>, which terminates the definition of the screen. </li>
	</ul>		</ul>

	===Logical and physical panels===		===Logical and physical panels===
	<p>		<p>
	The screen actually displayed to the terminal operator depends on the logical panel and physical panel.</p>		The screen actually displayed to the terminal operator depends on the logical panel and physical panel. </p>

	====Logical screen====		====Logical screen====
	<p>		<p>
	A logical screen (panel) is that part of the logical screen definition which is ended by a ~~NEW PAGE~~ or by an ~~END SCREEN~~ statement. These statements control where the display screen is to end. </p>		A logical screen (panel) is that part of the logical screen definition which is ended by a <var>New Page</var> or by an <var>End Screen</var> statement. These statements control where the display screen is to end. </p>

	====Physical screen====		====Physical screen====
	<p>		<p>
	A physical screen (panel) is the part of the logical panel that fits on the user's physical terminal as determined by the MODEL parameter. The full-screen formatting feature defines screens independently of the terminal operator's 3270 terminal model; the correct length is displayed when the request is evaluated.</p>		A physical screen (panel) is the part of the logical panel that fits on the user's physical terminal as determined by the <var>MODEL</var> parameter. The full-screen formatting feature defines screens independently of the terminal operator's 3270 terminal model; the correct length is displayed when the request is evaluated. </p>

	<p>If the prompts and/or input items specified in a screen definition exceed the number of lines available on a physical panel, <var class="product">Model 204</var> automatically constructs an overflow panel for the remaining lines. The overflow panel has the same title as the original screen.</p>		<p>If the prompts and/or input items specified in a screen definition exceed the number of lines available on a physical panel, <var class="product">Model 204</var> automatically constructs an overflow panel for the remaining lines. The overflow panel has the same title as the original screen. </p>

	==TITLE and PROMPT statements for screens==		==TITLE and PROMPT statements for screens==

ELowell: /* Maximum number of screens and menus */

2016-09-28T00:10:52Z

Maximum number of screens and menus

← Older revision		Revision as of 00:10, 28 September 2016
Line 36:		Line 36:
	===Maximum number of screens and menus===		===Maximum number of screens and menus===
	<p>		<p>
	The maximum number of screens and menus combined is 256 ~~per request~~.</p>		The maximum number of screens and menus combined per request is 256 (version 7.6 and earlier) or 4095 (version 7.7 and later).</p>

	===Global screens and menus===		===Global screens and menus===
	<p>		<p>

ELowell: /* LFSCB parameter setting */

2016-06-23T20:13:44Z

LFSCB parameter setting

← Older revision		Revision as of 20:13, 23 June 2016
Line 32:		Line 32:
	===LFSCB parameter setting===		===LFSCB parameter setting===
	<p>		<p>
	The system manager sets the <var>[[LFSCB parameter\|LFSCB]]</var> parameter (size of full-screen buffer) ~~to a positive number~~ during system initialization, or the user sets the LFSCB parameter Online with the UTABLE command. </p>		The system manager sets the <var>[[LFSCB parameter\|LFSCB]]</var> parameter (size of full-screen buffer) during system initialization, or the user sets the LFSCB parameter Online with the UTABLE command. </p>

	===Maximum number of screens and menus===		===Maximum number of screens and menus===
	<p>		<p>

ELowell: /* Defining screens */

2016-02-26T00:24:01Z

Defining screens

← Older revision		Revision as of 00:24, 26 February 2016
Line 945:		Line 945:
	==<b id="scrnStmt"></b>Defining screens==		==<b id="scrnStmt"></b>Defining screens==

	<p>		<p>The <var class="term">Screen block</var> is used to define and format a screen. Formatting involves specifying a title and all prompts to be displayed on the screen, and describing input items to be entered by the terminal operator. </p>
	The <var>Screen</var~~> <b>block</b~~> is used to define and format a screen. Formatting involves specifying a title and all prompts to be displayed on the screen, and describing input items to be entered by the terminal operator. </p>

	<p>		<p>The <var>Screen</var> block must begin with <var>Screen</var> and end with <var>End Screen</var>. In between, you specify a series of <var class="term">screenLine</var>s that describe the titles, prompts, input areas, and blank lines to appear on the screen.</p>
	The <var>Screen</var> block must begin with <var>Screen</var> and end with <var>End Screen</var>. In between, you specify a series of <var class="term">screenLine</var>s that describe the titles, prompts, input areas, and blank lines to appear on the screen.</p>

	<p>		<p>You must include a <var>Screen</var> block in a SOUL request for every screen to be displayed by that request.</p>
	You must include a <var>Screen</var> block in a SOUL request for every screen to be displayed by that request.		<p>You can also use the <var class="term">Screen statement</var> to define a <var>Common</var> name for a screen defined in an earlier <var>Screen</var> block.</p>
	You ~~may~~ also use the <var>Screen</var~~> <b>statement</b~~> to define a <var>Common</var> name for a screen defined in an
	earlier <var>Screen</var> block. </p>

	===Screen block and statement syntax===		===Screen block and statement syntax===
	<p>		<p>The syntax of the <var>Screen</var> block and statement is:</p>
	The syntax of the <var>Screen</var> block and statement is:</p>
	{{Template: Screen statement syntax}}		{{Template: Screen statement syntax}}

Line 965:		Line 960:
	<li><var class="term">screenName</var> is a user-defined string from 1 to 255 characters in length. Every screen name defined in a request must be unique. The screen name specified in the Screen statement is assigned to the screen being defined; it subsequently can be referenced in screen manipulation statements.</li>		<li><var class="term">screenName</var> is a user-defined string from 1 to 255 characters in length. Every screen name defined in a request must be unique. The screen name specified in the Screen statement is assigned to the screen being defined; it subsequently can be referenced in screen manipulation statements.</li>

	<li><var>Declare</var> and <var>Common</var> are used if the screen is a common element in the request. Specifying <var>Common</var> (or specifying neither <var>Common</var> nor <var>Global</var>) results in the screen being stored in the default area (the FSCB) rather than in GTBL. Common elements, as well as ~~Declareand~~ Common, are discussed in detail in [[Subroutines#Sharing common elements\|Sharing common elements]]. </li>		<li><var>Declare</var> and <var>Common</var> are used if the screen is a common element in the request. Specifying <var>Common</var> (or specifying neither <var>Common</var> nor <var>Global</var>) results in the screen being stored in the default area (the FSCB) rather than in GTBL. Common elements, as well as Declare and Common, are discussed in detail in [[Subroutines#Sharing common elements\|Sharing common elements]].</li>

	<li>Global specifies that the screen is stored in GTBL. Global menus have an implied scope of Common (see above).		<li>Global specifies that the screen is stored in GTBL. Global menus have an implied scope of Common (see above).
Line 1,038:		Line 1,033:
	====Physical screen====		====Physical screen====
	<p>		<p>
	A physical screen (panel) is ~~that~~ part of the logical panel ~~which~~ fits on the user's physical terminal as determined by the MODEL parameter. The full-screen formatting feature defines screens independently of the terminal operator's 3270 terminal model; the correct length is displayed when the request is evaluated. If the prompts and/or input items specified in a screen definition exceed the number of lines available on a physical panel, <var class="product">Model 204</var> automatically constructs an overflow panel for the remaining lines. The overflow panel has the same title as the original screen. </p>		A physical screen (panel) is the part of the logical panel that fits on the user's physical terminal as determined by the MODEL parameter. The full-screen formatting feature defines screens independently of the terminal operator's 3270 terminal model; the correct length is displayed when the request is evaluated.</p>

			<p>If the prompts and/or input items specified in a screen definition exceed the number of lines available on a physical panel, <var class="product">Model 204</var> automatically constructs an overflow panel for the remaining lines. The overflow panel has the same title as the original screen.</p>

	==TITLE and PROMPT statements for screens==		==TITLE and PROMPT statements for screens==

ELowell at 00:12, 26 February 2016

2016-02-26T00:12:53Z

← Older revision		Revision as of 00:12, 26 February 2016
Line 232:		Line 232:
	===Extended display attributes===		===Extended display attributes===
	<p>		<p>
	In addition, extended display attributes available on some 3278 and 3279-type terminals can be used within an application to alert the terminal operator to areas of the display and error conditions. To use extended attributes, the <var>[[FSOUTPUT parameter\|FSOUTPUT]]</var> parameter must be set.		In addition, extended display attributes available on some 3278 and 3279-type terminals can be used within an application to alert the terminal operator to areas of the display and error conditions. To use extended attributes, the <var>[[FSOUTPUT parameter\|FSOUTPUT]]</var> parameter must be set.</p>
	<p>		<p>
	Extended attributes are a combination of display attributes selected from the categories listed below. Abbreviations are capitalized. Consult the appropriate hardware support person within your installation to determine if extended attributes are supported.</p>		Extended attributes are a combination of display attributes selected from the categories listed below. Abbreviations are capitalized. Consult the appropriate hardware support person within your installation to determine if extended attributes are supported.</p>

ELowell: /* PREPARE statement */

2015-08-20T20:03:12Z

PREPARE statement

← Older revision		Revision as of 20:03, 20 August 2015
Line 1,612:		Line 1,612:
	A MODIFY statement changes only those attributes that you wish to change (for example, from BRIGHT to DIM); the statement leaves other attributes unchanged. If ALL is specified or the FOR clause is omitted, the new attributes apply to READ, REREAD, TAG, and PRINT. </p>		A MODIFY statement changes only those attributes that you wish to change (for example, from BRIGHT to DIM); the statement leaves other attributes unchanged. If ALL is specified or the FOR clause is omitted, the new attributes apply to READ, REREAD, TAG, and PRINT. </p>

	===<b id="PrepareStmtScrn"</b>PREPARE statement===		===<b id="PrepareStmtScrn"></b>PREPARE statement===
	<p>		<p>
	The PREPARE statement reinitializes the values of all input items and other text displayed on a screen. PREPARE can be issued at any point in a request to restore values that were altered by READ, REREAD, TAG, MODIFY, and assignment statements. </p>		The PREPARE statement reinitializes the values of all input items and other text displayed on a screen. PREPARE can be issued at any point in a request to restore values that were altered by READ, REREAD, TAG, MODIFY, and assignment statements. </p>

Full-screen feature - Revision history

Dme: /* Screen item name variables */

Dme: /* Screen item name variables */

DCameron: /* Reserved cursor variables */

JAL: mixed case for statements

JAL: /* Defining screens */ add s

ELowell: /* Maximum number of screens and menus */

ELowell: /* LFSCB parameter setting */

ELowell: /* Defining screens */

ELowell at 00:12, 26 February 2016

ELowell: /* PREPARE statement */

JAL: /* Defining screens */ add `s`