gtpd1m0w | Database Reference |
You can define record groups for VFA candidates with the following attributes:
In a loosely coupled environment, this record is not synchronized between processors. That is, other processors accessing this record will not see the version of this record in any other processors VFA.
Data record processing occurs for the following general macros:
See TPF General Macros for more information about these macros.
The following general and system macros cause the target record to be flushed from VFA if the target record is in VFA:
See TPF General Macros for more information about the FINSC and FILSC macros. See TPF System Macros for more information about the FNSPC and FLSPC macros.
VFA program record processing occurs for the following general macros:
See TPF General Macros for more information about these macros.
Whenever VFA delay filing is selected and active (both normal delay filing and synchronized delay filing), it is possible for an application program to retrieve a record from file using the FDCTC macro while a more recent copy of the record exists in a VFA buffer. For this reason, it is essential that any application program that manages data records using the FDCTC macro not be processed while delay filing or synchronized delay filing is active.
Data records are defined as VFA candidates by record ID. Program records are defined as VFA candidates by record ID as well. Special record ID X'00FF' in the record ID attribute table (RIAT) describes the candidacy of all file resident programs.
If a program record that is resident in VFA is accessed by a FILSC, FILEC, FILUC, or FILNC macro, the record is flushed from the VFA buffers.
See TPF Operations for more information about the ZRTDM DISPLAY and ZRTDM MODIFY commands, and for information about displaying and modifying VFA candidacy in the RIAT.