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

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 special file on its PNETTXVOLUME volume. If the communications line to one of those primary
systems is down, and you then issue a STOP RDF command on the network master’s primary
system, the STOP RDF command could appear to hang. The reason for this is that the RDFNET
process might be trying to open a file for the system whose path is down. In such a case, the
RDFNET process waits until either the line comes back up or the Expand level-4 timer expires.
If the RDFNET process must wait for the Expand level-4 timer to expire, it will not be able to
respond to the STOP RDF or abort RDF request until the timer expires. By default, the timer is
four or five minutes.
If you are waiting for the network master subsystem to shut down, and the operation does not
appear to be happening, check the communication lines to the other systems in the network. If
284 Network Transactions