BEGIN command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Automatically generated page update)
 
 
(13 intermediate revisions by 5 users not shown)
Line 4: Line 4:
<dd>User
<dd>User
<dt>Function
<dt>Function
<dd>Specifies the beginning of a User Language request
<dd>Specifies the beginning of a User Language [[Introduction_to_User_Language#Request_structure|request]]
</dl>
</dl>
==Syntax==
==Syntax==
<p class="syntax">BEGIN
<p class="syntax"><b>B</B>EGIN
</p>
</p>
==Example==
==Example==
<p class="code">BEGIN  
<p class="code">BEGIN  
Line 19: Line 21:
</p>
</p>
==Usage notes==
==Usage notes==
<p>Every User Language request must be preceded by a BEGIN command or a MORE command and concluded by an END statement. After encountering a BEGIN command, <var class="product">Model&nbsp;204</var> assumes that every input line entered by the user is a User Language statement (or a portion of a statement), until the user specifies an END statement.</p>
<p>
<p>Output from a User Language request appears on the user's terminal unless a USE command directs the output to an alternate device.</p>
Every SOUL request must be preceded by either the <var>Begin</var> or <var>[[MORE command|More]]</var> command and must be concluded by an <var>[[End statement|End]]</var> statement. After encountering a <var>Begin</var> command, <var class="product">Model&nbsp;204</var> assumes that every user input line is a SOUL statement (or a portion of a statement), until the <var>End</var> statement is processed.</p>
<p>A BEGIN command is required even when a request is embedded in a stored procedure. User Language requests are described in detail in the <var>Model&nbsp;204 User Language Manual</var>. </p>
<p>
<p>When BEGIN 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. For more information about <var class="product">Model&nbsp;204</var> update units, see the <var>Model&nbsp;204 File Manager's Guide</var>.    </p>
Output from a SOUL request appears on the user's terminal unless a <var>[[USE_command|USE]]</var> command directs the output to an alternate device.</p>
<p>
A <var>Begin</var> command is required even when a request is embedded in a stored procedure. SOUL [[Basic request structure|requests]] are described in detail in the [[:Category:SOUL|SOUL wiki pages]].</p>
<p>
When <var>Begin</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 [[File_integrity_and_recovery#Non-backoutable_update_units|non-backoutable update unit]].</p>
 
[[Category:Commands]]
[[Category:Commands]]

Latest revision as of 14:52, 6 February 2019

Summary

Privileges
User
Function
Specifies the beginning of a User Language request

Syntax

BEGIN

Example

BEGIN DRIVER: FIND ALL RECORDS FOR WHICH RECTYPE = DRIVER END FIND NUM.DRIVERS: COUNT RECORDS IN DRIVER PRINT COUNT IN NUM.DRIVERS END

Usage notes

Every SOUL request must be preceded by either the Begin or More command and must be concluded by an End statement. After encountering a Begin command, Model 204 assumes that every user input line is a SOUL statement (or a portion of a statement), until the End statement is processed.

Output from a SOUL request appears on the user's terminal unless a USE command directs the output to an alternate device.

A Begin command is required even when a request is embedded in a stored procedure. SOUL requests are described in detail in the SOUL wiki pages.

When Begin 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.