gtpd1m03 | Database Reference |
- File Address Formats
- FARF Address Generation
- FARF3 Fixed Address Decode Procedure
- FARF4, FARF5, and FARF6 Fixed Address Decode Procedure
- Extended MCHR File Address Formats
- Capture and Restore Load Balancing Using DASDCU and DASDCH
- Capture and Restore Load Balancing Using the TAPECU and TAPECH Parameters
- General Layout of a TPFCS Database
- TPFCS Abstract Class Hierarchy
- Data on an External Device
- Class Inheritance Tree Example
- Object Class Inheritance
- Multiple Inheritance Example
- Object Aggregation
- Defining TPF Collection Support Source Code Instance Attributes
- ClassC Inheritance Scheme
- A ClassC Object
- Another Way to Depict the Same ClassC Object
- Separate Objects in the Same Record
- A ClassX Object
- A Limousine Object
- Data Area Attribute of a ClassX Object in the Vehicle Database
- DSECT Showing the 4-Byte Format Record Header
- DSECT Showing the 8-Byte Format Record Header
- TPF Collection Support Primary Record Header Using 4-Byte File Addresses
- TPFCS Shadow Record Header
- Primary Record Header with No Shadow
- Contents of the TPFCS Record Trailer
- DATXPAGE Envelope Format
- Example of a Collection Control Record
- Conceptual View of a Control Record for a Keyed Log Collection
- USERdata Object
- Example of the Data Area of a MemFLAT Object
- Example of the Data Area of a MemHash Object
- Data Area of MemKey in Memory
- Example of a MemList Data Area in Memory
- Abstract View of How Data Is Stored for Extended-Resident Collections
- How Directory Records Are Used to Locate RRNs 18-26
- How TPF Collection Support Adds Records to a StructureDasd Chain
- How Records Are Linked on Both Allocated and Released Chains
- DASDINDEXPool Object and Its Associated Records
- Example of a Key (Index) Record Containing Five Entries
- Example of a Data Record Containing Four Active Entries
- Abstract Model of a DASDHASD Structure Collection
- Example of a VDATPAGE Data Record Containing Four Active Entries
- How Elements of a DASDLIST Structure Collection Are Written in the Database
- How Elements of a DASDLIST Structure Collection Are Ordered
- How the Order of a DASDLIST Collection Is Maintained
- Example of an LDATPAGE Data Record Containing Four Active Entries
- How an Object Containing a Data Area Appears in Memory
- How an Object Containing a Data Area with Locators Appears after Space Saving
- How OBJECTA Is Spread Across Three Records (with Shadowing)
- Control Record for a Nonshadowed Array with Overflow
- How TPFCS Handles the Control Record Contents
- Collection Attributes Display Format
- Actual Collection Attributes Display
- Multiple Systems Sharing Data through a CF
- Allocating a CF Structure
- Connecting to an Allocated CF Structure
- A Serialized List Structure
- A List Containing Entries with Various Numbers of Data Elements
- Elements of a Cache System for Processor Shared Cache
- Elements of a Cache System for Processor Unique Cache
- Registered Interest in Shared Pieces of Data
- Invalidating a Local Cache Copy of a Shared Piece of Data
- Format of the CF Lock
- Format of the CF Lock When a CF Is in Available State
- Format of the CF Lock When a CF Is in a Nonavailable State
- Format of the CF Lock When the Lock Holder Field Is Set to Zero
- Format of the CF Lock When the Lock Holder Field Is Set to the Processor Ordinal Number for Processor C