Basic SOUL statements and commands - Revision history

Dme: /* Processing a VALUE IN clause */

2018-06-19T00:20:23Z

Processing a VALUE IN clause

← Older revision		Revision as of 00:20, 19 June 2018
Line 122:		Line 122:
	You can incorporate a <var>Value In</var> clause in the following SOUL statements: </p>		You can incorporate a <var>Value In</var> clause in the following SOUL statements: </p>
	<ul>		<ul>
	<li><var>Find All Records</var>: see <i>retrieval-conditions</i> in [[#FIND ALL RECORDS statement\|~~FIND ALL RECORDS statement~~]]</li>		<li><var>Find All Records</var>: see <i>retrieval-conditions</i> in the <var>[[#FIND ALL RECORDS statement\|Find All Records]]</var> statement</li>

	<li><var>Find All Values</var>: see [[Value loops#FIND ALL VALUES statement\|~~FIND ALL VALUES statement~~]] </li>		<li><var>Find All Values</var>: see <var>[[Value loops#FIND ALL VALUES statement\|Find All Values]]</var> statement</li>

	<li><var>For Each Record Where</var>: see [[Record loops#WhereWith\|Restricting For Each Record processing]] </li>		<li><var>For Each Record Where</var>: see [[Record loops#WhereWith\|Restricting For Each Record processing]] </li>

JAL: /* PRINT ALL INFORMATION (or PAI) statement */ add `s and repair link`

2018-06-08T00:47:50Z

PRINT ALL INFORMATION (or PAI) statement: add <var>s and repair link

← Older revision		Revision as of 00:47, 8 June 2018
Line 615:		Line 615:
	<b>Purpose</b> </p>		<b>Purpose</b> </p>
	<p>		<p>
	The ~~PRINT ALL INFORMATION~~ (or PAI) statement causes output of whole records. </p>		The <var>Print All Information</var> (or <var>PAI</var>) statement causes output of whole records. </p>
	<b>Syntax</b>		<b>Syntax</b>
	<p>		<p>
	The ~~form~~ of the PAI statement is:</p>		The format of the <var>PAI</var> statement is: </p>
	{{Template:PAI statement syntax}}		{{Template:PAI statement syntax}}
	<p>		<p>
Line 625:		Line 625:
	<li>At most one Lob option can be specified for large object display:		<li>At most one Lob option can be specified for large object display:
	<ul>		<ul>
	<li>Lob_Flod, the default, specifies output in a format that Flod can read and reload Large Object fields. The output includes the descriptor in binary format, plus the full field value.</li>		<li><var>Lob_Flod</var>, the default, specifies output in a format that Flod can read and reload Large Object fields. The output includes the descriptor in binary format, plus the full field value.</li>

	<li>Lob_Data specifies whether to display the field value. The PAI statement displays the Large Object descriptor in printable format.</li>		<li><var>Lob_Data</var> specifies whether to display the field value. The <var>PAI</var> statement displays the Large Object descriptor in printable format.</li>

	<li>Lob_Short_Data specifies to display the first 255 bytes of the field value. The PAI statement displays the Large Object descriptor in printable format.</li>		<li><var>Lob_Short_Data</var> specifies to display the first 255 bytes of the field value. The <var>PAI</var> statement displays the Large Object descriptor in printable format.</li>

	<li>Lob_No_Data specifies not to display the value. However, the PAI ~~statement displays the Large Object descriptor in printable format.~~</li>		<li><var>Lob_No_Data</var> specifies not to display the value. However, the <var>PAI</var>
			<li><var>Lob_None</var> specifies not to display any Large Object fields. </li>
	<li>Lob_None specifies not to display any Large Object fields.</li>
	</ul></li>		</ul></li>

	<li>~~Ctofields~~ specifies that the counter (CTO) field(s) should be printed. By default CTO fields are not printed.		<li><var>CtoFields</var> specifies that the counter (<var>CTO</var>) field(s) should be printed. By default, <var>CTO</var> fields are not printed.
	<p class="note"><b>Note:</b>		<p class="note"><b>Note:</b>
	The <var>CtoFields</var> keyword and a <var>Lob_</var>xxx keyword can be in either order, but neither of them can follow the <var>Into</var> clause. </p></li>		The <var>CtoFields</var> keyword and a <var>Lob_</var>xxx keyword can be in either order, but neither of them can follow the <var>Into</var> clause. </p></li>

	<li>The <var>Into</var> clause is not used for display purposes. It lets you move a record's field names and values into a form of storage that can be easily manipulated. For details, see [[Record loops#~~PRINT ALL INFORMATION_.28or_PAI.29_INTO statement~~\|~~PRINT ALL INFORMATION~~ (or PAI) ~~INTO~~ statement]].</li>		<li>The <var>Into</var> clause is not used for display purposes. It lets you move a record's field names and values into a form of storage that can be easily manipulated. For details, see [[Record loops#paiInto\|Print All Information (or PAI) Into statement]].</li>
	</ul>		</ul>

Line 684:		Line 683:
	</p>		</p>
	<p>		<p>
	results in output with the following format (note the inclusion of the CTO fields <code>NUMBER_OF_DRIVERS</code> and <code>NUMBER_OF_VEHICLES</code>): </p>		results in output with the following format (note the inclusion of the <var>CTO</var> fields <code>NUMBER_OF_DRIVERS</code> and <code>NUMBER_OF_VEHICLES</code>): </p>
	<p class="output">ADDRESS = 3621 GLEN CT		<p class="output">ADDRESS = 3621 GLEN CT
	POLICY_NUMBER = 100000		POLICY_NUMBER = 100000
Line 722:		Line 721:
	END</p>		END</p>
	<p>		<p>
	results in output with the following format. Note the output of the EXACTLY-ONE field first in the list, followed by the preallocated field, and finally the non-preallocated field: </p>		results in output with the following format. Note the output of the <var>EXACTLY-ONE</var> field first in the list, followed by the preallocated field, and finally the non-preallocated field: </p>
	<p class="output">EORD1 = JANE		<p class="output">EORD1 = JANE
	PORD1 = FRED		PORD1 = FRED

JAL: use syntax template for AAI stmt

2018-05-18T22:07:23Z

use syntax template for AAI stmt

Show changes

JAL: /* AUDIT ALL INFORMATION statement */ use template for syntax

2018-05-18T21:48:16Z

AUDIT ALL INFORMATION statement: use template for syntax

← Older revision		Revision as of 21:48, 18 May 2018
Line 534:		Line 534:
	(<var>CTO</var>) field(s) are audited. By default <var>CTO</var> fields are not audited.</p>		(<var>CTO</var>) field(s) are audited. By default <var>CTO</var> fields are not audited.</p>

	===~~AUDIT ALL INFORMATION~~ statement===		===Audit All Information statement===
	<b>Purpose</b>		<b>Purpose</b>
	<p>The ~~AUDIT ALL INFORMATION~~ (or AAI) statement writes the output of entire records to the [[Report generation#~~AUDIT ALL INFORMATION~~ statement\|audit trail]].</p>		<p>
	<b>Syntax</b>		The <var>Audit All Information</var> (or <var>AAI</var>) statement writes the output of entire records to the [[Report generation#Audit All Information statement\|audit trail]]. </p>
	<p>The form of the AAI statement is:</p>		<p>
	~~<p class="code">AUDIT ALL INFORMATION [CTOFIELDS]~~		<b>Syntax</b> </p>
	</p>		<p>
	<b>Where</b>		The form of the <var>AAI</var> statement is: </p>
	<p>~~CTOFIELDS~~ specifies to print the counter (CTO) field(s). By default CTO fields		{{Template:Audit All Information statement syntax}}
	are not printed.</p>		<p>
			<b>Where</b> </p>
			<p>
			<var>CtoFields</var> specifies to print the counter (CTO) field(s). By default CTO fields are not printed. </p>

	<div id="pafgiStmt"></div>		<div id="pafgiStmt"></div>

JAL: /* Find All Records statement */ add link

2018-05-11T17:35:53Z

Find All Records statement: add link

← Older revision		Revision as of 17:35, 11 May 2018
Line 86:		Line 86:
	</p>		</p>
	<p class="syntax"><span class="term">field</span> <> <span class="term">value1</span> AND <span class="term">field</span> <> <span class="term">value2</span> AND....		<p class="syntax"><span class="term">field</span> <> <span class="term">value1</span> AND <span class="term">field</span> <> <span class="term">value2</span> AND....
	</p></li>		</p>
			<p>
			For the full variety of possible retrieval conditions, see [[Statement syntax#Retrieval condition syntax\|Retrieval condition syntax]]. </p></li>
	</ul>		</ul>

Line 95:		Line 97:
	END FIND		END FIND
	</p>		</p>

	===Ending a Find statement===		===Ending a Find statement===
	<p>		<p>

JAL: /* Loop statements */ mixed case for stmts

2018-05-08T18:47:16Z

Loop statements: mixed case for stmts

← Older revision		Revision as of 18:47, 8 May 2018
Line 295:		Line 295:
	When a <var>Find</var> statement refers back to a previous found set and the found set is empty, then the loop for the <var>Find</var> statement is skipped. Performance for the <var>Find</var> processing is enhanced because no retrieval is performed. </p>		When a <var>Find</var> statement refers back to a previous found set and the found set is empty, then the loop for the <var>Find</var> statement is skipped. Performance for the <var>Find</var> processing is enhanced because no retrieval is performed. </p>

	===~~FOR EACH RECORD~~ statement===		===For Each Record statement===
	<p>		<p>
	Use the <var>For Each Record</var> statement to refer to each record within a set of records located by a <var>Find</var> statement. </p>		Use the <var>For Each Record</var> statement to refer to each record within a set of records located by a <var>Find</var> statement. </p>

JAL: misc formatting

2018-05-04T20:00:40Z

misc formatting

← Older revision		Revision as of 20:00, 4 May 2018
Line 1:		Line 1:
	~~<!-- statement, fdwol -->~~
	<p>		<p>
	This page discusses in more detail the basic statements that can be used within a request. This ~~chapter~~ also presents the system control commands that you commonly use during a terminal session. There are many more ~~User Language~~ statements and [[:Category:Commands\|commands]] than are presented here.</p>		This page discusses in more detail the basic statements that can be used within a request. This page also presents the system control commands that you commonly use during a terminal session. There are many more SOUL statements and [[:Category:Commands\|commands]] than are presented here. </p>
	__TOC__		__TOC__

	==System control commands==		==System control commands==
	<p>		<p>
	Before learning about ~~User Language~~ statements, it is important to understand the role of <var class="product">Model 204</var> commands that are required for basic request processing.</p>		Before learning about SOUL statements, it is important to understand the role of <var class="product">Model 204</var> commands that are required for basic request processing. </p>

	===Use of commands with requests===		===Use of commands with requests===
	<p>		<p>
	System control commands are used outside requests to perform system level operations such as opening files and saving requests. Although system control commands are not part of ~~User Language~~, many commands you might find useful are ~~illustrated~~ in examples ~~throughout this manual~~. </p>		System control commands are used outside requests to perform system level operations such as opening files and saving requests. Although system control commands are not part of SOUL, many commands you might find useful are found in examples of SOUL constructs. </p>
	<p>		<p>
	Complete descriptions of these and other commands are included in [[:Category:Commands\|commands]]. </p>		Complete descriptions of these and other commands are included in [[:Category:Commands\|commands]]. </p>

	===Key commands===		===Key commands===
	<p>		<p>
	The following system control commands are essential to allow ~~User Language~~ requests to function: </p>		The following system control commands are essential to allow SOUL requests to function: </p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 22:		Line 21:
	<th>Action</th>		<th>Action</th>
	</tr>		</tr>

	<tr>		<tr>
	<td><var>[[BEGIN command\|BEGIN]]</var></td>		<td><var>[[BEGIN command\|BEGIN]]</var></td>
	<td>Initiates a User Language request.</td>		<td>Initiates a User Language request.</td>
	</tr>		</tr>

	<tr>		<tr>
	<td><var>[[OPEN FILE command\|OPEN]]</var> </td>		<td><var>[[OPEN FILE command\|OPEN]]</var> </td>
	<td>Opens a <var class="product">Model 204</var> file or group. See [[Files, groups, and reference context#OPEN statement and OPENC statement\|Open statement and OpenC statement]] for a detailed discussion of the OPEN statement. Refer to [[#IN clauses\|IN clauses]] for a discussion of using the IN clause when several files are open.</td>		<td>Opens a <var class="product">Model 204</var> file or group. See [[Files, groups, and reference context#OPEN statement and OPENC statement\|Open statement and OpenC statement]] for a detailed discussion of the OPEN statement. Refer to [[#IN clauses\|IN clauses]] for a discussion of using the IN clause when several files are open.</td>
	</tr>		</tr>

	<tr>		<tr>
	<td><var>[[CLOSE command\|CLOSE]]</var> </td>		<td><var>[[CLOSE command\|CLOSE]]</var> </td>
	<td>Closes a <var class="product">Model 204</var> file or group that has been opened. </td>		<td>Closes a <var class="product">Model 204</var> file or group that has been opened. </td>
	</tr>		</tr>
	</table>		</table>
	<p>		<p>
	The MORE command and ~~END MORE~~ statement are discussed in the ~~section~~ [[#Request continuation\|Request continuation]] and in [[Large request considerations]].</p>		The <var>MORE</var> command and <var>End More</var> statement are discussed in the [[#Request continuation\|Request continuation]] and [[Large request considerations]] sections. </p>

	<~~div~~ id="findRecords"></~~div>~~		==<b id="findRecords"></b>Find statement==
	~~<div id="FIND statement"></div~~> ~~<!-- In case of existing links -->~~

	==Find statement== ~~<!-- Note <div>s above -->~~
	<p>		<p>
	You can retrieve sets of records, records with specified characteristics, and individual records. </p>		You can retrieve sets of records, records with specified characteristics, and individual records. </p>
	<p>		<p>
	The basic retrieval statement in SOUL is the <var>Find</var> statement. Several forms of the <var>Find</var> statement are provided for basic and complex retrievals. Basic retrieval statements are discussed in this topic. See [[Record retrievals]] for a discussion of more complex retrieval statements. </p>		The basic retrieval statement in SOUL is the <var>Find</var> statement. Several forms of the <var>Find</var> statement are provided for basic and complex retrievals. Basic retrieval statements are discussed in this topic. See [[Record retrievals]] for a discussion of more complex retrieval statements. </p>
			<p>
	<p>The complete syntax is presented on the <var>[[Find Records statement\|Find Records]]</var> statement page, including its various forms such as <var>Find Without Locks</var> (which is abbreviated <var>FDWOL</var>). </p>		The complete syntax is presented on the <var>[[Find Records statement\|Find Records]]</var> statement page, including its various forms such as <var>Find Without Locks</var> (which is abbreviated <var>FDWOL</var>). </p>

	===Find All Records statement===		===Find All Records statement===
	<b>Syntax</b>		<b>Syntax</b>
	<p>		<p>
	The syntax for retrieving records in a <var class="product">Model 204</var> file is: </p>		The syntax for retrieving records in a <var class="product">Model 204</var> file is: </p>
	<p class="syntax"><span class="term">label</span>: Find All Records		<p class="syntax"><span class="term">label</span>: Find All Records

Line 75:		Line 74:
	<li><var class="term">listname</var> specifies a list from a preceding <var>Find</var> statement.</li>		<li><var class="term">listname</var> specifies a list from a preceding <var>Find</var> statement.</li>

	<li>The <i>retrieval-conditions</i> can be:~~</li>~~		<li>The <i>retrieval-conditions</i> can be:
	<p class="syntax">[<span class="term">fieldname</span> {Eq \| Ne} Value In <span class="term">value_set</span>] </p~~></li>~~		<p class="syntax">[<span class="term">fieldname</span> {Eq \| Ne} Value In <span class="term">value_set</span>] </p>
	~~</ul~~>
	<p>		<p>
	<var class="term">fieldname</var> identifies the field from which to retrieve values. </p>		<var class="term">fieldname</var> identifies the field from which to retrieve values. </p>
Line 88:		Line 86:
	</p>		</p>
	<p class="syntax"><span class="term">field</span> <> <span class="term">value1</span> AND <span class="term">field</span> <> <span class="term">value2</span> AND....		<p class="syntax"><span class="term">field</span> <> <span class="term">value1</span> AND <span class="term">field</span> <> <span class="term">value2</span> AND....
	</p>		</p></li>
			</ul>

	<b>Example</b>		<b>Example</b>
	<p>		<p>
Line 98:		Line 98:
	===Ending a Find statement===		===Ending a Find statement===
	<p>		<p>
	Except where noted ~~in this manual~~, you must end a <var>Find</var> statement with either an <var>End Find</var> statement or a label. A <var>Find</var> statement cannot be ended by an <var>End Block</var> statement. </p>		Except where explicitly noted, you must end a <var>Find</var> statement with either an <var>End Find</var> statement or a label. A <var>Find</var> statement cannot be ended by an <var>End Block</var> statement. </p>
	<b>Syntax</b>		<b>Syntax</b>
	<p>		<p>
	The format of the <var>End Find</var> statement is: ~~</p>~~		The format of the <var>End Find</var> statement is:
	</p>		</p>
	<p class="syntax">End Find [<span class="term">label</span>]		<p class="syntax">End Find [<span class="term">label</span>]

JAL: mixed case for statements

2018-05-04T19:39:41Z

mixed case for statements

← Older revision		Revision as of 19:39, 4 May 2018
Line 45:		Line 45:
	You can retrieve sets of records, records with specified characteristics, and individual records. </p>		You can retrieve sets of records, records with specified characteristics, and individual records. </p>
	<p>		<p>
	The basic retrieval statement in ~~User Language~~ is the ~~FIND~~ statement. Several forms of the ~~FIND~~ statement are provided for basic and complex retrievals. Basic retrieval statements are discussed in this ~~chapter~~. See [[Record retrievals~~\|"Record retrievals"~~]] for a discussion of more complex retrieval statements. </p>		The basic retrieval statement in SOUL is the <var>Find</var> statement. Several forms of the <var>Find</var> statement are provided for basic and complex retrievals. Basic retrieval statements are discussed in this topic. See [[Record retrievals]] for a discussion of more complex retrieval statements. </p>

	<p>The complete syntax is presented on the <var>[[Find Records statement\|Find Records]]</var> statement page, including its various forms such as <var>Find Without Locks</var> (which is abbreviated <var>FDWOL</var>).</p>		<p>The complete syntax is presented on the <var>[[Find Records statement\|Find Records]]</var> statement page, including its various forms such as <var>Find Without Locks</var> (which is abbreviated <var>FDWOL</var>). </p>

	===Find All Records statement===		===Find All Records statement===
	<b>Syntax</b>		<b>Syntax</b>
	<p>		<p>
	The syntax for retrieving records in a <var class="product">Model 204</var> file is:</p>		The syntax for retrieving records in a <var class="product">Model 204</var> file is: </p>
	<p class="syntax"><span class="term">label</span>: ~~FIND ALL RECORDS~~		<p class="syntax"><span class="term">label</span>: Find All Records

	[IN {~~FILE~~ <span class="term">filename</span> \| ~~GROUP~~ <span class="term">groupname</span>}] -		[In {File <span class="term">filename</span> \| Group <span class="term">groupname</span>}] -

	~~FIND~~ [~~AND RESERVE~~] [~~ALL~~] ~~RECORDS~~ -		Find [And Reserve] [All] Records -

	[IN <span class="term">label</span> \| ON [~~LIST~~] <span class="term">listname</span>] -		[In <span class="term">label</span> \| On [List] <span class="term">listname</span>] -

	~~FOR WHICH~~ \| ~~WITH~~] <span class="term">retrieval-conditions</span>		For Which \| With] <span class="term">retrieval-conditions</span>
			. . .
	~~. .~~ . . .		End Find
	~~END FIND~~
	</p>		</p>
	<b>Where</b>		<b>Where</b>
	<ul>		<ul>
	<li><i>filename</i> specifies the file that has the records you want to retrieve.</li>		<li><var class="term">filename</var> specifies the file that has the records you want to retrieve.</li>
	~~</li>~~
	<li><i>groupname</i> specifies the group of files that has the records you want to retrieve.</li>		<li><var class="term">groupname</var> specifies the group of files that has the records you want to retrieve.</li>
	~~</li>~~
	<li><i>label</i> specifies the label of a preceding ~~FIND~~ statement. </li>		<li><var class="term">label</var> specifies the label of a preceding <var>Find</var> statement. </li>
	~~</li>~~
	<li><i>listname</i> specifies a list from a preceding ~~FIND~~ statement.</li>		<li><var class="term">listname</var> specifies a list from a preceding <var>Find</var> statement.</li>
	~~</li>~~
	<li>The <i>retrieval-conditions</i> can be:</li>		<li>The <i>retrieval-conditions</i> can be:</li>
	<p class="syntax">[<span class="term">fieldname</span> {EQ \| NE} ~~VALUE IN~~ <span class="term">value_set</span>]		<p class="syntax">[<span class="term">fieldname</span> {Eq \| Ne} Value In <span class="term">value_set</span>] </p></li>
	</p></li>
	</ul>		</ul>
	<p>		<p>
	<i>fieldname</i> identifies the field from which to retrieve values.</p>		<var class="term">fieldname</var> identifies the field from which to retrieve values. </p>
	<p>		<p>
	The <i>value_set</i> label represents an existing value set. Values of the value set in the ~~EQ VALUE IN~~ <i>value_set</i> clause are treated as boolean OR, for example:~~</p>~~		The <var class="term">value_set</var> label represents an existing value set. Values of the value set in the <var>Eq Value In <i>value_set</i></var> clause are treated as boolean OR, for example:
	~~<p class="syntax"><span class="term">field</span> = <span class="term">value1</span> OR <span class="term">field</span> = <span class="term">value2</span> OR....~~
	</p>		</p>
			<p class="syntax"><span class="term">field</span> = <span class="term">value1</span> OR <span class="term">field</span> = <span class="term">value2</span> OR.... </p>
	<p>		<p>
	The ~~NE VALUE IN~~ <i>value_set</i> clause is likewise treated as boolean AND, for example:</p>		The <var>Ne Value In <i>value_set</i></var> clause is likewise treated as boolean AND, for example:
			</p>
	<p class="syntax"><span class="term">field</span> <> <span class="term">value1</span> AND <span class="term">field</span> <> <span class="term">value2</span> AND....		<p class="syntax"><span class="term">field</span> <> <span class="term">value1</span> AND <span class="term">field</span> <> <span class="term">value2</span> AND....
	</p>		</p>
	<b>Example</b>		<b>Example</b>
	<p>		<p>
	A basic ~~FIND~~ statement is coded as follows: </p>		A basic <var>Find</var> statement is coded as follows: </p>
	<p class="code">FIND.RECS: FIND ALL RECORDS		<p class="code">FIND.RECS: FIND ALL RECORDS
	END FIND		END FIND
Line 99:		Line 98:
	===Ending a Find statement===		===Ending a Find statement===
	<p>		<p>
	Except where noted in this manual, you must end a ~~FIND~~ statement with either an ~~END FIND~~ statement or a label. A ~~FIND~~ statement cannot be ended by an ~~END BLOCK~~ statement. </p>		Except where noted in this manual, you must end a <var>Find</var> statement with either an <var>End Find</var> statement or a label. A <var>Find</var> statement cannot be ended by an <var>End Block</var> statement. </p>
	<b>Syntax</b>		<b>Syntax</b>
	<p>		<p>
	The format of the ~~END FIND~~ statement is:</p>		The format of the <var>End Find</var> statement is: </p>
	<p class="syntax">~~END FIND~~ [<span class="term">label</span>]		</p>
			<p class="syntax">End Find [<span class="term">label</span>]
	</p>		</p>
	<p>		<p>
	In addition, the retrieval conditions of a ~~FIND~~ statement must not be labeled, even if they begin new lines.</p>		In addition, the retrieval conditions of a <var>Find</var> statement must not be labeled, even if they begin new lines.</p>

	===Large Object data support===		===Large Object data support===
	<p>		<p>
	The ~~FIND~~ statement supports Large Object data in the following format:</p>		The <var>Find</var> statement supports Large Object data in the following format:</p>
	<p class="syntax">~~FIND~~ <span class="term">lob-fieldname</span> IS [~~NOT~~] ~~PRESENT~~		<p class="syntax">Find <span class="term">lob-fieldname</span> Is [Not] Present
	</p>		</p>

JAL: /* Processing a VALUE IN clause */ link repair

2018-05-03T18:31:27Z

Processing a VALUE IN clause: link repair

← Older revision		Revision as of 18:31, 3 May 2018
Line 124:		Line 124:
	<li><var>Find All Values</var>: see [[Value loops#FIND ALL VALUES statement\|FIND ALL VALUES statement]] </li>		<li><var>Find All Values</var>: see [[Value loops#FIND ALL VALUES statement\|FIND ALL VALUES statement]] </li>

	<li><var>For Each Record Where</var>: see [[Record loops#~~Restricting For Each Record processing~~\|Restricting For Each Record processing]] </li>		<li><var>For Each Record Where</var>: see [[Record loops#WhereWith\|Restricting For Each Record processing]] </li>
	</ul>		</ul>
	<p>		<p>

JAL: /* FIND ALL RECORDS FOR WHICH/WITH statement */ mixed case for stmts

2018-05-03T18:27:01Z

FIND ALL RECORDS FOR WHICH/WITH statement: mixed case for stmts

← Older revision		Revision as of 18:27, 3 May 2018
Line 162:		Line 162:
	<p>		<p>
	The basic statement for retrieving data based on specific retrieval conditions is: </p>		The basic statement for retrieving data based on specific retrieval conditions is: </p>
	<p class="syntax"><span class="term">label</span>: ~~FIND ALL RECORDS~~		<p class="syntax"><span class="term">label</span>: Find All Records {For Which \| With}

	{~~FOR WHICH~~ \| ~~WITH}~~		{<span class="term">fieldname</span>=<span class="term">value</span> \| <span class="term">fieldname</span>=<span class="term">value1</span> Or <span class="term">value2</span>

	{<span class="term">fieldname</span>=<span class="term">value~~</span> \| <span class="term">fieldname</span>=<span class="term">value1</span> OR <span class="term">value2~~</span>		\| <span class="term">fieldname</span> Not=<span class="term">value</span>

	\| <span class="term">fieldname</span> ~~NOT~~=<span class="term">~~value~~</span>		\| <span class="term">fieldname</span>=<span class="term">value1</span> And Not=<span class="term">value2</span>

	\| <span class="term">fieldname</span>=<span class="term">value1</span> ~~AND NOT=~~<span class="term">value2</span>		\| <span class="term">fieldname</span> Not=<span class="term">value1</span> Nor <span class="term">value2</span>

	\| <span class="term">fieldname</span> ~~NOT=<span class="term">value1</span> NOR~~ <span class="term">~~value2~~</span>		\| <span class="term">fieldname</span> Is Like <span class="term">pattern</span>}

	~~\| <span class="term">fieldname</span> IS LIKE <span class="term">pattern</span>}~~		\| <span class="term">fieldname</span> {Eq \| Ne} Value In <span class="term">value-set</span>

	\| <span class="term">fieldname</span> {EQ \| NE} ~~VALUE IN~~ <span class="term">value-set</span>
	</p>		</p>
	<b>Example</b>		<b>Example</b>
	<p>		<p>
	This ~~FIND ALL RECORDS FOR WHICH~~ statement directs <var class="product">Model 204</var> to look for records of blue Fords:</p>		This <var>Find All Records For Which</var> statement directs <var class="product">Model 204</var> to look for records of blue Fords:</p>
	<p class="code">FIND.RECS: FIND ALL RECORDS FOR WHICH		<p class="code">FIND.RECS: FIND ALL RECORDS FOR WHICH
	MAKE = FORD		MAKE = FORD
Line 187:		Line 185:
	</p>		</p>
	<p>		<p>
	This statement contains an ~~AND~~ implied by the fact that COLOR = BLUE appears on a separate line. Only the records containing both fields, MAKE = FORD and COLOR = BLUE, are retrieved. </p>		This statement contains an implied <var>And</var> by the fact that <code>COLOR=BLUE</code> appears on a separate line. Only the records containing both fields, <code>MAKE=FORD</code> and <code>COLOR=BLUE</code>, are retrieved. </p>

	==Using expressions for value retrieval==		==Using expressions for value retrieval==
	<p>		<p>