gtps4m2dSystem Generation

Record ID Attribute Table (RIAT)

The record ID attribute table (RIAT) contains information on every file type (both fixed and pool) in the database. This information includes the following pool file attributes:

The RIAT also includes the following information for both fixed and pool file records:

There is 1 entry in the RIAT for each record ID defined in the system.

Creating the RIAT

RIATA macro calls, coded in the RIAT segment, create entries in the record ID attribute table (RIAT). This table contains information about all (fixed and pool file) IDs in the system. There must be 1 RIATA call for every ID in the database. It is used by VFA, logging, restoring, exception recording, GFS, the locking attribute, and record cache subsystem (RCS) support for processing options.

The RIAT is created by coding a deck of RIATA calls and assembling it. The RIAT deck consists of:

You can code the RIATA calls in any order. When the RIAT is assembled, a RIAT is created. Error messages are generated for duplicate IDs or invalid parameter values.

A sample deck of RIATA calls is provided as the SPRIAT macro, which is a copy member in ACP.MACRO.RELxx. Modify these RIATA calls to fit each individual system (for example, only pool types coded in your RAMFIL statements should appear in your RIATA calls). Edit this deck and incorporate the applicable RIATA calls into the RIAT segment by either (1) including a COPY SPRIAT statement in the RIAT segment or (2) including the edited SPRIAT directly into the RIAT segment.

The IDs can be in character, hexadecimal, Boolean, or decimal format; the SPRIAT deck contains IDs in character and hexadecimal format. (A duplicate ID error message is generated for RIATA calls that code the same numeric ID in two different formats.)

To locate the RIAT, SIP stage I retrieves the data set name (coded in the INDSN macro) and the member name in which the RIAT resides from SPPGML. The RIAT is assembled as part of SIP stage II and is loaded into the system as part of the core image restart area. The RIATDSN= parameter of the INDSN SIP macro is used to indicate what RIAT segment to assemble and load. The default is the RIAT segment located in ACP.SRCE.OL.RELxx.

When the RIAT is assembled, a check is made to ensure that the pool types coded in RIATA calls are available (pool type availability is determined by input to the RAMFIL macro). If a RIATA call is coded with an unavailable pool type, a warning message appears in the assembly listing.

Positive feedback support allows you to understand what programs have been loaded onto your TPF system. It also provides information about changes that were made to the program allocation table (PAT) or RIAT; for instance, ordinal record 1 through the number of records that were defined will have entries added to them by positive feedback support for every program that is activated, deactivated, accepted, or excluded (that is, every time an operator enters the ZAPAT, ZAPGM, or ZRTDM MODIFY command). You must define #IPSFB 4-KB fixed file records to use positive feedback support.

Accessing the RIAT Online

Although the attributes associated with a particular record ID are initialized when the RIAT is built, some of the attributes can be modified online.

The attributes that can be modified (using the ZRTDM command) include:

Logging

Exception recording

Record restore

User exit

VFA candidacy

Locking attribute

Record caching candidacy.

Note:
Attributes cannot be modified for IDs that are not defined in the RIAT, and table entries for IDs cannot be added after the RIAT is created. Pool attributes cannot be changed with the ZRTDM command. In order to add pool attributes or new IDs, a new RIAT table must be created and loaded to the system.

Information in the RIAT is accessed by means of the RITID macro and the ZRTDM command.