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

5. When all other RDF subsystems in the RDF network list 0:00 extractor RTD times, issue the
RDFCOM START RDF command on the system where you had stopped RDF.
6. Perform your shared access NonStop SQL/MP DDL operation on your primary system.
7. Follow the normal method for replicating shared access NonStop SQL/MP DDL operations
on your backup system.
Network Validation and Considerations
A set of rules has been devised to ensure that all RDF subsystems in your configured RDF network
are consistent with each other.
1. You must validate all non network master subsystems before validating the network master’s
subsystem.
2. Because you cannot validate the network master until all non network master subsystems have
been validated, you cannot start the network master until all non network master subsystems
have been validated.
3. If you have validated a non network master, you are allowed to start that subsystem even
though the network master has not been validated.
See Appendix C (page 346) for the error messages that can occur during validation steps.
NOTE: It is strongly recommended that you validate the configurations of all RDF subsystems in
your RDF network with the RDFCOM VALIDATE CONFIGURATION command before you attempt
to start any. This would then guarantee that your entire RDF network is configured correctly before
you start any of the individual RDF subsystems.
RDF Reinitialization in a Network Environment
For any number of reasons you might choose to stop some of your RDF network subsystems and
reinitialize them. This can be done without impacting the other subsystems in the RDF network.
When you reconfigure those subsystems after initialization, there are several considerations.
Network Master Subsystem Initialization
When you reconfigure the subsystem, the network record must list all the non network master
systems and the information for each system in the network record must be identical to the previous
configuration. If not, validation will fail and you will not be able to start the subsystem.
Non-Network Master Subsystem Initialization
If you reconfigure the RDF subsystem of a non-network master:
1. The network configuration record must point to the network master of the RDF network.
2. You must ensure that the updater responsible for the PNETTXVOLUME is also configured to
the same image trail as that listed in the network master’s network configuration record.
Otherwise, validation will fail and you will be unable to start the newly configured subsystem.
NOTE: If you must change the PNETTXVOLUME, the imagetrail, or the RDFVOLUME of any
subsystem in your RDF network, then you must stop and reinitialize all of the RDF subsystems
in that network.
RDF Networks and ABORT or STOP RDF Operations
If no network transactions are active, you can stop RDF on any subsystem at any time without
affecting the other systems in an RDF network. The same is true with regard to an RDF monitor
process aborting its RDF subsystem.
There is, however, one exceptional situation. The RDFNET process runs on the network master’s
primary system. For every primary system in the RDF network, the RDFNET process maintains a
Network Validation and Considerations 287