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

TMF is not running.
Cause While either attempting to validate the RDF configuration or to start RDF, RDFCOM
discovered that TMF is not running.
Effect The command fails.
Recovery Start TMF. Then validate your configuration and start RDF.
TMF is not started yet.
Cause TMF has not been started.
Effect The requested RDFCOM operation fails.
Recovery Check the contents of the RDF configuration file, issue a VALIDATE RDF command
to verify the configuration, and reissue your request for the RDFCOM operation you originally
wanted to perform.
TMF NAT table is full.
Cause There is a problem with TMF.
Effect The configuration validation fails.
Recovery Check the status of TMF. When TMF is operational, reenter the command.
TMF Shutdown at timestamp has been found. RDF starts with MAT file
filename at RBA relative-byte-address
timestamp
is the shutdown timestamp sought.
filename
is the name of the MAT file that contained the record with the matching timestamp.
relative-byte-address
is the relative byte address where the record with the matching timestamp was found in
the MAT file.
Cause RDFCOM has found the TMF shutdown timestamp identical to the timestamp
specified in the INITIALIZE RDF timestamp command.
Effect RDF is ready to be initialized at the specified timestamp.
Recovery This is an informational message; no recovery is required.
TMF STOP in progress.
Cause A TMF stop operation is in progress.
Effect TMF stops, and RDF automatically stops thereafter.
Recovery This is an informational message; no recovery is required.
To issue this command, the RTD time of the extractor must be 0:00. Have
you confirmed that the RTD is 0:00?
Cause You are attempting to execute an RDFCOM STOP SYNCH command. To ensure that
the extractor does not miss any audit information, the extractor RTD must be 0:00 before
executing this command.
Effect You are prompted for a “yes” or “no” response.
Recovery Enter YES (or Y) to execute the command or NO (or N) to cancel it.
Too many volumes are configured (number > max)
max
is 64 for RDF, and 255 for the RDF/MP, MPX, IMP, or IMPX
Cause The maximum number of volumes that can be protected on a node (64 for RDF, 255
for RDF/MP, MPX, IMP, or IMPX) has been exceeded.
Effect The configuration validation fails.
426 Messages