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

• Volume and Seqnce 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 master image trail files to which each receiver
is writing ($DATA01.RDF04.AA000044 and $DATA02.RDF04.AA000003 in this example).
The image trail 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).
• Rel Byte 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 (*****), the updater has
experienced a critical error. If the updater is doing an undo pass, the word undo appears in
the Error column. If RDFCOM cannot reach a particular process, the Error column for that
process contains the applicable file-system error number.
The occurrence of a critical error could mean that the backup database is no longer
synchronized with the primary database because of 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.
Except for updaters, asterisks in the Error column continue to appear in every STATUS
RDF display until the error condition has been corrected.
For updaters, the asterisks disappear when the error is corrected and 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
affected updater processes restart, the databases are probably still synchronized with one another.
In that case, the asterisks are cleared from subsequent STATUS RDF displays.
For more information on critical errors, you can scan the EMS collectors on the primary and
backup systems:
• The EMS collector on the primary system contains log messages for the extractor and monitor
processes.
• The EMS collector on the backup system contains log messages for the receiver, purger, and
all updater processes.
When RDF is not running, the STATUS RDF report indicates why. For example, the report might
indicate that the subsystem has never been started, or that it has crashed. The report also indicates
where processing resumes in the TMF audit-trail when RDF is restarted.
Performing Routine Operational Tasks 115