MORE command - Revision history

ELowell at 16:12, 22 March 2017

2017-03-22T16:12:28Z

← Older revision		Revision as of 16:12, 22 March 2017
Line 49:		Line 49:
	<p>When <var>More</var> follows another command that does not automatically end its own update unit (for example, <var>[[DEFINE FIELD command\|DEFINE FIELD]]</var>), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. See [[File_integrity_and_recovery#Update_units_and_transactions\|Update units and transactions]] for more information.</p>		<p>When <var>More</var> follows another command that does not automatically end its own update unit (for example, <var>[[DEFINE FIELD command\|DEFINE FIELD]]</var>), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. See [[File_integrity_and_recovery#Update_units_and_transactions\|Update units and transactions]] for more information.</p>

	[[Category: ~~General user~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

Dme at 11:32, 25 January 2015

2015-01-25T11:32:05Z

← Older revision		Revision as of 11:32, 25 January 2015
Line 4:		Line 4:
	<dd>Any user		<dd>Any user
	<dt>Function		<dt>Function
	<dd>Indicates to <var class="product">Model 204</var> that the next ~~User Language~~ request is a continuation of the previous request		<dd>Indicates to <var class="product">Model 204</var> that the next SOUL request is a continuation of the previous request
	</dl>		</dl>
	==Syntax==		==Syntax==
Line 10:		Line 10:

	==Usage notes==		==Usage notes==
	<p>A ~~User Language~~ request normally is preceded by a <var>[[BEGIN command\|Begin]]</var> command and concluded by an <var>[[End statement\|End]]</var> statement. However, if the <var>More</var> command is used rather than <var>Begin</var>, <var class="product">Model 204</var> considers the request that follows to be a continuation of the previous request. The continued request can refer to statement labels and other information contained in the previous request.</p>		<p>A SOUL request normally is preceded by a <var>[[BEGIN command\|Begin]]</var> command and concluded by an <var>[[End statement\|End]]</var> statement. However, if the <var>More</var> command is used rather than <var>Begin</var>, <var class="product">Model 204</var> considers the request that follows to be a continuation of the previous request. The continued request can refer to statement labels and other information contained in the previous request.</p>
	<p>A request that is to be continued must be concluded by: </p>		<p>A request that is to be continued must be concluded by: </p>
	<p class="code">end more		<p class="code">end more

Dme: /* Usage notes */

2015-01-25T10:54:51Z

Usage notes

← Older revision		Revision as of 10:54, 25 January 2015
Line 10:		Line 10:

	==Usage notes==		==Usage notes==
	<p>A User Language request normally is preceded by a BEGIN command and concluded by an ~~END~~ statement. However, if the ~~BEGIN~~ is ~~replaced by the MORE command~~, <var class="product">Model 204</var> considers the request that follows to be a continuation of the previous request. The continued request can refer to statement labels and other information contained in the previous request.</p>		<p>A User Language request normally is preceded by a <var>[[BEGIN command\|Begin]]</var> command and concluded by an <var>[[End statement\|End]]</var> statement. However, if the <var>More</var> command is used rather than <var>Begin</var>, <var class="product">Model 204</var> considers the request that follows to be a continuation of the previous request. The continued request can refer to statement labels and other information contained in the previous request.</p>
	<p>A request that is to be continued must be concluded by: </p>		<p>A request that is to be continued must be concluded by: </p>
	<p class="code">~~END MORE~~		<p class="code">end more
	</p>		</p>
	<p>not simply by ~~END~~.</p>		<p>not simply by <var>End</var>.</p>
	<p>The following example shows the use of the ~~MORE~~ command:</p>		<p>The following example shows the use of the <var>More</var> command:</p>
	<p class="code">~~BEGIN~~		<p class="code">begin
	.		.
	.		.
	.		.
	~~User Language~~ statement(s)		SOUL statement(s)
	.		.
	.		.
	.		.
	~~END MORE~~		end more
	request output		request output
	.		.
Line 33:		Line 33:
	.		.
	.		.
	~~MORE~~		more
	.		.
	.		.
	.		.
	~~User Language~~ statement(s)		SOUL statement(s)
	.		.
	.		.
	.		.
	~~END~~		end
	request output		request output
	</p>		</p>
	<p>Request continuation is used to break up requests that otherwise would be too large to run (that is, would exhaust work table space), or to increase user interaction with <var class="product">Model 204</var> without increasing retrieval costs.</p>		<p>Request continuation is used to break up requests that otherwise would be too large to run (that is, would exhaust work table space), or to increase user interaction with <var class="product">Model 204</var> without increasing retrieval costs.</p>
	<p>If a request ends with an ~~END MORE USE~~ statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>		<p>If a request ends with an <var>End More Use</var> statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>
	<p>After <var class="product">Model 204</var> encounters an ~~END that does not have a MORE argument~~, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in ~~the <var class="book">Model 204 User Language Manual</var>~~.</p>		<p>After <var class="product">Model 204</var> encounters an <var>End</var> statement without <var>More</var>, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in [[Large request considerations]].</p>
	<p>When ~~MORE~~ follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. See [[File_integrity_and_recovery#Update_units_and_transactions\|Update units and transactions]] for more information.</p>		<p>When <var>More</var> follows another command that does not automatically end its own update unit (for example, <var>[[DEFINE FIELD command\|DEFINE FIELD]]</var>), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. See [[File_integrity_and_recovery#Update_units_and_transactions\|Update units and transactions]] for more information.</p>

	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

Dme: /* Syntax */

2015-01-25T10:46:48Z

Syntax

← Older revision		Revision as of 10:46, 25 January 2015
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax">~~MORE~~		<p class="syntax">More</p>
	</p>
	==Usage notes==		==Usage notes==
	<p>A User Language request normally is preceded by a BEGIN command and concluded by an END statement. However, if the BEGIN is replaced by the MORE command, <var class="product">Model 204</var> considers the request that follows to be a continuation of the previous request. The continued request can refer to statement labels and other information contained in the previous request.</p>		<p>A User Language request normally is preceded by a BEGIN command and concluded by an END statement. However, if the BEGIN is replaced by the MORE command, <var class="product">Model 204</var> considers the request that follows to be a continuation of the previous request. The continued request can refer to statement labels and other information contained in the previous request.</p>

ELowell at 22:38, 11 December 2013

2013-12-11T22:38:37Z

← Older revision		Revision as of 22:38, 11 December 2013
Line 47:		Line 47:
	<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>		<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>
	<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var>.</p>		<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var>.</p>
	<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. See [[~~File_Integrity_and_Recovery~~#Update_units_and_transactions\|Update units and transactions]] for more information.</p>		<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. See [[File_integrity_and_recovery#Update_units_and_transactions\|Update units and transactions]] for more information.</p>

	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Usage notes */

2013-10-22T18:33:09Z

Usage notes

← Older revision		Revision as of 18:33, 22 October 2013
Line 47:		Line 47:
	<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>		<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>
	<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var>.</p>		<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var>.</p>
	<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. ~~For~~ more information ~~about <var class="product">Model 204</var> update units, see the <var class="book">Model 204 File Manager's Guide</var>~~.</p>		<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. See [[File_Integrity_and_Recovery#Update_units_and_transactions\|Update units and transactions]] for more information.</p>

	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

JALWiccan: Automatically generated page update

2013-04-20T01:26:34Z

Automatically generated page update

← Older revision		Revision as of 01:26, 20 April 2013
Line 47:		Line 47:
	<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>		<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>
	<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var>.</p>		<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var>.</p>
	<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.</p>		<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var class="book">Model 204 File Manager's Guide</var>.</p>
	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL at 01:20, 20 April 2013

2013-04-20T01:20:53Z

← Older revision		Revision as of 01:20, 20 April 2013
Line 46:		Line 46:
	<p>Request continuation is used to break up requests that otherwise would be too large to run (that is, would exhaust work table space), or to increase user interaction with <var class="product">Model 204</var> without increasing retrieval costs.</p>		<p>Request continuation is used to break up requests that otherwise would be too large to run (that is, would exhaust work table space), or to increase user interaction with <var class="product">Model 204</var> without increasing retrieval costs.</p>
	<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>		<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>
	<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var></p>		<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var>.</p>
	<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.</p>		<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.</p>
	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

JALWiccan: Automatically generated page update

2013-04-20T01:07:14Z

Automatically generated page update

← Older revision		Revision as of 01:07, 20 April 2013
Line 46:		Line 46:
	<p>Request continuation is used to break up requests that otherwise would be too large to run (that is, would exhaust work table space), or to increase user interaction with <var class="product">Model 204</var> without increasing retrieval costs.</p>		<p>Request continuation is used to break up requests that otherwise would be too large to run (that is, would exhaust work table space), or to increase user interaction with <var class="product">Model 204</var> without increasing retrieval costs.</p>
	<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>		<p>If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.</p>
	<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var>Model 204 User Language Manual.</var></p>		<p>After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var class="book">Model 204 User Language Manual</var></p>
	<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.</p>		<p>When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.</p>
	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:05:16Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>Any user
<dt>Function
<dd>Indicates to <var class="product">Model 204</var> that the next User Language request is a continuation of the previous request
</dl>
==Syntax==
MORE

==Usage notes==
A User Language request normally is preceded by a BEGIN command and concluded by an END statement. However, if the BEGIN is replaced by the MORE command, <var class="product">Model 204</var> considers the request that follows to be a continuation of the previous request. The continued request can refer to statement labels and other information contained in the previous request.
A request that is to be continued must be concluded by: 
END MORE

not simply by END.
The following example shows the use of the MORE command:
BEGIN
.
.
.
User Language statement(s)
.
.
.
END MORE
request output
.
.
.
command(s)
.
.
.
MORE
.
.
.
User Language statement(s)
.
.
.
END
request output

Request continuation is used to break up requests that otherwise would be too large to run (that is, would exhaust work table space), or to increase user interaction with <var class="product">Model 204</var> without increasing retrieval costs.
If a request ends with an END MORE USE statement, the USE data set is left open after the request has been completed. This allows a continuation to add to the USE output without having the page number reset.
After <var class="product">Model 204</var> encounters an END that does not have a MORE argument, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in the <var>Model 204 User Language Manual.</var>
When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.
[[Category: General user commands]]
[[Category:Commands]]