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

• Stop Update, Timestamp Pending
• * STOP RDF In Progress *
• * TMF STOP In Progress *
• * TAKEOVER In Progress *
• WRONG PROGRAM VERSION
• NSA Stop Update Pending
• Update NSA Stopped
• *Monitor Unavailable*
The rest of the display provides current information about each RDF process configured.
For extractors, receivers, and image trails, the configured ATINDEX value is displayed in parentheses
following the object name. In the example, the extractor a$REXT0 and receiver $RRCV0 are
associated with the MAT, while the extractor $REXT1 and receiver $RRCV1 are associated with
auxiliary audit trail AUX01.
Because of insufficient space, however, ATINDEX values could not be displayed explicitly for
updaters. To determine the ATINDEX value of a particular updater, see the ATINDEX value of the
associated secondary image trail.
In the first example, an RDF network master's running environment on the primary system is depicted
with a monitor process, a master extractor ($REXT0) associated with the MAT, a second extractor
($REXT1) associated with the AUX01 audit trail, and the special RDFNET process. On the backup
system the other set of RDF processes is depicted: the master receiver ($RRCV0) associated with
the MAT and writing to the Master Image Trail ($MIT) and a Secondary Image Trail ($IMAGE0),
a second receiver ($RRCV1) associated with AUX01 and writing to a Secondary Image Trail
($IMAGEA1), updater $RUPD1 associated with the MAT reading $IMAGE0 and applying updates
to $DATA006, updater $RUPD2 associated with the AUX01 reading $IMAGEA1 and applying
updates to $DATA007, and updater $RUPD3 associated with the AUX01 reading $IMAGEA1
and applying updates to $DATA08.
The second example shows the same configuration, but this time in the midst of an RDF takeover
operation.
In both examples, different state information is displayed for each entity under the different column
headings.
RDF Process
The first column of the display identifies the type of process. Notice that each updater process is
identified by the names of both the primary volume the updater process is protecting and the
corresponding volume on the backup system. In this example, each volume being updated on the
backup system has the same name as the corresponding volume on the primary system (for example,
updates to the volume $DATA007 on the primary system are duplicated by the updater process
$RUPD2 to the volume $DATA007 on the backup system).
Name
The second column specifies the name of each process. Because the secondary image trails
$IMAGE0 and $IMAGEA1 are not processes, they do not have process names or RTD times. In
the second example, observe that the monitor no longer has the configured process name. The
reason for this is that the monitor started on the backup system for a takeover operation is started
with a Guardian-generated name.
Relative Delay Time (RTD)
The third column (labeled RTD Time) specifies the current RTD value for the extractor process,
receiver process, and all updater processes. These values can help you determine how far behind
RDFCOM Commands 239