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

Volume and Seqnce
The fifth and sixth columns together specify a file associated with each process:
• The monitor entry reflects the name of the latest MAT file to which TMF is writing
($AUDMAT.ZTMFAT.AA000056 in this example).
• Each extractor entry reflects the name of the TMF audit trail file from which it is reading
($AUDMAT.ZTMFAT.AA000056 for the master extractor and $AUDAUX1.ZTMFAT.BB000004
for the auxiliary extractor in this example).
• The receiver entries reflect the names of the current image trail files to which each receiver is
writing ($RRCV0 write control records to $MIT and image records for updater $RUPD1 to
$IMAGE0; $RRCV1 writes image records for updaters $RUPD2 and $RUPD3 to $IMAGEA1
in this example).
• The image trail entries reflect the names of the secondary image trail files to which each
receiver is writing ($RRCV0 writes image records for updater $RUPD1 to $IMAGE0; $RRCV1
writes image records for updaters $RUPD2 and $RUPD3 to $IMAGEA1 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.
In the case of an RDF takeover operation, however, nothing is displayed for the Monitor's sequence
and relative byte number because those values have no relevance.
Rel Byte Addr
The column designated "Rel Byte Addr" indicates the relative byte address where the process in
question is positioned. For the extractor and updaters, it indicates where in the file that the process
is reading. For the receiver it represents where in the file that the last write operation completed.
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.
During non-takeover processing, you can observe the relative byte numbers increasing, and as the
processes finishes with a given file, you can see that the sequence number of the file increases and
that the relative byte number drops as the process starts reading at the beginning of that next file.
During a takeover or a stop-update-to-time operation when an updater has begun its undo pass,
however, you can observe that the relative byte numbers decrease. Further, when an updater has
finished with its current file, you can observe that the sequence number decreases as the updater
switches to the next file in reverse sequence and that the relative byte number starts at the end of
this next file and decreases as the updater reads backwards through the file.
Cpus
The eighth column specifies the CPUs in which each process pair is running.
Error
The final column is used for several purposes. For all RDF processes it is usually blank, which
indicates the process is running normally and without any error condition. The following displays
can also be reported.
****
The specific process has encountered a serious error. You should examine the event log to see
what happened. If the error condition is cleared, for example, an updater reporting a file
system error 122, then the asterisks are cleared. If the error condition is not corrected, the
asterisks continue to appear until the situation is corrected. If an updater encounters an
unexpected error 1, 10, 11, 71, or some other condition, this could indicate that your backup
RDFCOM Commands 237