Basic request structure - Revision history

JAL: /* Cancelling a request */ link repair

2018-01-02T21:51:31Z

Cancelling a request: link repair

← Older revision		Revision as of 21:51, 2 January 2018
Line 405:		Line 405:
	===Cancelling a request===		===Cancelling a request===
	<p>		<p>
	The <var>*CANCEL</var> command or the attention key can be used to terminate certain types of processing. The key used as the attention key depends upon the terminal or access method being used. Refer to the ~~<var class="book">~~[[~~Media~~:~~M204_TerminalUserGuide_V75.pdf~~\|~~Rocket Model 204~~ Terminal ~~User's Guide~~]]~~</var> for~~ a detailed description of the attention key used for each terminal or access method. </p>		The <var>*CANCEL</var> command or the attention key can be used to terminate certain types of processing. The key used as the attention key depends upon the terminal or access method being used. Refer to the [[:Category:Terminal processing and support\|Category:Terminal processing and support]] page to locate a detailed description of the attention key used for each terminal or access method. </p>
	<p>		<p>
	These methods of cancellation are most helpful to the user who is receiving unexpected responses or prompts from <var class="product">Model 204</var>. When a request is being entered, the cancellation has the same effect as <var>End NoRun</var>. Control is returned to command level. </p>		These methods of cancellation are most helpful to the user who is receiving unexpected responses or prompts from <var class="product">Model 204</var>. When a request is being entered, the cancellation has the same effect as <var>End NoRun</var>. Control is returned to command level. </p>
Line 412:		Line 412:
	<ul>		<ul>
	<li>[[On statement\|On units]]</li>		<li>[[On statement\|On units]]</li>
	~~</li>~~
	<li>[[Procedures#Using CANCEL to return to command level\|Using CANCEL to return to command level]]</li>		<li>[[Procedures#Using CANCEL to return to command level\|Using CANCEL to return to command level]]</li>
	~~</li>~~
	</ul>		</ul>

	[[Category:SOUL]]		[[Category:SOUL]]

JAL: link repair

2015-01-26T18:21:25Z

link repair

← Older revision		Revision as of 18:21, 26 January 2015
Line 402:		Line 402:
	<p>		<p>
	<var>End More</var> terminates the request but allows continuation of the request with the <var>[[MORE command\|More]]</var> command. Specifying <var>Use</var> in addition to <var>More</var> keeps any USE dataset in effect open for the request continuation.</p>		<var>End More</var> terminates the request but allows continuation of the request with the <var>[[MORE command\|More]]</var> command. Specifying <var>Use</var> in addition to <var>More</var> keeps any USE dataset in effect open for the request continuation.</p>

	===Cancelling a request===		===Cancelling a request===
	<p>		<p>
	The *CANCEL command or the attention key can be used to terminate certain types of processing. The key used as the attention key depends upon the terminal or access method being used. Refer to the <var class="book">Rocket Model 204 Terminal User's Guide</var> for a detailed description of the attention key used for each terminal or access method. </p>		The <var>*CANCEL</var> command or the attention key can be used to terminate certain types of processing. The key used as the attention key depends upon the terminal or access method being used. Refer to the <var class="book">[[Media:M204_TerminalUserGuide_V75.pdf\|Rocket Model 204 Terminal User's Guide]]</var> for a detailed description of the attention key used for each terminal or access method. </p>
	<p>		<p>
	These methods of cancellation are most helpful to the user who is receiving unexpected responses or prompts from <var class="product">Model 204</var>. When a request is being entered, the cancellation has the same effect as ~~END NORUN~~. Control is returned to command level. </p>		These methods of cancellation are most helpful to the user who is receiving unexpected responses or prompts from <var class="product">Model 204</var>. When a request is being entered, the cancellation has the same effect as <var>End NoRun</var>. Control is returned to command level. </p>
	<p>		<p>
	Additional information:</p>		Additional information:</p>

Dme: /* Compilation termination and request cancellation */

2015-01-25T11:00:24Z

Compilation termination and request cancellation

← Older revision		Revision as of 11:00, 25 January 2015
Line 387:		Line 387:

	==Compilation termination and request cancellation==		==Compilation termination and request cancellation==

	===Stopping compilation===		<div id="Stopping compilation"></div>
			<div id="endStmt"></div>
			===Stopping compilation: the End statement===
			<!--Caution: <div>s above-->
			The syntax of the <var>End</var> statment is:
			<p class="syntax">End [NoRun] [More [Use]]</p>
	<p>		<p>
	If you are entering a request and want to stop after compilation and before evaluation, you can enter this statement: </p>		If you are entering a request and want to stop after compilation and before evaluation, you can enter this statement: </p>
	<p class="code">~~END NORUN~~		<p class="code">end norun
	</p>		</p>
	<p>		<p>
	~~END NORUN~~ terminates the request and returns you to command level. The request is stored as temporary procedure 0. For more information about temporary procedures, refer to [[Procedures#Procedures\|Procedures]].</p>		<var>End NoRun</var> terminates the request and returns you to command level. The request is stored as temporary procedure 0. For more information about temporary procedures, refer to [[Procedures#Procedures\|Procedures]].</p>
			<p>
			<var>End More</var> terminates the request but allows continuation of the request with the <var>[[MORE command\|More]]</var> command. Specifying <var>Use</var> in addition to <var>More</var> keeps any USE dataset in effect open for the request continuation.</p>
	===Cancelling a request===		===Cancelling a request===
	<p>		<p>

Dme at 21:00, 23 January 2015

2015-01-23T21:00:49Z

← Older revision		Revision as of 21:00, 23 January 2015
Line 1:		Line 1:
	<p>		<p>
	~~User Language~~ statements are grouped together into requests. Requests can retrieve specific sets of records, operate on each record retrieved one-by-one or as a set, and display or save data from the retrieved records. A single request can perform one or more of these functions. <var class="product">Model 204</var> requests are processed as a unit. </p>		SOUL statements are grouped together into requests. Requests can retrieve specific sets of records, operate on each record retrieved one-by-one or as a set, and display or save data from the retrieved records. A single request can perform one or more of these functions. <var class="product">Model 204</var> requests are processed as a unit. </p>
	<p>		<p>
	The statements are read in and compiled, any diagnostic messages are displayed, and the request is executed if no errors have occurred.</p>		The statements are read in and compiled, any diagnostic messages are displayed, and the request is executed if no errors have occurred.</p>

Dme at 19:18, 2 June 2014

2014-06-02T19:18:58Z

← Older revision		Revision as of 19:18, 2 June 2014
Line 404:		Line 404:
	Additional information:</p>		Additional information:</p>
	<ul>		<ul>
	<li>[[~~Subroutines#ON units~~\|ON units]]</li>		<li>[[On statement\|On units]]</li>
	</li>		</li>
	<li>[[Procedures#Using CANCEL to return to command level\|Using CANCEL to return to command level]]</li>		<li>[[Procedures#Using CANCEL to return to command level\|Using CANCEL to return to command level]]</li>

JAL: /* Statement numbers */

2014-05-01T15:10:04Z

Statement numbers

← Older revision		Revision as of 15:10, 1 May 2014
Line 133:		Line 133:
	For compatibility with older <var class="product">Model 204</var> releases, statement numbers can be used to label and refer to statements. </p>		For compatibility with older <var class="product">Model 204</var> releases, statement numbers can be used to label and refer to statements. </p>
	<p>		<p>
	However, Rocket Technical Support strongly recommends using statement labels instead of statement numbers. Refer to [[Obsolete features]] for the rules for numbering statements. </p>		However, [[Contacting Rocket Software Technical Support\|Rocket Technical Support]] strongly recommends using statement labels instead of statement numbers. Refer to [[Obsolete features]] for the rules for numbering statements. </p>

	==User language blocks==		==User language blocks==

JAL: /* Input lines for statements */

2014-05-01T14:44:20Z

Input lines for statements

← Older revision		Revision as of 14:44, 1 May 2014
Line 65:		Line 65:
	===Input lines for statements===		===Input lines for statements===
	<p>		<p>
	Each ~~User Language~~ statement begins a new input line.</p>		Each SOUL statement begins a new input line.</p>
	<p>		<p>
	Statement entry can begin in any column. When a statement is too long to fit on one line, a special symbol is used to continue the statement on the next line. See [[#Use of hyphens\|Use of hyphens]] for more information on line continuation.</p>		Statement entry can begin in any column. When a statement is too long to fit on one line, a special symbol is used to continue the statement on the next line. See [[#Use of hyphens\|Use of hyphens]] for more information on line continuation.</p>
	<p>		<p>
	Indentation is used throughout ~~this manual~~ to make the structure of a request more obvious to the reader. Indentation is not a requirement of ~~User Language~~. </p>		Indentation is used throughout the SOUL documentation to make the structure of a request more obvious to the reader. Indentation is not a requirement of SOUL. </p>

	===Spaces between words===		===Spaces between words===

Admin: Admin moved page Basic Request Structure to Basic request structure without leaving a redirect: title caps

2014-01-02T21:36:39Z

Admin moved page Basic Request Structure to Basic request structure without leaving a redirect: title caps

← Older revision	Revision as of 21:36, 2 January 2014
(No difference)

JAL at 17:53, 2 January 2014

2014-01-02T17:53:20Z

← Older revision		Revision as of 17:53, 2 January 2014
Line 133:		Line 133:
	For compatibility with older <var class="product">Model 204</var> releases, statement numbers can be used to label and refer to statements. </p>		For compatibility with older <var class="product">Model 204</var> releases, statement numbers can be used to label and refer to statements. </p>
	<p>		<p>
	However, Rocket Technical Support strongly recommends using statement labels instead of statement numbers. Refer to [[Obsolete ~~Features#Obsolete Features\|Obsolete Features~~]] for the rules for numbering statements. </p>		However, Rocket Technical Support strongly recommends using statement labels instead of statement numbers. Refer to [[Obsolete features]] for the rules for numbering statements. </p>

	==User language blocks==		==User language blocks==

JAL at 16:53, 2 January 2014

2014-01-02T16:53:44Z

← Older revision		Revision as of 16:53, 2 January 2014
Line 207:		Line 207:
	</p>		</p>
	<p>		<p>
	See [[Record ~~Loops~~#Specify retrieval criteria on one logical line\|Specify retrieval criteria on one logical line]] for information about line continuation with FR WHERE statements.</p>		See [[Record loops#Specify retrieval criteria on one logical line\|Specify retrieval criteria on one logical line]] for information about line continuation with FR WHERE statements.</p>

	===Alternate line continuation method===		===Alternate line continuation method===