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

Transaction processing need not be enabled on the primary system, however, when you enter
the VALIDATE CONFIGURATION command.
Whenever you issue a START RDF command, RDF automatically validates the configuration as
though a VALIDATE CONFIGURATION command was explicitly issued.
In response to a VALIDATE CONFIGURATION command, RDF verifies:
• RDF global options are configured.
• RDF is initialized, and TMF is running on the primary system.
• The monitor, extractor, receiver, purger, and at least one updater are all configured.
• The primary and backup CPUs are different from each other for each of the monitor, extractor,
receiver, purger, and updater processes.
• The TMF audit trail referred to by the context file exists (for an RDF restart).
• All necessary RDF image files are present (for an RDF restart).
• The volumes for the image files (specified by the RDFVOLUME option of a SET RECEIVER
command and any ADD IMAGETRAIL commands) are valid and exist on the backup system.
• The volumes for the image files have enough room for two more image files (for an RDF
restart).
• The primary volumes associated with the updater processes are valid and are being audited
to the TMF audit trail.
• The backup volume associated with each updater process (specified by the UPDATEVOLUME
option of the SET VOLUME command) exists on the backup system.
• Mapping strings specified in the mapfiles of all the updaters are valid.
If RDFCOM detects any configuration errors, it displays an appropriate message.
Example
To validate the RDF configuration, enter:
]VALIDATE CONFIGURATION
If the current content of the RDF configuration file is valid, RDFCOM displays this message:
Configuration Validated
If any of the parameters in the RDF configuration file are not valid, RDFCOM displays a message
such as:
BACKUPSYSTEM (\TORONTO) is not available
RECEIVER RDFVOLUME $TRAIN does not exist
RDFCOM Commands 243