Field value pairs (File architecture) - Revision history

Dme at 04:35, 10 May 2014

2014-05-10T04:35:21Z

← Older revision		Revision as of 04:35, 10 May 2014
Line 1:		Line 1:
	==Overview==		==Overview==
	<p>		<p>
	The basic unit of storage inside a Model 204 [[Record (File architecture)\|record]] is the field value pair (or, more literally, "field name = value pair," specifying the field's name and value). A record or a [[Field group design ~~(File management)~~\|field group]] contains a series of field groups and field value pairs.</p>		The basic unit of storage inside a Model 204 [[Record (File architecture)\|record]] is the field value pair (or, more literally, "field name = value pair," specifying the field's name and value). A record or a [[Field group design\|field group]] contains a series of field groups and field value pairs.</p>

	A record can contain multiple field value pairs for fields with the [[Field design ~~(File management)~~#OCCURS_attribute\|OCCURS attribute]].		A record can contain multiple field value pairs for fields with the [[Field design#OCCURS_attribute\|OCCURS attribute]].

	A record or a field group can contain non-<var>OCCURS</var> field value pairs, whose physical structure is described below, for each storage data type.		A record or a field group can contain non-<var>OCCURS</var> field value pairs, whose physical structure is described below, for each storage data type.
Line 21:		Line 21:
	==BINARY or CODED fields==		==BINARY or CODED fields==
	<p>		<p>
	The storage of <var>[[Field design ~~(File management)~~#BINARY attribute\|BINARY]]</var> and <var>[[Field design ~~(File management)~~#CODED attribute\|CODED]]</var> fields depends on whether the file has the Optimized Field Extraction (<var>FILEORG</var> X'80') bit set. </p>		The storage of <var>[[Field design#BINARY attribute\|BINARY]]</var> and <var>[[Field design#CODED attribute\|CODED]]</var> fields depends on whether the file has the Optimized Field Extraction (<var>FILEORG</var> X'80') bit set. </p>
	<p class="note"><b>Note:</b> <var>FILEORG</var> X'100' files automatically also turn on x'80'. </p>		<p class="note"><b>Note:</b> <var>FILEORG</var> X'100' files automatically also turn on x'80'. </p>

Line 39:		Line 39:
	</ul>		</ul>
	<p>		<p>
	By storing a length with <b>all</b> field occurrences, data in records can be read much faster. The possible trade-off on performance versus space is discussed in [[File design ~~(File management)~~#X'80' - Optimized Field Extraction files\|X'80' - Optimized Field Extraction files]]. </p>		By storing a length with <b>all</b> field occurrences, data in records can be read much faster. The possible trade-off on performance versus space is discussed in [[File design#X'80' - Optimized Field Extraction files\|X'80' - Optimized Field Extraction files]]. </p>

	==FLOAT fields==		==FLOAT fields==
	<p>		<p>
	The storage of <var>[[Field design ~~(File management)~~#FLOAT attribute\|FLOAT]]</var> fields depends on whether the file has the Optimized Field Extraction (<var>FILEORG</var> x'80') bit set. </p>		The storage of <var>[[Field design#FLOAT attribute\|FLOAT]]</var> fields depends on whether the file has the Optimized Field Extraction (<var>FILEORG</var> x'80') bit set. </p>
	<p class="note"><b>Note:</b> <var>FILEORG</var> X'100' files automatically also turn on x'80'. </p>		<p class="note"><b>Note:</b> <var>FILEORG</var> X'100' files automatically also turn on x'80'. </p>

Line 61:		Line 61:
	</ul>		</ul>
	<p>		<p>
	By storing a length with <i>all</i> field occurrences, data in records can be read much faster. The possible trade-off on performance versus space is discussed in [[File design ~~(File management)~~#X'80' - Optimized Field Extraction files\|X'80' - Optimized Field Extraction files]].</p>		By storing a length with <i>all</i> field occurrences, data in records can be read much faster. The possible trade-off on performance versus space is discussed in [[File design#X'80' - Optimized Field Extraction files\|X'80' - Optimized Field Extraction files]].</p>

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

JAL at 18:42, 4 February 2014

2014-02-04T18:42:58Z

← Older revision		Revision as of 18:42, 4 February 2014
Line 1:		Line 1:
	==Overview==		==Overview==
	<p>		<p>
	The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field name = value pair," specifying the field's name and value). A record or a [[Field group design (File management)\|field group]] contains a series of field groups and field value pairs.</p>		The basic unit of storage inside a Model 204 [[Record (File architecture)\|record]] is the field value pair (or, more literally, "field name = value pair," specifying the field's name and value). A record or a [[Field group design (File management)\|field group]] contains a series of field groups and field value pairs.</p>

	A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].		A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].

JAL at 18:39, 4 February 2014

2014-02-04T18:39:17Z

← Older revision		Revision as of 18:39, 4 February 2014
Line 1:		Line 1:
	==Overview==		==Overview==
	<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field name = value pair," specifying the field's name and value). A record or a field group contains a series of field groups and field value pairs.</p>		<p>
			The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field name = value pair," specifying the field's name and value). A record or a [[Field group design (File management)\|field group]] contains a series of field groups and field value pairs.</p>

	A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].		A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].

JAL: /* Overview */

2014-01-24T20:02:55Z

Overview

← Older revision		Revision as of 20:02, 24 January 2014
Line 1:		Line 1:
	==Overview==		==Overview==
	<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field = value pair," specifying the field's name and value). A record or a field group contains a series of field groups and field value pairs.</p>		<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field name = value pair," specifying the field's name and value). A record or a field group contains a series of field groups and field value pairs.</p>

	A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].		A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].

JAL: /* BINARY or CODED fields */

2014-01-24T01:18:53Z

BINARY or CODED fields

← Older revision		Revision as of 01:18, 24 January 2014
Line 29:		Line 29:
	</ul>		</ul>

	<p>For Optimized Field Extraction ~~Files~~, the field value pair contains three parts:</p>		<p>For Optimized Field Extraction files, the field value pair contains three parts:</p>
	<ul>		<ul>
	<li>The field code from Table A: 3 bytes for <var>FILEORG</var> X'100' files, or 2 bytes for all others.		<li>The field code from Table A: 3 bytes for <var>FILEORG</var> X'100' files, or 2 bytes for all others.

JAL: /* STRING fields */

2014-01-24T01:17:45Z

STRING fields

← Older revision		Revision as of 01:17, 24 January 2014
Line 16:		Line 16:
	</ul>		</ul>

	<p>For example, a NAME field containing 'SMITH' ~~is held in either~~ 8 or 9 bytes (depending on the FILEORG), while a NAME of 'FRANKENSTEIN' ~~is held in either~~ 15 or 16 bytes.</p>		<p>For example, a <code>NAME</code> field containing <code>'SMITH'</code> occupies 8 or 9 bytes (depending on the <var>FILEORG</var> value), while a <code>NAME</code> of <code>'FRANKENSTEIN'</code> occupies 15 or 16 bytes.</p>

	==BINARY or CODED fields==		==BINARY or CODED fields==

JAL: /* Overview */

2014-01-24T01:13:02Z

Overview

← Older revision		Revision as of 01:13, 24 January 2014
Line 1:		Line 1:
	==Overview==		==Overview==
	<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field = value pair"). A record or a field group contains a series of field groups and field value pairs.</p>		<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field = value pair," specifying the field's name and value). A record or a field group contains a series of field groups and field value pairs.</p>

	A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].		A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].

JAL: /* Overview */

2014-01-24T00:20:04Z

Overview

← Older revision		Revision as of 00:20, 24 January 2014
Line 1:		Line 1:
	==Overview==		==Overview==
	<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field = value pair"). A record ~~for~~ a field group contains a series of field groups and field value pairs.</p>		<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field = value pair"). A record or a field group contains a series of field groups and field value pairs.</p>

	A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].		A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].

JAL: /* BINARY or CODED fields */

2014-01-24T00:14:18Z

BINARY or CODED fields

← Older revision		Revision as of 00:14, 24 January 2014
Line 23:		Line 23:
	<p class="note"><b>Note:</b> <var>FILEORG</var> X'100' files automatically also turn on x'80'. </p>		<p class="note"><b>Note:</b> <var>FILEORG</var> X'100' files automatically also turn on x'80'. </p>

	<p>For files that are <i>not</i> Optimized Field Extraction ~~Files~~ (X'80), the field value pair contains two parts:</p>		<p>For files that are <i>not</i> Optimized Field Extraction files (X'80), the field value pair contains two parts:</p>
	<ul>		<ul>
	<li>The field code from Table A: 2 bytes.		<li>The field code from Table A: 2 bytes.

JAL: /* Overview */

2014-01-24T00:11:09Z

Overview

← Older revision		Revision as of 00:11, 24 January 2014
Line 1:		Line 1:
	==Overview==		==Overview==
	<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field = value pair"). A record or a field group contains a series of field groups and field value pairs.</p>		<p>The basic unit of storage inside a Model 204 record is the field value pair (or, more literally, "field = value pair"). A record for a field group contains a series of field groups and field value pairs.</p>

	A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].		A record can contain multiple field value pairs for fields with the [[Field design (File management)#OCCURS_attribute\|OCCURS attribute]].