RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

$SYSTEM.control-subvolume.CONFIG
• Context file
The context file is a key-sequenced file with record length 4062. The context file contains the
context information that tells the RDF subsystem where the RDF processes stopped. There is a
separate context file on the primary node and the backup node; on both nodes, the context
file is named:
$SYSTEM.control-subvolume.CONTEXT
• Exception files
Exception files are entry-sequenced files that contain transaction information for all audit data
that could not be applied during takeover processing. These files exist on the backup node
and use the naming convention:
$SYSTEM.control-subvolume.volume
The RDF subsystem creates one exception file for each primary node volume that the RDF
subsystem is protecting.
The name of the exception file is the primary volume name configured for the updater of that
volume.
You can use the RDFSNOOP utility to display the contents of exception files, as explained
previously in this appendix.
• RDF image files
RDF image files are unstructured files that contain logical audit record images and commit-abort
records. These image files exist on the backup node. The RDF image files reside on
$volume.control-subvolume, in which $volume is specified by the RDFVOLUME parameter
of the ADD RECEIVER command and ADD IMAGETRAIL command. The actual file names are
of the form AAnnnnnn.
• RDFLOCK file
The RDFLOCK file is an unstructured, semaphore lock file that exists only to protect RDFCOM
from performing multiple critical operations at the same time. A semaphore lock is the software
mechanism that prevents other processes from executing certain functions until the process
that initiated the semaphore lock has finished its processing. For example, if you issue any
one of these RDFCOM commands, RDFCOM tries to lock the RDFLOCK file:
COPYAUDIT
INITIALIZE RDF
START RDF
STOP RDF
START UPDATE
STOP UPDATE
TAKEOVER
If the RDFLOCK file is not already locked, RDFCOM locks this file and executes the critical
type of operation. If another RDFCOM user tries to execute a critical type of operation and
RDFCOM finds the RDFLOCK file already locked, RDFCOM issues the message:
Another RDFCOM is performing a CRITICAL operation.
• ZFILEINC file
This is a key-sequenced file that stores information about transactions and files involved in
transactions that aborted on the primary system, but TMF Backout could not undo the audit
because the volumes were down. A record for each transaction and file is stored in the
ZFILEINC file. If a volume is re-enabled on the primary system and TMF Backout is able to
undo the audit data it could not previously undo, then the corresponding records are removed
from the ZFILEINC file.
The ZFILEINC file resides on the backup node and is named
$SYSTEM.control-subvolume.ZFILEINC.
344 Additional Reference Information