Fast/Unload Extraction Language (FUEL) - Revision history

Dme: /* Contrasting SOUL and FUEL comparisons */

2019-03-03T18:54:23Z

Contrasting SOUL and FUEL comparisons

← Older revision		Revision as of 18:54, 3 March 2019
Line 2,109:		Line 2,109:
	</p>		</p>

	===Contrasting SOUL and FUEL comparisons===		===<b id="soulVsFuelDataComparisons"></b>Contrasting SOUL and FUEL comparisons===
	Some differences between <var class="product">SOUL</var> and <var class="product">Fast/Unload</var> comparisons are described in the following two subsections.		Some differences between <var class="product">SOUL</var> and <var class="product">Fast/Unload</var> comparisons are described in the following two subsections. In addition to the detailed information here, see:

			<ul>
			<li>[[Fast/Unload floating point arithmetic and numeric conversion]]
			<li>[[Floating_point_conversion,_rounding,_and_precision_rules\|SOUL float conversion/rounding/precision rules]]
			</ul>

	====FUEL does not imply numeric comparison for FLOAT fields====		====FUEL does not imply numeric comparison for FLOAT fields====

JAL: minor formatting

2017-01-27T01:03:23Z

minor formatting

← Older revision		Revision as of 01:03, 27 January 2017
Line 2,783:		Line 2,783:
	<blockquote class="note"><b>Notes:</b> As specified in [[#longnot\|Permitted use of long string values]] and [[#lobnot\|Permitted use of Lobs]], <i>info</i> may not be any of the following:		<blockquote class="note"><b>Notes:</b> As specified in [[#longnot\|Permitted use of long string values]] and [[#lobnot\|Permitted use of Lobs]], <i>info</i> may not be any of the following:
	<ul>		<ul>
	<li>a %variable that contains a value longer than 255 bytes</li>		<li>A %variable that contains a value longer than 255 bytes</li>
	<li>a <var>BLOB</var> or <var>CLOB</var> field</li>		<li>A <var>BLOB</var> or <var>CLOB</var> field</li>
	<li>a #function whose return value is longer than 255 bytes</li>		<li>A #function whose return value is longer than 255 bytes</li>
	</ul>		</ul>
	</blockquote>		</blockquote>

Dme: /* PUT */

2017-01-26T21:04:39Z

PUT

← Older revision		Revision as of 21:04, 26 January 2017
Line 2,781:		Line 2,781:
	<p class="code">PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) </p> </li>		<p class="code">PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) </p> </li>
	</ul>		</ul>
	<p class="note"><b>~~Note~~:</b> As specified in [[#longnot\|Permitted use of long string values]] and [[#lobnot\|Permitted use of Lobs]], <i>info</i> may not be a %variable that contains a value longer than 255 bytes~~, or be~~ a <var>BLOB</var> or <var>CLOB</var> field. </p>		<blockquote class="note"><b>Notes:</b> As specified in [[#longnot\|Permitted use of long string values]] and [[#lobnot\|Permitted use of Lobs]], <i>info</i> may not be any of the following:
			<ul>
			<li>a %variable that contains a value longer than 255 bytes</li>
			<li>a <var>BLOB</var> or <var>CLOB</var> field</li>
			<li>a #function whose return value is longer than 255 bytes</li>
			</ul>
			</blockquote>
	</td></tr>		</td></tr>

Line 2,808:		Line 2,814:
	With this more readable and efficient substitute:		With this more readable and efficient substitute:
	<p class="code">PUT %VAL AS COUNTED2 </p>		<p class="code">PUT %VAL AS COUNTED2 </p>

			Specifying <var>COUNTED</var> is the same as <var>COUNTED1</var>.

	<table>		<table>

JAL: replace LK option with P in example

2017-01-23T19:15:44Z

replace LK option with P in example

← Older revision		Revision as of 19:15, 23 January 2017
Line 3,241:		Line 3,241:
	<p>		<p>
	You can replace the above statements by the more readable and efficient: </p>		You can replace the above statements by the more readable and efficient: </p>
	<p class="code">PUT #STRIP(ITEM.NUMBER(%OCC), 'LK', '0', '_') AS COUNTED2		<p class="code">PUT #STRIP(ITEM.NUMBER(%OCC), 'P', '0', '_') AS COUNTED2
	</p>		</p>
	<p class="note"><b>Note:</b> A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.</p></li>		<p class="note"><b>Note:</b> A FUEL <var>IF</var> statement oddity is that the precedence of <var>AND</var> and <var>OR</var> are the same.</p></li>

JAL: /* PUT statement examples */ add 7.7 example

2016-10-03T16:50:26Z

PUT statement examples: add 7.7 example

@@ Line 3,225: / Line 3,225: @@
 the <code>PUT</code> and <code>OUTPUT</code> statements, and move the <code>PAI</code> to after the
 first <code>END FOR</code>.</p></li>
 </ol>

JAL: /* PUT */ add $function call for info argument

2016-09-07T18:33:30Z

PUT: add $function call for info argument

← Older revision		Revision as of 18:33, 7 September 2016
Line 2,773:		Line 2,773:
	<li>An entity. This results in the value of the entity being placed in the output buffer with the indicated format.</li>		<li>An entity. This results in the value of the entity being placed in the output buffer with the indicated format.</li>

	<li>Any valid <var class="product">Model 204</var> field name followed by the asterisk (<tt>*</tt>) symbol in parentheses. This results in each occurrence of the specified field being placed in the output buffer with the indicated format, one after the other.		<li>Any valid <var class="product">Model 204</var> field name followed by the asterisk (<tt>*</tt>) symbol in parentheses. This results in each occurrence of the specified field being placed in the output buffer with the indicated format, one after the other. </li>
	<p class="note"><b>Note:</b> As specified in [[#longnot\|Permitted use of long string values]] and [[#lobnot\|Permitted use of Lobs]], <i>info</i> may not be a %variable that contains a value longer than 255 bytes, or be a <var>BLOB</var> or <var>CLOB</var> field. </p~~></li~~>
	~~</ul>~~</td></tr>		<li>A #function call (available as of version 7.7 of Model 204). For example, instead of:
			<p class="code">%VAL = #STRIP(ITEM.VALUE(%OCC), 'L', 0)
			PUT %VAL </p>
			You can use this more readable and somewhat more efficient equivalent:
			<p class="code">PUT #STRIP(ITEM.VALUE(%OCC), 'L', 0) </p> </li>
			</ul>
			<p class="note"><b>Note:</b> As specified in [[#longnot\|Permitted use of long string values]] and [[#lobnot\|Permitted use of Lobs]], <i>info</i> may not be a %variable that contains a value longer than 255 bytes, or be a <var>BLOB</var> or <var>CLOB</var> field. </p>
			</td></tr>

	<tr><th>loc</th>		<tr><th>loc</th>

JAL: /* PUT */ wordsmithing

2016-09-07T18:22:28Z

PUT: wordsmithing

← Older revision		Revision as of 18:22, 7 September 2016
Line 2,789:		Line 2,789:
	If no <var>AS</var> clause is present, the default format is <code>STRING(*)</code>.		If no <var>AS</var> clause is present, the default format is <code>STRING(*)</code>.
	<p>		<p>
	If an <var>AS COUNTED[1\|2]</var> clause is present, and <i>format</i> is omitted, the default format is <code>STRING(*)</code>.		If an <var>AS COUNTED[1\|2]</var> clause is present, and <i>format</i> is omitted, the default format is <code>STRING(*)</code>. </p>
	For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence. <var>COUNTED1</var> specifies a one-byte length value. </p>
	<p>		<p>
	~~This ability to combine~~ a length~~-prefix with~~ the output value feature lets you ~~condense~~ FUEL code such as the following: </p>		Using <var>COUNTED1</var> or <var>COUNTED2</var> inserts a one-byte or two-byte binary integer, containing the byte length of the <var>PUT</var> value, in the output stream before the value. These keywords are available as of version 7.7 of Model 204.
			For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence.</p>
			<p>
			This feature lets you replace FUEL code such as the following: </p>
	<p class="code">%VAL = ITEM.CODE(%OCC)		<p class="code">%VAL = ITEM.CODE(%OCC)
	%LEN = #LEN( %VAL )		%LEN = #LEN( %VAL )
	PUT %LEN AS FIXED(2)		PUT %LEN AS FIXED(2)
	PUT %VAL </p>		PUT %VAL </p>
	~~The above statements can be replaced by the~~ more readable and ~~more~~ efficient:		With this more readable and efficient substitute:
	<p class="code">PUT %VAL AS COUNTED2 </p>		<p class="code">PUT %VAL AS COUNTED2 </p>
	~~<p>~~
	~~The <var>COUNTED1</var> and <var>COUNTED2</var> keywords are available as of version 7.7 of Model 204. </p>~~
	<table>		<table>
	<tr><th><var>FIXED(</var>n1<var>, [</var>n2<var>])</var></th>		<tr><th><var>FIXED(</var>n1<var>, [</var>n2<var>])</var></th>

JAL: /* PUT */ word change

2016-09-06T20:18:33Z

PUT: word change

← Older revision		Revision as of 20:18, 6 September 2016
Line 2,792:		Line 2,792:
	For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence. <var>COUNTED1</var> specifies a one-byte length value. </p>		For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence. <var>COUNTED1</var> specifies a one-byte length value. </p>
	<p>		<p>
	This length-~~before-~~value feature lets you condense FUEL code such as the following: </p>		This ability to combine a length-prefix with the output value feature lets you condense FUEL code such as the following: </p>
	<p class="code">%VAL = ITEM.CODE(%OCC)		<p class="code">%VAL = ITEM.CODE(%OCC)
	%LEN = #LEN( %VAL )		%LEN = #LEN( %VAL )

JAL: /* PUT */ add 7.7 COUNTED keywords

2016-09-06T20:07:30Z

PUT: add 7.7 COUNTED keywords

← Older revision		Revision as of 20:07, 6 September 2016
Line 2,757:		Line 2,757:
	PUT <span class="term">info</span> -		PUT <span class="term">info</span> -
	[AT <span class="term">loc</span>] -		[AT <span class="term">loc</span>] -
	[AS <span class="term">format</span> -		[AS { <span class="term">format</span> \| [<span class="term">format</span>] COUNTED[1\|2] } -
	[MISSING <span class="term">missActOrVal</span> [<span class="term">repOrNot</span>]] -		[MISSING <span class="term">missActOrVal</span> [<span class="term">repOrNot</span>]] -
	[ERROR <span class="term">errActOrVal</span> [<span class="term">repOrNot</span>]]		[ERROR <span class="term">errActOrVal</span> [<span class="term">repOrNot</span>]]
Line 2,786:		Line 2,786:

	<tr><th>format</th>		<tr><th>format</th>
	<td>One of the ~~following~~. If <var>AS <i>format</i></~~var~~> is omitted, the default format is <code>STRING(*)</code>.		<td>One of the data types listed below.
			If no <var>AS</var> clause is present, the default format is <code>STRING(*)</code>.
			<p>
			If an <var>AS COUNTED[1\|2]</var> clause is present, and <i>format</i> is omitted, the default format is <code>STRING(*)</code>.
			For example, <code>PUT FIRST.NAME AS COUNTED2</code> puts the first occurrence of field <code>FIRST.NAME</code> as a string value, preceded by a two-byte binary integer containing the length of that occurrence. <var>COUNTED1</var> specifies a one-byte length value. </p>
			<p>
			This length-before-value feature lets you condense FUEL code such as the following: </p>
			<p class="code">%VAL = ITEM.CODE(%OCC)
			%LEN = #LEN( %VAL )
			PUT %LEN AS FIXED(2)
			PUT %VAL </p>
			The above statements can be replaced by the more readable and more efficient:
			<p class="code">PUT %VAL AS COUNTED2 </p>
			<p>
			The <var>COUNTED1</var> and <var>COUNTED2</var> keywords are available as of version 7.7 of Model 204. </p>
	<table>		<table>
	<tr><th><var>FIXED(</var>n1<var>, [</var>n2<var>])</var></th>		<tr><th><var>FIXED(</var>n1<var>, [</var>n2<var>])</var></th>

Admin: /* FSTATS [AVGTOT | MINMAX] */

2016-08-08T20:09:20Z

FSTATS [AVGTOT | MINMAX]

← Older revision		Revision as of 20:09, 8 August 2016
Line 1,507:		Line 1,507:
	<var>AVGTOT</var> or <var>MINMAX</var>.		<var>AVGTOT</var> or <var>MINMAX</var>.
	See [[Fast/Unload program parameters#fstp\|FStats[=AVGTOT\|MINMAX]]].		See [[Fast/Unload program parameters#fstp\|FStats[=AVGTOT\|MINMAX]]].

	~~<var>FSTATS</var> is not valid if the Field Statistics~~
	~~option is not linked with your Fast Unload load module.~~

	This directive was new in <var class="product">Fast/Unload</var> version 4.0, as is the additional		This directive was new in <var class="product">Fast/Unload</var> version 4.0, as is the additional