gtpd2m25 | Data Communications Services Reference |
Many MR system records have been introduced in the discussion of the
message routing facility architecture. Figure 14 represents an overview of all the system records used by the
message routing facility and their relationship to the various
components. The records shown are exclusively used by MR. Other
records that are common to other TPF function and have been mentioned in prior
sections (for example, LSTB Line Status Table) are neither shown nor discussed
any further in this book. Following is a summary of all the Message
Routing system records containing information relative to data macro name,
FACE ID, storage and file considerations, and record initialization.
Additional detailed information is found in the referenced literature.
Note that message router tables reside in the Basic Subsystem (BSS)
only.
- Note:
- Records that are listed here as large are 1055 bytes unless
otherwise noted.
- Data Macro Name:
- C01DR
- FACE ID:
- #C01RI
- Storage Factors:
- Both prime and overflow CODR records are large records.
- File Requirements:
- Prime records are allocated to fixed file storage. Overflow records
are created and purged as necessary. They reside in random file pool
storage.
- Record Initialization:
- These records are initialized by the Unsolicited Record Initializer
(DCSL-UMP) during the initial system cycle-up.
- Data Macro Name:
- C03NL
- FACE ID:
- Not Applicable
- Storage Factors:
- The CONL records are large records.
- File Requirements:
- These records are created and purged as necessary. They reside in
random file pool storage.
- Record Initialization:
- These records are initialized by the Unsolicited Message Processor
(UMP).
- Data Macro Name:
- TA0PP
- FACE ID:
- #TAPID
- Storage Factors:
- Both prime and overflow TAPP records are large records.
- File Requirements:
- Prime and overflow records are allocated to fixed file storage.
- Record Initialization:
- These records are initialized by the System Test Compiler (STC) or by the
ZAUTH command.
- Data Macro Name:
- RC0AT
- FACE ID:
- #RCATU
- Storage Factors:
- The RCAT record(s), when in main storage, reside in Global Area 3 of the
Primary Subsystem User of the Basic Subsystem (BSS).
- File Requirements:
- RCAT records are allocated to fixed file storage. They are forward
chained, the last record having a forward chain value of zero.
- Record Initialization:
- The records are initialized by Router Table Loader (03-RTLP) from the RCAT
Initialization Table (RCIT) during the initial system IPL.
- Data Macro Name:
- CI0CO
- FACE ID:
- #RCBRA
- Storage Factors:
- RCBs are large records
- File Requirements:
- The prime RCB's are allocated to fixed file storage. Overflow,
if any, reside in random file pool storage.
- Record Initialization:
- Each RCB is initialized, when its terminal/Link becomes active in the
system, by the RCB Initialization Program (03-RCBI) from information contained
in the AAA/RCB Initialization Table (UAT).
- Data Macro Name:
- RC1IT
- FACE ID:
- Not Applicable
- Storage Factors:
- The RCIT records are large records.
- File Requirements:
- The RCIT records on file are large program records and reside in the
program area.
- Record Initialization:
- These records are initially generated by the System Initialization Package
(SIP). Any changes to the application names will be reflected by
changing and reassembling the RCIT records. This will force rebuilding
of the Message Router Tables during the next IPL.
- Data Macro Name:
- UA1UA
- FACE ID:
- #UATRI
- Storage Factors:
- The UAT records are large records.
- File Requirements:
- The UAT records are allocated to fixed file storage.
- Record Initialization:
- These records are initialized by the System Test Compiler (STC).
- Data Macro Name:
- WG0TA
- FACE ID:
- #WGTRU
- Storage Factors:
- The WGTA table resides in main storage. The required area is carved
out by the Control Program Initializer.
- File Requirements:
- WGTA tables are allocated to fixed file storage. They are 4K
records.
- Locking Requirements:
- WGTA table entries must be locked for update as the entries are shared by
I-streams.
- Record Initialization:
- The WGTA tables are initialized by the WGTA Table Generation Routines
(03-WGTA) during system cycle up.
- Data Macro Name:
- SN0CT
- FACE ID:
- Not Applicable
- Storage Factors:
- The SNCT resides in main storage. It is created from the file
records during system restart.
- File Requirements:
- Up to eleven large program records on file are used to used to store the
SNCT.
- Record Initialization:
- The SNCT is generated by the System Initialization Package (SIP).
- Data Macro Name:
- RV1VT
- FACE ID:
- #RV1RU
- Storage Factors:
- The RVT resides in main storage.
- File Requirements:
- The Keypoint copy of the RVT resides in 4K fixed file records.
- Locking Requirements:
- RVT table entries must be locked for update as the entries are shared by
I-streams.
- Record Initialization:
- These records are initialized by the SNA restart programs from the
Resource Resolution Table, which is created by the Offline SNA Table
Generation Program.
Figure 14. Message Routing System Records. Relationship to MR Components.