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

VALIDATE CONFIGURATION
The VALIDATE CONFIGURATION command validates the parameters in the RDF configuration file
and optionally generates a report on the status of validations.
VALIDATE CONFIGURATION [, REPORT [filename]]
where,
REPORT [filename]
is an optional parameter used to generate report on the result of validations. Validation reports
for the following scenarios are generated:
• A filename is not provided, the report is generated on the screen.
• The filename provided is an EDIT (101 coded) file.
A fully qualified name is not provided, the file is searched in the current subvolume. If the
file does not exist, an EDIT file is created and the report is written to that file.
• The filename provided is not an EDIT file. In this case, an error is reported.
• A filename is provided and it is a valid spooler location, the report is generated on the
spooler.
• File-system error encountered during the report generation.
Where Issued
Primary system only.
Security Restrictions
You can issue the VALIDATE CONFIGURATION command if you are a member of the super ID
group.
RDF State Requirement
You can only issue the VALIDATE CONFIGURATION command while RDF is stopped.
Usage Guidelines
It is often useful to issue a VALIDATE CONFIGURATION command just prior to issuing a START
RDF command. If the validation check reveals errors in the configuration file, you can correct them
immediately, ensuring that the START RDF operation will complete successfully.
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 the following:
• 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 monitor, extractor, receiver, purger, and network RDF program files are licensed.
• The user-specified process names are not in use and are not repeated from an existing
configuration.
• 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).
RDFCOM Commands 247