MORE command: Difference between revisions
No edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| 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 | <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 | <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 | ||
| 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: | [[Category: User commands]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
Latest revision as of 16:12, 22 March 2017
Summary
- Privileges
- Any user
- Function
- Indicates to Model 204 that the next SOUL request is a continuation of the previous request
Syntax
More
Usage notes
A SOUL request normally is preceded by a Begin command and concluded by an End statement. However, if the More command is used rather than Begin, Model 204 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 . . . SOUL statement(s) . . . end more request output . . . command(s) . . . more . . . SOUL 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 Model 204 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 Model 204 encounters an End statement without More, it does not consider subsequent requests to be continuations. Request continuation is described in greater detail in Large request considerations.
When More follows another command that does not automatically end its own update unit (for example, DEFINE FIELD), Model 204 ends any update unit in progress and begins a non-backoutable update unit. See Update units and transactions for more information.