RDF System Management Manual for H-Series RVUs (RDF 1.8)

Pri
The fourth column specifies the priority at which each process is running.
Volume and Seqnce
The fifth and sixth columns together specify a file associated with each process:
• 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 primary 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
$DATA05.RDF04.AA000003 for $RU03 in this example).
If RDFCOM cannot connect to a particular process, RDFCOM displays dots (...) in the RTD Time,
Sequence, and Rel Byte No fields, and an appropriate file-system error number in the Error field.
Rel Byte No
The seventh column specifies where in the specified file the particular
process is currently reading.
If RDFCOM cannot connect to a particular process, RDFCOM displays dots (...) in the RTD Time,
Sequence, and Rel Byte No fields, and an appropriate file-system error number in the Error field.
Cpus
The eighth column specifies the CPUs in which each process pair is running.
Error
The final column lets you know if an updater process has experienced a critical error. If the
column is blank, no error has occurred. If the column contains asterisks (*****), the updater process
has experienced a critical error. If the updater is performing an undo pass for takeover or
stop-update-to-time, the column contains undo. The occurrence of a critical error could mean
that the backup database is no longer synchronized with the primary database due to data loss.
If asterisks appear in the Error column for any RDF process, you should examine the messages
in the RDF log file or on the RDF log device to determine what is happening and what corrective
action to take.
Asterisks in the Error column continue to appear in every STATUS RDF display until the error
condition has been corrected.
The asterisks will also disappear for updater processes when updating is restarted after execution
of any of the following commands:
• STOP UPDATE
• STOP RDF
• STOP TMF
Although the occurrence of a critical error might mean that the primary and backup databases
are no longer synchronized with one another, that is not always the case. If, for example, the
primary CPU of the disk process goes down, all updater processes affected by that error condition
report a file-system error and then attempt to restart. If the error does not occur again when the
RDFCOM Commands 233