Fast/Unload with Model 204 fieldgroups - Revision history

JAL: /* Support for FILEORG X'100' files */ link repair

2016-02-19T16:23:00Z

Support for FILEORG X'100' files: link repair

← Older revision		Revision as of 16:23, 19 February 2016
Line 7:		Line 7:
	<table class="thJustBold">		<table class="thJustBold">
	<tr><th>UAI</th>		<tr><th>UAI</th>
	<td><var>UAI</var> FUEL programs may be used to unload <var>FILEORG</var> X'100' files, for reloading with <var class="product">[[~~Media:FrelrNew.pdf\|~~Fast/Reload]]</var>.</td></tr>		<td><var>UAI</var> FUEL programs may be used to unload <var>FILEORG</var> X'100' files, for reloading with <var class="product">[[Fast/Reload]]</var>.</td></tr>

	<tr><th>PAI</th>		<tr><th>PAI</th>
Line 233:		Line 233:

	<div id="grp"></div>		<div id="grp"></div>

	==FOR FIELDGROUP blocks==		==FOR FIELDGROUP blocks==
	<!--Caution: <div> above-->		<!--Caution: <div> above-->

JAL: misc cleanup

2015-04-14T23:30:46Z

misc cleanup

Show changes

JAL: misc cleanup

2015-04-14T15:43:15Z

misc cleanup

← Older revision		Revision as of 15:43, 14 April 2015
Line 54:		Line 54:
	For example, <var class="product">Fast/Unload</var> does not enforce the <var>DATETIME</var> format restriction in the <var>ADD</var> or <var>CHANGE</var> statement. </p>		For example, <var class="product">Fast/Unload</var> does not enforce the <var>DATETIME</var> format restriction in the <var>ADD</var> or <var>CHANGE</var> statement. </p>

	~~<div id="str100"></div>~~
	===Record structure and basic fieldgroup concepts===		===Record structure and basic fieldgroup concepts===
	~~<!--Caution: <div> above-->~~

	A record in a <var class="product">Model 204</var> file with the <var>FILEORG</var> X'100' bit		A record in a <var class="product">Model 204</var> file with the <var>FILEORG</var> X'100' bit
	consists of a sequence of field and/or fieldgroup occurrences. These occurrences are called		consists of a sequence of field and/or fieldgroup occurrences. These occurrences are called
Line 94:		Line 91:
	</p>		</p>

	An example <var>PAI</var> of a record in a file with these definitions is:		An example <var>[[Fast/Unload Extraction Language (FUEL)#PRINT ALL INFORMATION or PAI\|PAI]]</var> statement output of a record in a file with these definitions is:
	<p class="code"><nowiki>OUTFLD = OUT01		<p class="code"><nowiki>OUTFLD = OUT01
	OUTFLD = OUT02		OUTFLD = OUT02
Line 110:		Line 107:
	</nowiki></p>		</nowiki></p>

	~~Notes~~:		Example notes:
	<ul>		<ul>
	<li>The order of fieldgroup IDs, as in this example (20 and 5),		<li>The order of fieldgroup IDs, as in this example (20 and 5),
	need not correspond to the order of the fieldgroups in the record.		need not correspond to the order of the fieldgroups in the record.
	The ID of a fieldgroup is assigned when it is added to the record, and is		The ID of a fieldgroup is assigned when it is added to the record, and is
	equal to one more than the highest fieldgroup ID ~~which had been~~ used in the		equal to one more than the highest fieldgroup ID that was used in the
	record (even if the fieldgroup with that ID ~~has been~~ deleted). </li>		record (even if the fieldgroup with that ID was deleted). </li>

	<li>The default repeatability for (non-<var>FG *</var>) fieldgroup member <b>fields</b>		<li>The default repeatability field attribute for (non-<var>[[Field group design#FIELDGROUP (FG) attribute\|FG *]]</var>) fieldgroup member <b>fields</b> is <var>EXACTLY-ONE</var>.
	is <var>EXACTLY-ONE</var>.		In the second occurrence of <code>GRP</code> above, whether or not <code>EXOMEM2</code> has been stored cannot be determined; it is treated in all respects as if it had been
	In the second occurrence of <code>GRP</code> above, whether or not <code>EXOMEM2</code> has been stored		stored with a null string value. </li>
	cannot be determined; it is treated in all respects as if it had been
	stored with a ~~value of the~~ null string. </li>
	</ul>		</ul>

Line 129:		Line 124:
	This is obtained in either of two ways:		This is obtained in either of two ways:
	<ul>		<ul>
	<li>By referring to the member of the fieldgroup within a <var>FOR FIELDGROUP</var>		<li>By referring to the member of the fieldgroup within a <var>[[#FOR FIELDGROUP block\|FOR FIELDGROUP</var> block that identifies an occurrence of the fieldgroup — this fieldgroup
	block that identifies an occurrence of the fieldgroup — this fieldgroup
	occurrence is the <b>fieldgroup context</b> for the fieldgroup member. </li>		occurrence is the <b>fieldgroup context</b> for the fieldgroup member. </li>

	<li>For an <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var> non-<var>FG *</var> field member of a non-nested		<li>For an <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var> non-<var>FG *</var> field member of a non-nested fieldgroup, a reference outside the context of the fieldgroup implicitly
	fieldgroup, a reference outside the context of the fieldgroup implicitly
	identifies the fieldgroup occurrence; see [[#legacy\|References to fieldgroup members not in fieldgroup context]].		identifies the fieldgroup occurrence; see [[#legacy\|References to fieldgroup members not in fieldgroup context]].
	</ul>		</ul>
Line 140:		Line 133:
	The following FUEL program explains both cases of fieldgroup member reference,		The following FUEL program explains both cases of fieldgroup member reference,
	assuming that the record shown in the above <var>PAI</var> output is the current record:		assuming that the record shown in the above <var>PAI</var> output is the current record:
	<p class="code"~~><nowiki~~>FOR EACH RECORD		<p class="code">FOR EACH RECORD
	FOR FIELDGROUP GRP(1)		FOR FIELDGROUP GRP(1)
	PUT EXOMEM /* In context of GRP(1): MEM01		PUT EXOMEM /* In context of GRP(1): MEM01
Line 152:		Line 145:
	* REPMEM illegal here; it requires a fieldgroup context		* REPMEM illegal here; it requires a fieldgroup context
	END FOR		END FOR
	</~~nowiki~~></p>		</p>
	In addition to fieldgroup context:		<p class="note"><b>Note:</b> In addition to fieldgroup context, <b>record context</b> is always available for fields and fieldgroups defined without the <var>FG</var> attribute.
	~~<ul>~~		</p>
	~~<li>~~<b>~~Record~~ context</b> is always available for fields and fieldgroups
	defined without the <var>FG</var> attribute.
	</ul>

	===Nested fieldgroups and FG *===		===Nested fieldgroups and FG *===
	Two advanced aspects of the fieldgroup feature, not explored in [[#~~str100~~\|Record structure ~~in FILEORG X'100' files, context~~ and ~~other~~ fieldgroup concepts]], are:		Two advanced aspects of the fieldgroup feature, not explored in [[#Record structure and basic fieldgroup concepts\|Record structure and basic fieldgroup concepts]], are:
	<ul>		<ul>
	<li>The <var>DEFINE FIELDGROUP</var> command allows the <var>FG</var> attribute, which		<li>The <var>DEFINE FIELDGROUP</var> command allows the <var>FG</var> attribute, which

JAL: misc cleanup

2015-04-13T22:10:56Z

misc cleanup

Show changes

JAL: /* PAI */

2015-04-10T22:00:47Z

PAI

← Older revision		Revision as of 22:00, 10 April 2015
Line 840:		Line 840:
	===PAI===		===PAI===
	The <var>PAI</var> statement in FUEL supports <var>FILEORG</var> X'100' files, providing		The <var>PAI</var> statement in FUEL supports <var>FILEORG</var> X'100' files, providing
	the same information that <code>PAI CTOFIELDS</code> in <var class="product">SOUL</var> provides.		the same information that <code>[[PAI statement#PAI\|PAI CTOFIELDS]]</code> in <var class="product">SOUL</var> provides.
	There are no operands of the FUEL <var>PAI</var> statement, to control display		There are no operands of the FUEL <var>PAI</var> statement to control display
	of automatic fields or <var>LOB</var> fields, as there are in the <var class="product">SOUL</var> <var>PAI</var> statement.		of automatic fields or <var>LOB</var> fields as there are in the <var class="product">SOUL</var> <var>PAI</var> statement.

	Fieldgroups are displayed with a <code><i>fieldgroup name</i> = <i>ID</i></code> line at the start		Fieldgroups are displayed with a <code><i>fieldgroup name</i> = <i>ID</i></code> line at the start and end of the fieldgroup. For example, repeating the example <var>PAI</var> output
	and end of the fieldgroup. For example, repeating the example <var>PAI</var> output
	shown in [[#str100\|Record structure in FILEORG X'100' files, context and other fieldgroup concepts]]:		shown in [[#str100\|Record structure in FILEORG X'100' files, context and other fieldgroup concepts]]:
	<p class="code"><nowiki>OUTFLD = OUT01		<p class="code"><nowiki>OUTFLD = OUT01

JAL: add 4.6 items

2015-04-10T19:45:21Z

add 4.6 items

← Older revision		Revision as of 19:45, 10 April 2015
Line 882:		Line 882:

	<var>#FIELDGROUPOCCURRENCE</var> is not usable in a <var>SORT FIELDS</var> shorthand. These shorthands are discussed in [[Fast/Unload with an external sort package#Using SORT FIELDS\|Using SORT FIELDS]].		<var>#FIELDGROUPOCCURRENCE</var> is not usable in a <var>SORT FIELDS</var> shorthand. These shorthands are discussed in [[Fast/Unload with an external sort package#Using SORT FIELDS\|Using SORT FIELDS]].

			==Other fieldgroup references==

			===Reference to the number of occurrences of a fieldgroup===
			Just as you can refer to the [[Fast/Unload Extraction Language (FUEL)#FOR v FROM begin TO end\|number of occurrences of a field]] as an entity in a FUEL program, you can also refer to the number of occurrences of a fieldgroup. For a fieldgroup, specify the <var>FIELDGROUP</var> keyword, followed by the fieldgroup name, followed by the number token (<tt>#</tt>) in parentheses:
			<p class="code">FOR I FROM 1 TO FIELDGROUP PAYMENT.INFO(#)
			</p>

			===#IF FIELDGROUP fieldgroup DEFINED===
			The <var>[[Fast/Unload_Extraction_Language_(FUEL)##IF\|#IF]]</var> preprocessor statement allows testing for the presence of a fieldgroup in the file being unloaded (or any of the files in a group being unloaded).

			For example:
			<p class="code"><nowiki>#IF FIELDGROUP PAYMENT.INFO DEFINED
			</nowiki></p>

	==FSTATS for FILEORG X'100' files==		==FSTATS for FILEORG X'100' files==

JAL: add link

2015-04-10T19:14:58Z

add link

← Older revision		Revision as of 19:14, 10 April 2015
Line 1:		Line 1:
	<var class="product">Model 204</var> processing for multiply occurring fields was enhanced in version 7.5 to support physical ~~field groups~~ which let you view and process groups of fields as a logical entity. <var class="product">Fast/Unload</var> supports ~~[[Field group (File architecture)\|~~physical fieldgroups]] as of its version 4.6.		<var class="product">Model 204</var> processing for multiply occurring fields was enhanced in version 7.5 to support [[Field group (File architecture)\|physical fieldgroups]] which let you view and process groups of fields as a logical entity. <var class="product">Fast/Unload</var> supports physical fieldgroups as of its version 4.6.

	Since you can define a physical field group only for files with the <var>[[FILEORG parameter\|FILEORG]]</var> X'100' setting, the documentation for Fast/Unload support of <var>FILEORG</var> X'100' files is presented as part of the <var class="product">Fast/Unload</var> support for fieldgroups.		Since you can define a physical field group only for files with the <var>[[FILEORG parameter\|FILEORG]]</var> X'100' setting, the documentation for Fast/Unload support of <var>FILEORG</var> X'100' files is presented as part of the <var class="product">Fast/Unload</var> support for fieldgroups.

JAL: add link

2015-04-10T19:13:06Z

add link

← Older revision		Revision as of 19:13, 10 April 2015
Line 1:		Line 1:
	<var class="product">Model 204</var> processing for multiply occurring fields was enhanced in version 7.5 to support physical field groups which let you view and process groups of fields as a logical entity. <var class="product">Fast/Unload</var> supports physical fieldgroups as of its version 4.6.		<var class="product">Model 204</var> processing for multiply occurring fields was enhanced in version 7.5 to support physical field groups which let you view and process groups of fields as a logical entity. <var class="product">Fast/Unload</var> supports [[Field group (File architecture)\|physical fieldgroups]] as of its version 4.6.

	Since you can define a physical field group only for files with the <var>[[FILEORG parameter\|FILEORG]]</var> X'100' setting, the documentation for Fast/Unload support of <var>FILEORG</var> X'100' files is presented as part of the <var class="product">Fast/Unload</var> support for fieldgroups.		Since you can define a physical field group only for files with the <var>[[FILEORG parameter\|FILEORG]]</var> X'100' setting, the documentation for Fast/Unload support of <var>FILEORG</var> X'100' files is presented as part of the <var class="product">Fast/Unload</var> support for fieldgroups.

JAL: link repair

2015-04-06T17:45:35Z

link repair

← Older revision		Revision as of 17:45, 6 April 2015
Line 258:		Line 258:
	In addition, within any of the above blocks there is a version 4.6		In addition, within any of the above blocks there is a version 4.6
	statement for terminating execution of the block		statement for terminating execution of the block
	(<var>[[LEAVE FIELDGROUP]]</var>), a version 4.6 special		(<var>[[#LEAVE FIELDGROUP\|LEAVE FIELDGROUP]]</var>), a version 4.6 special
	variable for obtaining the fieldgroup ID of a fieldgroup occurrence		variable for obtaining the fieldgroup ID of a fieldgroup occurrence
	(<var>[[##grpid\|#FIELDGROUPID]]</var>), and a version 4.6 special		(<var>[[##grpid\|#FIELDGROUPID]]</var>), and a version 4.6 special

JAL: /* Handling of missing AT-MOST-ONE fields */ remove NOUNLOAD and NOUNLOADC

2015-04-03T15:08:49Z

Handling of missing AT-MOST-ONE fields: remove NOUNLOAD and NOUNLOADC

← Older revision		Revision as of 15:08, 3 April 2015
Line 577:		Line 577:
	<li>The <var>IF/ELSEIF</var> statement's <var>MISSING</var> test for the missing first occurrence is true. </li>		<li>The <var>IF/ELSEIF</var> statement's <var>MISSING</var> test for the missing first occurrence is true. </li>

	<li>The missing first occurrence may <b>not</b> be used with a <var>DELETE</var>, <var>UNLOAD~~</var>, or <var>NOUNLOAD~~</var> statement (<var>DELETEC</var>, <var>UNLOADC</var>~~, and <var>NOUNLOADC</var>, respectively,~~ <b>can</b> be used), nor may it be used on the left side of a <var>CHANGE</var> statement.		<li>The missing first occurrence may <b>not</b> be used with a <var>DELETE</var> or <var>UNLOAD</var> statement (<var>DELETEC</var> and <var>UNLOADC</var> <b>can</b> be used), nor may it be used on the left side of a <var>CHANGE</var> statement.
	</ul>		</ul>