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

when the STATUS RDF command was issued. The second line specifies the fully-qualified name of
the control subvolume.
RDF States
The third line specifies the current state of the subsystem; any of the following entries are possible:
Table 9 RDF States
DescriptionStatus
RDF running with Update OnNormal
RDF running with Update OffNormal - Update Stopped
RDF was running with Update Off, Update was just turned On, but one
or more updaters have not yet started.
Start Update Pending
RDF was running with Update On, Update was just turned Off, but one
or more updaters have not yet stopped.
Stop Update Pending
RDF was running with Update On, you issued a STOP UPDATE
command with the timestamp option, but one or more updaters have
not reached the end of Redo and/or Undo operations.
Stop Update, Timestamp Pending
RDF was running with Update On, you have issued a STOP RDF
command, but one or more RDF processes have not yet stopped.
* STOP RDF In Progress *
RDF was running with either Update On or Off, you have issued a
TMFCOM STOP TMF command on the primary system, the master
* TMF STOP In Progress *
extractor has detected the STOP TMF audit record, but one or more
RDF processes have not yet stopped in response.
You have tried to START RDF, but the RDF software on the backup
system is not compatible with the RDF software on the primary system.
WRONG PROGRAM VERSION
RDF was running with Update On, a Shared Access NonStop SQL/MP
or SQL/MX operation was detected, but some updaters have not yet
shutdown.
NSA Stop Update Pending
RDF had been running with Update On, a Shared Access NonStop
SQL/MP or SQL/MX operation was detected, and all updaters have
Update NSA Stopped
completed their shutdown. Note, you must consult the RDF LOG for
either the RDF event 905 or 908 to determine if it is safe for you to
perform the DDL operation on the backup system.
The monitor is either stopped or is running but unable to respond. The
latter situation can happen for several reasons, such as the STATUS
* Monitor Unavailable *
RDF command having been issued from the backup system when the
Expand connection to the primary system is done. Another example
of this can happen as a result of a STOP RDF, REVERSE operation that
includes a REVERSE trigger that starts RDF with the WAIT option. If this
state persists and if Expand is up, then you should check the status of
the Monitor via a TACL status command. If the monitor is gone but the
other RDF processes are still present, then the process was probably
either manually stopped from TACL or perhaps is was stopped by a
double CPU failure. If you can confirm that the monitor is stopped and
the other RDF processes are running, you should manually stop all
surviving RDF processes by issuing the following TACL command on
both the primary and backup systems: STATUS *, PROG
$SYSTEM.RDF.*, STOP. This example assumes the location of the RDF
software is $SYSTEM.RDF.
Main STATUS RDF Display
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 preceding example, the extractor $REXT0 and receiver $RRCV0
Performing Routine Operational Tasks 105