MORE command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
 
(2 intermediate revisions 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&nbsp;204</var> that the next User Language request is a continuation of the previous request
<dd>Indicates to <var class="product">Model&nbsp;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 BEGIN command and concluded by an END statement. However, if the BEGIN is replaced by the MORE command, <var class="product">Model&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;204 User Language Manual</var>.</p>
<p>After <var class="product">Model&nbsp;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&nbsp;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&nbsp;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]]

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.