RDF/IMP and IMPX System Management Manual (RDF 1.4+)
Operating and Monitoring RDF
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
4-20
Displaying Current Configuration Parameters and
Operating Statistics
because the primary system goes down, this save point becomes the receiver’s 
restart point. The RTD for a receiver is the difference between the “last modified 
time” of the TMF MAT and the timestamp that identifies the associated restart 
point. 
The RTD value reported for each updater process is the difference between the 
“last modified time” of the TMF master audit trail (MAT) and the timestamp in the 
most recent image record seen by the particular updater.
The RTD value reflects, in the most general sense, the amount of time by which 
the backup database is lagging behind the primary database. In the example 
shown under “Output Displayed” earlier in this command description, the specified 
RTD time for the updater $RU01 is 0 minutes and 6 seconds, meaning that the 
updater is running approximately 6 seconds behind the MAT.
On a finely tuned RDF backup node, the RTD for an updater can typically vary 
between 1 and 15 seconds behind TMF processing. However, this 15-second 
delay does not mean that 15 seconds are needed to catch up; that operation may 
only take a few seconds.
•
Pri specifies the priority at which each process is running.
•
Volume and Seqnce together specify a file associated with each process, as 
follows:
The monitor entry reflects the name of the MAT file to which TMF is writing 
($AUDIT.ZTMFAT.AA000056 in this example).
Each extractor entry reflects the name of the TMF audit trail file from which it is 
reading ($AUDIT.ZTMFAT.AA000056 for the master extractor and 
$DATA17.ZTMFAT.BB000004 for the auxiliary extractor in this example).
The receiver entries reflect the names of the master image trail files to which 
each receiver is writing ($DATA01.RDF04.AA000044 and 
$DATA02.RDF04.AA000003 in this example).
The imagetrail entries reflect the names of the secondary image trail files to 
which each receiver is writing ($DATA03.RDF04.AA000022 and 
$DATA04.RDF04.AA000003 in this example).
Each updater entry reflects the name of the secondary image file from which it 
is reading ($DATA03.RDF04.AA000020 for $RU01, 
$DATA04.RDF04.AA000003 for $RU02, and so forth, in this example).
•
Rbyte Addr specifies where in the specified file the particular process is 
currently reading.
•
Cpus specifies the CPUs in which each process pair is running.
•
Error lets you know if a process has experienced an error. If the column is 
blank, no error has occurred. If the column for an updater contains asterisks 
Note. RTD times are approximations. They are not necessarily precise.










