MORE command: Difference between revisions
No edit summary |
|||
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 [[ | <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]] |
Revision as of 22:38, 11 December 2013
Summary
- Privileges
- Any user
- Function
- Indicates to Model 204 that the next User Language request is a continuation of the previous request
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, 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 . . . 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 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 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 Model 204 User Language Manual.
When MORE follows another command that does not automatically end its own update unit (for example, DEFINE), Model 204 ends any update unit in progress and begins a non-backoutable update unit. See Update units and transactions for more information.