Using variables and values in computation - Revision history

JAL: /* Declaring %variables and %variable arrays */ insert ID

2018-05-29T17:18:54Z

Declaring %variables and %variable arrays: insert ID

← Older revision		Revision as of 17:18, 29 May 2018
Line 130:		Line 130:
	The <var>Variables Are Undefined</var> statement sets both the default <var>Len</var> and <var>Dp</var> options to 0. Therefore, when <var>Variables Are Undefined</var> is in effect, %variables declared as <var>String</var> must have the <var>Len</var> specified or an error message is issued.</p>		The <var>Variables Are Undefined</var> statement sets both the default <var>Len</var> and <var>Dp</var> options to 0. Therefore, when <var>Variables Are Undefined</var> is in effect, %variables declared as <var>String</var> must have the <var>Len</var> specified or an error message is issued.</p>

	==Declaring %variables and %variable arrays==		==<b id="Declaring"></b>Declaring %variables and %variable arrays==
	<p>		<p>
	You can declare a variable and subsequently assign and reset that variable any number of times during a SOUL request. You can use a variable declaration statement to specify:</p>		You can declare a variable and subsequently assign and reset that variable any number of times during a SOUL request. You can use a variable declaration statement to specify:</p>
Line 287:		Line 287:
	<p>		<p>
	then <code>%NAME</code> remains a string of length 30.</p>		then <code>%NAME</code> remains a string of length 30.</p>

	==%Variable types==		==%Variable types==
	<p>		<p>

JAL: /* Syntax */ add `s`

2018-05-02T16:03:31Z

Syntax: add <var>s

← Older revision		Revision as of 16:03, 2 May 2018
Line 563:		Line 563:
	<p>		<p>
	An expression has this format:</p>		An expression has this format:</p>
	<p class="code">{<span class="term">operand</span> \| (<span class="term">expression</span>)}		<p class="code">{<span class="term">operand</span> \| (<span class="term">expression</span>)} [<span class="term">operator</span> {<span class="term">operand</span> \| (<span class="term">expression</span>)}]...
	[<span class="term">operator</span> {<span class="term">operand</span> \| (<span class="term">expression</span>)}]...
	</p>		</p>
	Where:		Where:
Line 574:		Line 573:
	<li>%variable or element of %variable array</li>		<li>%variable or element of %variable array</li>

	<li>~~COUNT IN~~ label</li>		<li><var>Count In <i>label</i></var></li>

	<li>Field name</li>		<li>Field name</li>
Line 582:		Line 581:
	<li>Number</li>		<li>Number</li>

	<li>~~OCCURRENCE IN~~ label</li>		<li><var>Occurrence In <i>label</i></var></li>

	<li>Quoted string</li>		<li>Quoted string</li>

	<li>~~VALUE IN~~ label</li>		<li><var>Value In <i>label</i></var></li>
	</ul></li>		</ul></li>

	<li><var class="term">operator</var> can be arithmetic, Boolean, comparison, or concatenation.</li>		<li><var class="term">operator</var> can be arithmetic, Boolean, comparison, or concatenation.</li>
	</ul>		</ul>

	===Operator order of precedence===		===Operator order of precedence===
	<p>		<p>

JAL: /* Using expressions for value retrieval */ misc formatting

2018-05-02T15:48:58Z

Using expressions for value retrieval: misc formatting

← Older revision		Revision as of 15:48, 2 May 2018
Line 667:		Line 667:
	You can use expressions for value retrieval in the following SOUL statements:</p>		You can use expressions for value retrieval in the following SOUL statements:</p>
	<ul>		<ul>
	<li>Update statements (~~STORE RECORD~~, ~~ADD~~, ~~CHANGE~~, ~~DELETE~~, ~~INSERT~~)</li>		<li>Update statements (<var>Store Record</var>, <var>Add</var>, <var>Change</var>, <var>Delete</var>, <var>Insert</var>) </li>

	<li>~~FILE RECORDS~~</li>		<li><var>File Records</var> </li>

	<li>~~FIND~~</li>		<li><var>Find</var> </li>

	<li>~~FIND - POINT~~$ condition</li>		<li><var>Find...Point$</var> condition </li>

	<li>~~FIND - SFL~~$ and ~~SFGE~~$ conditions</li>		<li><var>Find...Sfl$</var> and <var>Find...Sfge$</var> conditions </li>

	<li>~~FOR EACH RECORD IN ORDER BY~~</li>		<li><var>For Each Record In Order By</var> </li>

	<li>~~FOR EACH RECORD WHERE~~</li>		<li><var>For Each Record Where</var> </li>

	<li>~~FIND ALL VALUES~~</li>		<li><var>Find All Values</var> </li>

	<li>~~FOR EACH VALUE~~</li>		<li><var>For Each Value</var> </li>

	<li>~~FOR RECORD NUMBER~~</li>		<li><var>For Record Number</var> </li>
	</ul>		</ul>

Line 700:		Line 700:
	<tr>		<tr>
	<td>Function call</td>		<td>Function call</td>
	<td>IN ?&~~FILE FD~~ ORDER.DATE ~~EQ VALUE~~($~~DATE~~(1,''))</td>		<td><p class="codeInTable">In ?&File Fd ORDER.DATE Eq Value(<b>$Date(1,'')</b>)</p></td>
	</tr>		</tr>

	<tr>		<tr>
	<td>String concatenation</td>		<td>String concatenation</td>
	<td>IN ?&~~FILE FD~~ BIRTH.DATE ~~EQ VALUE~~(%~~YYYY WITH~~ %~~MM WITH~~ %DD)</td>		<td><p class="codeInTable">In ?&File Fd BIRTH.DATE Eq Value(<b>%yyyy With %mm With %dd</b>)</p></td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Arithmetic operation</td>		<td>Arithmetic operation</td>
	<td>IN ?&~~FILE FD~~ SALES.VALUE ~~EQ VALUE~~(%~~ITEM~~.~~VALUE~~ * %~~ITEM~~.~~SALES~~ )</td>		<td><p class="codeInTable">In ?&File Fd SALES.VALUE Eq Value(<b>%item.value * %item.sales</b>)</p></td>
	</tr>		</tr>

	<tr>		<tr>
	<td>SOUL construct</td>		<td>SOUL construct</td>
	<td>IN ?&~~FILE FD~~ NUM.ORDERS ~~EQ VALUE~~(~~COUNT IN~~ FD.ORDERS)</td>		<td><p class="codeInTable">In ?&File Fd NUM.ORDERS Eq Value(<b>Count In FD.ORDERS</b>)</p></td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Boolean expression</td>		<td>Boolean expression</td>
	<td>IN ?&~~FILE FD~~ ORDER.STATUS ~~EQ VALUE~~(%~~STATUS IS LIKE~~ 'A*')</td>		<td><p class="codeInTable">In ?&File Fd ORDER.STATUS Eq Value(<b>%status Is Like 'A*'</b>)</p></td>
	</tr>		</tr>
	</table>		</table>
Line 796:		Line 796:
	END		END
	</p>		</p>

	==Operators==		==Operators==
	<p>		<p>

Dme: /* Understanding Initial processing */

2017-10-20T16:18:35Z

Understanding Initial processing

← Older revision		Revision as of 16:18, 20 October 2017
Line 525:		Line 525:

	===<b id="initial"></b>Understanding Initial processing===		===<b id="initial"></b>Understanding Initial processing===
			<!-- #.QA The following two requests are in QASHR regression test SOUL.SVT.001.QA -->
	<p>		<p>
	Code written using an <var>Initial</var> assignment for both %variables results in the assigned value of <code>%X</code> as the <var>Initial</var> value assigned for <code>%Y</code> as both assignments are resolved at compilation. For example:</p>		Code written using an <var>Initial</var> assignment for both %variables results in the assigned value of <code>%X</code> as the <var>Initial</var> value assigned for <code>%Y</code> as both assignments are resolved at compilation. For example:</p>

ELowell: /* Understanding Initial processing */

2017-10-19T18:54:47Z

Understanding Initial processing

← Older revision		Revision as of 18:54, 19 October 2017
Line 553:		Line 553:
	</p>		</p>
	<p>		<p>
	The <code>%X</code> value is assigned at evaluation. The <var>Initial</var> value is assigned at compilation, prior to the evaluation of <code>%X=1,</code>. The result is that <code>%Y</code> is assigned the default value, zero (0), for its type of <var>Fixed</var>.</p>		The <code>%X</code> value is assigned at evaluation. The <var>Initial</var> value is assigned at compilation, prior to the evaluation of <code>%X=1</code>. The result is that <code>%Y</code> is assigned the default value, zero (0), for its type of <var>Fixed</var>.</p>

	==Expressions==		==Expressions==

SSmirnova: /* Understanding Initial processing */

2017-10-19T18:41:33Z

Understanding Initial processing

← Older revision		Revision as of 18:41, 19 October 2017
Line 542:		Line 542:
	The following code reflects this processing:</p>		The following code reflects this processing:</p>
	<p class="code">BEGIN		<p class="code">BEGIN
			%X IS STRING LEN 1
	%X = 1		%X = 1
	* %X assigned the value of 1 at evaluation		* %X assigned the value of 1 at evaluation
Line 552:		Line 553:
	</p>		</p>
	<p>		<p>
	The <code>%X</code> value is assigned at evaluation. The <var>Initial</var> value is assigned at compilation, prior to the evaluation of <code>%X=1,/code>. The result is that <code>%Y</code> is assigned the default value, zero (0), for its type of <var>Fixed</var>.</p>		The <code>%X</code> value is assigned at evaluation. The <var>Initial</var> value is assigned at compilation, prior to the evaluation of <code>%X=1,</code>. The result is that <code>%Y</code> is assigned the default value, zero (0), for its type of <var>Fixed</var>.</p>

	==Expressions==		==Expressions==

SSmirnova: /* Understanding Initial processing */

2017-10-19T17:37:10Z

Understanding Initial processing

← Older revision		Revision as of 17:37, 19 October 2017
Line 528:		Line 528:
	Code written using an <var>Initial</var> assignment for both %variables results in the assigned value of <code>%X</code> as the <var>Initial</var> value assigned for <code>%Y</code> as both assignments are resolved at compilation. For example:</p>		Code written using an <var>Initial</var> assignment for both %variables results in the assigned value of <code>%X</code> as the <var>Initial</var> value assigned for <code>%Y</code> as both assignments are resolved at compilation. For example:</p>
	<p class="code">BEGIN		<p class="code">BEGIN
	%X IS STRING INITIAL(1)		%X IS STRING LEN 1 INITIAL(1)
	/? %X assigned the INITIAL value of 1, at compilation ?/		* %X assigned the INITIAL value of 1, at compilation
	%Y IS FIXED INITIAL(%X)		%Y IS FIXED INITIAL(%X)
	/? %Y assigned the INITIAL value of %X, at compilation ?/		* %Y assigned the INITIAL value of %X, at compilation
	PRINT 'Y = ' %Y		PRINT 'Y = ' %Y
	END		END
Line 543:		Line 543:
	<p class="code">BEGIN		<p class="code">BEGIN
	%X = 1		%X = 1
	/? %X assigned the value of 1 at evaluation ?/		* %X assigned the value of 1 at evaluation
	%Y IS FIXED INITIAL(%X)		%Y IS FIXED INITIAL(%X)
	/? %Y assigned the INITIAL value at compilation ?/		* %Y assigned the INITIAL value at compilation
	PRINT 'Y = ' %Y		PRINT 'Y = ' %Y
	END		END

Dme: /* Syntax */

2017-10-17T13:05:48Z

Syntax

← Older revision		Revision as of 13:05, 17 October 2017
Line 178:		Line 178:
	<p>		<p>
	If you want to use the <var>Common</var> attribute on a %variable declaration with the <var>Initial</var> and <var>Static</var> attributes, the <var>Common</var> attribute must be the last token in the statement. For example:</p>		If you want to use the <var>Common</var> attribute on a %variable declaration with the <var>Initial</var> and <var>Static</var> attributes, the <var>Common</var> attribute must be the last token in the statement. For example:</p>
	<p class="code">%~~X FLOAT INITIAL~~ (3) ~~STATIC COMMON~~		<p class="code">%x is float initial (3) static common
	</p></li>		</p></li>
	</ul>		</ul>

Dme: /* Syntax */

2017-10-17T13:01:04Z

Syntax

← Older revision		Revision as of 13:01, 17 October 2017
Line 155:		Line 155:
	<p class="syntax">[Declare] <span class="term">%variable</span> [Is] {Fixed [Dp <span class="term">n</span>] \| Float}		<p class="syntax">[Declare] <span class="term">%variable</span> [Is] {Fixed [Dp <span class="term">n</span>] \| Float}
	[Array(<span class="term">d1</span> [,<span class="term">d2</span> [,<span class="term">d3</span>]])]		[Array(<span class="term">d1</span> [,<span class="term">d2</span> [,<span class="term">d3</span>]])]
	[Initial(<span class="term">numeric-expression</span>)] [Static]		[[[Initial clause in %variable declaration\|Initial]](<span class="term">numeric-expression</span>)] [Static]
	[Common]		[Common]
	</p></li>		</p></li>
Line 163:		Line 163:
	[Dp [<span class="term">n</span> \|*}]		[Dp [<span class="term">n</span> \|*}]
	[Array(<span class="term">d1</span> [,<span class="term">d2</span> [,<span class="term">d3</span>]])] [No Field Save]		[Array(<span class="term">d1</span> [,<span class="term">d2</span> [,<span class="term">d3</span>]])] [No Field Save]
	[Initial('<span class="term">EBCDIC-string</span>' \| <span class="term">expression</span>)] [Static]		[[[Initial clause in %variable declaration\|Initial]]('<span class="term">EBCDIC-string</span>' \| <span class="term">expression</span>)] [Static]
	[Common]		[Common]
	</p></li>		</p></li>
Line 171:		Line 171:
	<li>The keyword <var>Declare</var> is optional. </li>		<li>The keyword <var>Declare</var> is optional. </li>

	<li>The <var>Initial</var> attribute assigns an initial value to a %variable at compilation time, without using any excess QTBL, STBL, or VTBL space and CPU usage. The <var>Initial</var> attribute is permitted only for numeric expressions or EBCDIC string variables, and not for arrays of any type or DBCS variables.</li>		<li>The <var>[[Initial clause in %variable declaration\|Initial]]</var> attribute assigns an initial value to a %variable at compilation time, without using any excess QTBL, STBL, or VTBL space and CPU usage. The <var>Initial</var> attribute is permitted only for numeric expressions or EBCDIC string variables, and not for arrays of any type or DBCS variables.</li>

	<li>The <var>Static</var> attribute limits assignment to a %variable to the <var>Initial</var> attribute and requires the <var>Initial</var> attribute to set the %variable's initial (and only) value.</li>		<li>The <var>Static</var> attribute limits assignment to a %variable to the <var>Initial</var> attribute and requires the <var>Initial</var> attribute to set the %variable's initial (and only) value.</li>
Line 181:		Line 181:
	</p></li>		</p></li>
	</ul>		</ul>

	====Usage====		====Usage====

Dme: /* Understanding Initial processing */

2017-10-17T12:55:57Z

Understanding Initial processing

← Older revision		Revision as of 12:55, 17 October 2017
Line 524:		Line 524:
	During a request, a %variable can be set equal to another %variable, a quoted string, a number, a field value, a noted value, a function, a count of records or field occurrences, an occurrence number, a null value, or the result of a computation.</p>		During a request, a %variable can be set equal to another %variable, a quoted string, a number, a field value, a noted value, a function, a count of records or field occurrences, an occurrence number, a null value, or the result of a computation.</p>

	===Understanding Initial processing===		===<b id="initial"></b>Understanding Initial processing===
	<p>		<p>
	Code written using an <var>Initial</var> assignment for both %variables results in the assigned value of <code>%X</code> as the <var>Initial</var> value assigned for <code>%Y</code> as both assignments are resolved at compilation. For example:</p>		Code written using an <var>Initial</var> assignment for both %variables results in the assigned value of <code>%X</code> as the <var>Initial</var> value assigned for <code>%Y</code> as both assignments are resolved at compilation. For example:</p>
Line 553:		Line 553:
	<p>		<p>
	The <code>%X</code> value is assigned at evaluation. The <var>Initial</var> value is assigned at compilation, prior to the evaluation of <code>%X=1,/code>. The result is that <code>%Y</code> is assigned the default value, zero (0), for its type of <var>Fixed</var>.</p>		The <code>%X</code> value is assigned at evaluation. The <var>Initial</var> value is assigned at compilation, prior to the evaluation of <code>%X=1,/code>. The result is that <code>%Y</code> is assigned the default value, zero (0), for its type of <var>Fixed</var>.</p>

	==Expressions==		==Expressions==
	<p>		<p>

Using variables and values in computation - Revision history

JAL: /* Declaring %variables and %variable arrays */ insert ID

JAL: /* Syntax */ add s

JAL: /* Using expressions for value retrieval */ misc formatting

Dme: /* Understanding Initial processing */

ELowell: /* Understanding Initial processing */

SSmirnova: /* Understanding Initial processing */

SSmirnova: /* Understanding Initial processing */

Dme: /* Syntax */

Dme: /* Syntax */

Dme: /* Understanding Initial processing */

JAL: /* Syntax */ add `s`