Table B (File architecture): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
This topic covers the internal architecture of a Model 204 Table B page. | |||
For a discussion of the ways a File Manager may organize these pages in a file, please refer to [[File Design (File Management)]]. | |||
At a minimum, Table B contains all of the base records in a Model 204 file. If [[Table X (File Architecture)|Table X]] is not enabled it also contains all extension records. If [[Table E (File Architecture)|Table E]] is not enabled, then any data whose contents is greater than 255 bytes must be held as a series of repeating fields. | At a minimum, Table B contains all of the base records in a Model 204 file. If [[Table X (File Architecture)|Table X]] is not enabled it also contains all extension records. If [[Table E (File Architecture)|Table E]] is not enabled, then any data whose contents is greater than 255 bytes must be held as a series of repeating fields. | ||
== The structure of a Table B page == | == The structure of a Table B page == | ||
=== Pointers === | |||
=== Space Management === | |||
Revision as of 04:32, 10 April 2013
This topic covers the internal architecture of a Model 204 Table B page.
For a discussion of the ways a File Manager may organize these pages in a file, please refer to File Design (File Management).
At a minimum, Table B contains all of the base records in a Model 204 file. If Table X is not enabled it also contains all extension records. If Table E is not enabled, then any data whose contents is greater than 255 bytes must be held as a series of repeating fields.
The structure of a Table B page
Pointers
Space Management
Table B Segments
Definition
As discussed below, bit maps are used