RDF/IMP and IMPX System Management Manual (RDF 1.4+)

Additional Reference Information
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
B-9
RDF System Files
•
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 the following
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 following 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.
•
RDFTKOVR file
This file records whether an RDF Takeover operation has completed successfully.
This file is empty under normal circumstances (eof = 0). If, however, you have
executed an RDF Takeover operation and it completes successfully, then they key
word "DONE" is written in the file by RDF. This file can be used for executing fast
business takeover operations. See in Tips for Executing Fast Business Takeover
Operations in section 1 for more details.
The RDFTKOVR file resides on the backup node and is named
$SYSTEM.control-subvolume.RDFTKOVR.