Table A (File architecture) - Revision history

Mlarocca at 20:11, 28 July 2014

2014-07-28T20:11:02Z

← Older revision		Revision as of 20:11, 28 July 2014
Line 9:		Line 9:
	<p>Each entry contains the field code (the representation of the field as physically used in records), the field name, and the field attributes as assigned by the <var>[[DEFINE FIELD command\|DEFINE FIELD]]</var> command (or by a redefinition).</p>		<p>Each entry contains the field code (the representation of the field as physically used in records), the field name, and the field attributes as assigned by the <var>[[DEFINE FIELD command\|DEFINE FIELD]]</var> command (or by a redefinition).</p>

	<p>To understand all the possible content of any entry, refer to the [[ZFIELD image]] (the structure definition is provided with the Model 204 product). This image is populated by the <var>[[$~~FDEF~~\|$~~FDEF~~]]</var> or <var>[[$~~LSTFLD~~\|$~~LSTFLD~~]]</var> function.</p>		<p>To understand all the possible content of any entry, refer to the [[ZFIELD image]] (the structure definition is provided with the Model 204 product). This image is populated by the <var>[[$FDef\|$FDef]]</var> or <var>[[$LstFld\|$LstFld]]</var> function.</p>

	===Non FILEORG X'100' files===		===Non FILEORG X'100' files===

ELowell at 16:58, 12 May 2014

2014-05-12T16:58:10Z

← Older revision		Revision as of 16:58, 12 May 2014
Line 1:		Line 1:
	Table A contains three structures: a file dictionary, a set of MANY-VALUED pages, and a set of FEW-VALUED pages. The first of these is a dictionary of the names and attributes of the file's fields and field groups. Some field attributes (notably <var>[[Field design ~~(File management)~~#CODED and NON-CODED attributes\|CODED]]</var>) require sets of values to be maintained. These values are stored either in the [[Field design ~~(File management)~~#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.		Table A contains three structures: a file dictionary, a set of MANY-VALUED pages, and a set of FEW-VALUED pages. The first of these is a dictionary of the names and attributes of the file's fields and field groups. Some field attributes (notably <var>[[Field design#CODED and NON-CODED attributes\|CODED]]</var>) require sets of values to be maintained. These values are stored either in the [[Field design#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.

	Table A usually is small in relation to the rest of the file.		Table A usually is small in relation to the rest of the file.
Line 17:		Line 17:
	In a <var>FILEORG</var> X'100' file (introduced in version 7.5 of Model 204), the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) is 32000 (not the usual 4000). To support this increase as well as to support field groups, the overhead in these files for each field occurrence is 4 bytes (not the usual 3).		In a <var>FILEORG</var> X'100' file (introduced in version 7.5 of Model 204), the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) is 32000 (not the usual 4000). To support this increase as well as to support field groups, the overhead in these files for each field occurrence is 4 bytes (not the usual 3).

	If the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) in a <var>FILEORG</var> X'100' file exceeds 4000, no fields can be defined as <var>[[Field design ~~(File management)~~#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field design ~~(File management)~~#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field design ~~(File management)~~#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.		If the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) in a <var>FILEORG</var> X'100' file exceeds 4000, no fields can be defined as <var>[[Field design#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field design#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field design#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.

	==MANY-VALUED and FEW-VALUED pages==		==MANY-VALUED and FEW-VALUED pages==
	If a field has the <var>[[Field design ~~(File management)~~#CODED and NON-CODED attribute\|CODED]]</var> or <var>[[Field design ~~(File management)~~#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]]</var> attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in the <var>FEW-VALUED</var> or <var>MANY-VALUED</var> sets of pages in Table A (<var>MANY-VALUED</var> is the default).		If a field has the <var>[[Field design#CODED and NON-CODED attribute\|CODED]]</var> or <var>[[Field design#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]]</var> attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in the <var>FEW-VALUED</var> or <var>MANY-VALUED</var> sets of pages in Table A (<var>MANY-VALUED</var> is the default).

	Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.		Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.

JAL at 19:11, 4 February 2014

2014-02-04T19:11:23Z

← Older revision		Revision as of 19:11, 4 February 2014
Line 15:		Line 15:

	===Enhanced Data Handling files (FILEORG X'100' files)===		===Enhanced Data Handling files (FILEORG X'100' files)===
	In a <var>FILEORG</var> X'100' file (introduced in version 7.5 of Model 204), the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) is 32000.		In a <var>FILEORG</var> X'100' file (introduced in version 7.5 of Model 204), the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) is 32000 (not the usual 4000). To support this increase as well as to support field groups, the overhead in these files for each field occurrence is 4 bytes (not the usual 3).

	~~In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased to 4 bytes (from 3).~~		If the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) in a <var>FILEORG</var> X'100' file exceeds 4000, no fields can be defined as <var>[[Field design (File management)#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field design (File management)#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.

	~~Where~~ the maximum number of fields exceeds 4000, no fields can be defined as <var>[[Field design (File management)#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field design (File management)#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.

	==MANY-VALUED and FEW-VALUED pages==		==MANY-VALUED and FEW-VALUED pages==
Line 28:		Line 26:
	==Parameters related to the use of Table A==		==Parameters related to the use of Table A==
	<table>		<table>
	<tr><td>[[ASIZE parameter]]</td>		<tr><td><var>[[ASIZE parameter\|ASIZE]]</var></td>
	<td>The size of Table A (the sum of the values of <var>ATRPG</var>, <var>FVFPG</var>, and <var>MVFPG</var>). View-only. </td></tr>		<td>The size of Table A (the sum of the values of <var>ATRPG</var>, <var>FVFPG</var>, and <var>MVFPG</var>). View-only. </td></tr>

	<tr><td nowrap>[[ASTRPPG parameter]]</td>		<tr><td nowrap><var>[[ASTRPPG parameter\|ASTRPPG]]</var></td>
	<td>The maximum number of field and field group definitions per page, or the maximum number of field values per page in either the FEW-VALUED or MANY-VALUED section of Table A. </td></tr>		<td>The maximum number of field and field group definitions per page, and also the maximum number of field values per page in either the FEW-VALUED or MANY-VALUED section of Table A. </td></tr>

	<tr><td>[[ATRPG parameter]]</td>		<tr><td><var>[[ATRPG parameter\|ATRPG]]</var></td>
	<td>The number of pages containing field and field group definitions.</td></tr>		<td>The number of pages containing field and field group definitions.</td></tr>

	<tr><td>[[FVFPG parameter]]</td>		<tr><td><var>[[FVFPG parameter\|FVFPG]]</var></td>
	<td>The number of pages containing FEW-VALUED field values.</td></tr>		<td>The number of pages containing FEW-VALUED field values.</td></tr>

	<tr><td>[[MVFPG parameter]]</td>		<tr><td><var>[[MVFPG parameter\|MVFPG]]</var></td>
	<td>The number of pages containing MANY-VALUED field values.</td></tr>		<td>The number of pages containing MANY-VALUED field values.</td></tr>
	</table>		</table>

JAL at 21:50, 24 January 2014

2014-01-24T21:50:22Z

← Older revision		Revision as of 21:50, 24 January 2014
Line 1:		Line 1:
	Table A contains three structures: a file dictionary, a set of MANY-VALUED pages, and a set of FEW-VALUED pages. The first of these is a dictionary of the names and attributes of the file's fields and field groups. Some field attributes (notably [[Field design (File management)#CODED and NON-CODED attributes\|CODED]]) require sets of values to be maintained. These values are stored either in the [[Field design (File management)#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.		Table A contains three structures: a file dictionary, a set of MANY-VALUED pages, and a set of FEW-VALUED pages. The first of these is a dictionary of the names and attributes of the file's fields and field groups. Some field attributes (notably <var>[[Field design (File management)#CODED and NON-CODED attributes\|CODED]]</var>) require sets of values to be maintained. These values are stored either in the [[Field design (File management)#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.

	Table A usually is small in relation to the rest of the file.		Table A usually is small in relation to the rest of the file.
Line 7:		Line 7:
	The internal file dictionary is a hashed file where each page contains as many as <var>[[ASTRPPG parameter\|ASTRPPG]]</var> field or field group definitions. The exact number of pages in the internal file dictionary is defined by the <var>[[ATRPG parameter\|ATRPG]]</var> parameter. </p>		The internal file dictionary is a hashed file where each page contains as many as <var>[[ASTRPPG parameter\|ASTRPPG]]</var> field or field group definitions. The exact number of pages in the internal file dictionary is defined by the <var>[[ATRPG parameter\|ATRPG]]</var> parameter. </p>

	<p>Each entry contains the field code (the representation of the field as physically used in records), the field name, and the field attributes as assigned by the [[DEFINE FIELD command\|DEFINE FIELD]] command (or by a redefinition).</p>		<p>Each entry contains the field code (the representation of the field as physically used in records), the field name, and the field attributes as assigned by the <var>[[DEFINE FIELD command\|DEFINE FIELD]]</var> command (or by a redefinition).</p>

	<p>To understand all the possible content of any entry, refer to the [[ZFIELD image]] (the structure definition is provided with the Model 204 product). This image is populated by the [[$FDEF\|$FDEF]] or [[$LSTFLD\|$LSTFLD]] function.</p>		<p>To understand all the possible content of any entry, refer to the [[ZFIELD image]] (the structure definition is provided with the Model 204 product). This image is populated by the <var>[[$FDEF\|$FDEF]]</var> or <var>[[$LSTFLD\|$LSTFLD]]</var> function.</p>

	===Non FILEORG X'100' files===		===Non FILEORG X'100' files===
	The maximum number of fields (the product the <var>ASTRPPG</var> and <var>ATRPG</var> parameter values) in a Model 204 file is 4000, unless the file is defined with the X'100' bit of the <var>FILEORG</var> parameter, as described in the following subsection. This limit might not actually be reached because of wasted entries (where ASTRPPG is defined as too large, you cannot fit the full number on any page) or due to vagaries of the hashing algorithm.		The maximum number of fields (the product the <var>ASTRPPG</var> and <var>ATRPG</var> parameter values) in a Model 204 file is 4000, unless the file is defined with the X'100' bit of the <var>FILEORG</var> parameter, as described in the following subsection. This limit might not actually be reached because of wasted entries (where <var>ASTRPPG</var> is defined as too large, you cannot fit the full number on any page) or due to vagaries of the hashing algorithm.

	===Enhanced Data Handling files (FILEORG X'100' files)===		===Enhanced Data Handling files (FILEORG X'100' files)===
	In a <var>FILEORG</var> X'100' file (introduced in version 7.5 of Model 204), the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) is 32000.		In a <var>FILEORG</var> X'100' file (introduced in version 7.5 of Model 204), the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) is 32000.

	In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased to 4 bytes (from 3).		In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased to 4 bytes (from 3).

JAL: /* MANY-VALUED and FEW-VALUED pages */

2014-01-24T17:07:03Z

MANY-VALUED and FEW-VALUED pages

← Older revision		Revision as of 17:07, 24 January 2014
Line 22:		Line 22:

	==MANY-VALUED and FEW-VALUED pages==		==MANY-VALUED and FEW-VALUED pages==
	If a field has the [[Field design (File management)#CODED and NON-CODED attribute\|CODED]] or [[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]] attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in the FEW-VALUED or MANY-VALUED sets of pages in Table A (MANY-VALUED is the default).		If a field has the <var>[[Field design (File management)#CODED and NON-CODED attribute\|CODED]]</var> or <var>[[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]]</var> attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in the <var>FEW-VALUED</var> or <var>MANY-VALUED</var> sets of pages in Table A (<var>MANY-VALUED</var> is the default).

	Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.		Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.

JAL at 19:15, 23 January 2014

2014-01-23T19:15:10Z

← Older revision		Revision as of 19:15, 23 January 2014
Line 1:		Line 1:
	Table A contains three structures:		Table A contains three structures: a file dictionary, a set of MANY-VALUED pages, and a set of FEW-VALUED pages. The first of these is a dictionary of the names and attributes of the file's fields and field groups. Some field attributes (notably [[Field design (File management)#CODED and NON-CODED attributes\|CODED]]) require sets of values to be maintained. These values are stored either in the [[Field design (File management)#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.

	A dictionary of the ~~fieldgroup / field~~ names and ~~their~~ attributes.

	Some attributes (notably '[[Field design (File management)#CODED and NON-CODED attributes\|CODED]]') require sets of values to be maintained. These values are stored either in the [[Field design (File management)#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.

	Table A usually is small in relation to the rest of the file.		Table A usually is small in relation to the rest of the file.

	~~<div id~~="Internal ~~File Dictionary"~~>		==Internal file dictionary==
	== <~~div id="Table A (File Architecture) Internal File Dictionary"~~>~~Internal File Dictionary~~</~~div~~> ==		<p>
			The internal file dictionary is a hashed file where each page contains as many as <var>[[ASTRPPG parameter\|ASTRPPG]]</var> field or field group definitions. The exact number of pages in the internal file dictionary is defined by the <var>[[ATRPG parameter\|ATRPG]]</var> parameter. </p>

	<p>The internal file dictionary is a hashed file where each page contains up to [[ASTRPPG parameter\|ASTRPPG]] field or field group definitions. The number of pages in the internal file dictionary is defined by the [[ATRPG parameter\|ATRPG]] parameter. </p>		<p>Each entry contains the field code (the representation of the field as physically used in records), the field name, and the field attributes as assigned by the [[DEFINE FIELD command\|DEFINE FIELD]] command (or by a redefinition).</p>

	<p>Each entry contains the field code (the representation of the field as physically used in records), the field name, and the attributes as assigned by the [[DEFINE FIELD command\|DEFINE FIELD]] command (or by a redefinition).</p>

	<p>To understand all the possible content of any entry, refer to the [[ZFIELD image]] (the structure definition is provided with the Model 204 product). This image is populated by the [[$FDEF\|$FDEF]] or [[$LSTFLD\|$LSTFLD]] function.</p>		<p>To understand all the possible content of any entry, refer to the [[ZFIELD image]] (the structure definition is provided with the Model 204 product). This image is populated by the [[$FDEF\|$FDEF]] or [[$LSTFLD\|$LSTFLD]] function.</p>

	=== Non FILEORG X'100' ~~Files~~ ===		===Non FILEORG X'100' files===
			The maximum number of fields (the product the <var>ASTRPPG</var> and <var>ATRPG</var> parameter values) in a Model 204 file is 4000, unless the file is defined with the X'100' bit of the <var>FILEORG</var> parameter, as described in the following subsection. This limit might not actually be reached because of wasted entries (where ASTRPPG is defined as too large, you cannot fit the full number on any page) or due to vagaries of the hashing algorithm.

	~~The~~ maximum number of fields (~~the product of [[~~ASTRPPG ~~parameter\|ASTRPPG]]~~ * [[ATRPG ~~parameter\|ATRPG]]~~) ~~in any Model 204 file~~ is ~~4000~~.		===Enhanced Data Handling files (FILEORG X'100' files)===
			In a <var>FILEORG</var> X'100' file (introduced in version 7.5 of Model 204), the maximum number of fields (<var>ASTRPPG</var> * <var>ATRPG</var>) is 32000.

	Even a number of 4000 or less might not actually be reached because of wasted entries (where ASTRPPG is defined as too large, you cannot fit the full number on any page) or due to vagaries of the hashing algorithm.		In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased to 4 bytes (from 3).

	~~=== Enhanced Data Handling files (FILEORG X'100' files) ===~~

	~~In a FILEORG X'100' file (introduced in version 7.5 of Model 204) the maximum number of fields (<var>[[ASTRPPG parameter\|ASTRPPG]]</var> * <var>[[ATRPG parameter\|ATRPG]]</var>) is 32000.~~

	In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased ~~from 3~~ to 4 bytes.

	Where the maximum number of fields exceeds 4000, no fields can be defined as <var>[[Field design (File management)#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field design (File management)#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.		Where the maximum number of fields exceeds 4000, no fields can be defined as <var>[[Field design (File management)#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field design (File management)#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.

	== MANY-VALUED and FEW-VALUED pages ==		==MANY-VALUED and FEW-VALUED pages==
			If a field has the [[Field design (File management)#CODED and NON-CODED attribute\|CODED]] or [[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]] attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in the FEW-VALUED or MANY-VALUED sets of pages in Table A (MANY-VALUED is the default).
	If a field has the [[Field design (File management)#CODED and NON-CODED attribute\|CODED]] or [[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]] attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in ~~either~~ FEW-VALUED or MANY-VALUED pages in Table A (MANY-VALUED is the default).

	Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.		Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.

	==Parameters related to the use of Table A==		==Parameters related to the use of Table A==
			<table>
	~~::{\|~~		<tr><td>[[ASIZE parameter]]</td>
	\|[[ASIZE parameter]]		<td>The size of Table A (the sum of the values of <var>ATRPG</var>, <var>FVFPG</var>, and <var>MVFPG</var>). View-only. </td></tr>
	~~\|A view-only parameter containing the~~ size of Table A (the sum of ATRPG + FVFPG + MVFPG).
	\|-		<tr><td nowrap>[[ASTRPPG parameter]]</td>
	\|[[ASTRPPG parameter]]		<td>The maximum number of field and field group definitions per page, or the maximum number of field values per page in either the FEW-VALUED or MANY-VALUED section of Table A. </td></tr>
	\|The maximum number of field / field group definitions per page, or maximum number of field values per page in either the FEW-VALUED or MANY-VALUED section of Table A.
	\|-		<tr><td>[[ATRPG parameter]]</td>
	\|[[ATRPG parameter]]		<td>The number of pages containing field and field group definitions.</td></tr>
	\|The number of pages containing field / field group definitions.
	\|-		<tr><td>[[FVFPG parameter]]</td>
	\|[[FVFPG parameter]]		<td>The number of pages containing FEW-VALUED field values.</td></tr>
	\|The number of pages containing FEW-VALUED field values.
	\|-		<tr><td>[[MVFPG parameter]]</td>
	\|[[MVFPG parameter]]		<td>The number of pages containing MANY-VALUED field values.</td></tr>
	\|The number of pages containing MANY-VALUED field values.		</table>
	\|}



	[[Category:File architecture]]		[[Category:File architecture]]

Admin: Admin moved page Table A (File Architecture) to Table A (File architecture) without leaving a redirect

2013-12-18T22:15:00Z

Admin moved page Table A (File Architecture) to Table A (File architecture) without leaving a redirect

← Older revision	Revision as of 22:15, 18 December 2013
(No difference)

ELowell at 20:14, 16 December 2013

2013-12-16T20:14:07Z

← Older revision		Revision as of 20:14, 16 December 2013
Line 3:		Line 3:
	A dictionary of the fieldgroup / field names and their attributes.		A dictionary of the fieldgroup / field names and their attributes.

	Some attributes (notably '[[Field ~~Design~~ (File ~~Management~~)#CODED and NON-CODED attributes\|CODED]]') require sets of values to be maintained. These values are stored either in the [[Field ~~Design~~ (File ~~Management~~)#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.		Some attributes (notably '[[Field design (File management)#CODED and NON-CODED attributes\|CODED]]') require sets of values to be maintained. These values are stored either in the [[Field design (File management)#FEW-VALUED and MANY-VALUED attributes\|FEW-VALUED or MANY-VALUED]] attribute structures.

	Table A usually is small in relation to the rest of the file.		Table A usually is small in relation to the rest of the file.
Line 28:		Line 28:
	In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased from 3 to 4 bytes.		In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased from 3 to 4 bytes.

	Where the maximum number of fields exceeds 4000, no fields can be defined as <var>[[Field ~~Design~~ (File ~~Management~~)#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field ~~Design~~ (File ~~Management~~)#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field ~~Design~~ (File ~~Management~~)#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.		Where the maximum number of fields exceeds 4000, no fields can be defined as <var>[[Field design (File management)#KEY and NON-KEY attributes\|KEY]]</var>, <var>[[Field design (File management)#NUMERIC RANGE and NON-RANGE attributes\|NUMERIC RANGE]]</var>, or <var>[[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attributes\|FOR EACH VALUE]]</var>.

	== MANY-VALUED and FEW-VALUED pages ==		== MANY-VALUED and FEW-VALUED pages ==

	If a field has the [[Field ~~Design~~ (File ~~Management~~)#CODED and NON-CODED attribute\|CODED]] or [[Field ~~Design~~ (File ~~Management~~)#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]] attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in either FEW-VALUED or MANY-VALUED pages in Table A (MANY-VALUED is the default).		If a field has the [[Field design (File management)#CODED and NON-CODED attribute\|CODED]] or [[Field design (File management)#FOR EACH VALUE (FRV) and NON-FRV attibute\|FRV]] attribute, a complete list of the values that the field has ever had (since it was last created or reorganized) is held in either FEW-VALUED or MANY-VALUED pages in Table A (MANY-VALUED is the default).

	Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.		Both of these sets of pages should be kept very small. If large numbers of values exist, the File Manager should consider making the field Ordered.

Dme: /* Enhanced Data Handling files (FILEORG X'100' files) */

2013-08-14T13:33:00Z

Enhanced Data Handling files (FILEORG X'100' files)

← Older revision		Revision as of 13:33, 14 August 2013
Line 24:		Line 24:
	=== Enhanced Data Handling files (FILEORG X'100' files) ===		=== Enhanced Data Handling files (FILEORG X'100' files) ===

	~~With the introduction of~~ X'100' ~~files~~ (in version 7.5 of Model 204) the maximum number of fields (<var>[[ASTRPPG parameter\|ASTRPPG]]</var> * <var>[[ATRPG parameter\|ATRPG]]</var>) ~~has been increased to~~ 32000.		In a FILEORG X'100' file (introduced in version 7.5 of Model 204) the maximum number of fields (<var>[[ASTRPPG parameter\|ASTRPPG]]</var> * <var>[[ATRPG parameter\|ATRPG]]</var>) is 32000.

	In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased from 3 to 4 bytes.		In order to support this increase as well as to support field groups, the overhead for each field occurrence has increased from 3 to 4 bytes.

ELowell: /* Parameters related to the use of Table A */

2013-07-17T20:20:51Z

Parameters related to the use of Table A

← Older revision		Revision as of 20:20, 17 July 2013
Line 43:		Line 43:
	\|-		\|-
	\|[[ASTRPPG parameter]]		\|[[ASTRPPG parameter]]
	\|The maximum number of field / ~~RFG~~ definitions per page, or maximum number of field values per page in either the FEW-VALUED or MANY-VALUED section of Table A.		\|The maximum number of field / field group definitions per page, or maximum number of field values per page in either the FEW-VALUED or MANY-VALUED section of Table A.
	\|-		\|-
	\|[[ATRPG parameter]]		\|[[ATRPG parameter]]
	\|The number of pages containing field / ~~RFG~~ definitions.		\|The number of pages containing field / field group definitions.
	\|-		\|-
	\|[[FVFPG parameter]]		\|[[FVFPG parameter]]