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

WARNING: No backup cpu has been configured for the procname
procname
is the RDF process without a backup CPU, which is one of: EXTRACTOR, MONITOR,
RECEIVER, or $volume UPDATER.
Cause
RDF is started without a backup process for the process identified in this message.
Effect
RDF is started.
Recovery
Stop RDF, reconfigure it to include a backup CPU for the RDF process, and start the subsystem
once again.
* * * WARNING * * * NSA SQL DDL operation encountered in the audit
trail. If you have already performed this DDL operation on the backup
database, you should initialize RDF to a later point in the audit trail.
Cause
You tried to initialize RDF to a timestamp, and RDFCOM encountered an audit record indicating
that you previously performed a SQL shared-access DDL operation.
Effect
The operation completes.
Recovery
This is an informational message. If you already performed the SQL DDL operation manually on
the backup system, then you must reinitialize RDF to a later point in time. Failure to do so could
cause a cascade of errors by RDF updaters after you start RDF.
WARNING - PRIMARYSWAP parameter has no effect, KMSF swap volume takes
precedence
Cause
The user attempted to SET or ALTER the RDF PRIMARYSWAP parameter.
Effect
This parameter no longer has any effect. The KMSF subsystem controls the placement of the RDF
processes’ swap files.
Recovery
This is an informational message; no recovery is required.
* * * WARNING * * * RDF will start at the first record in the TMF master
audit trail beyond the specified shutdown timestamp. RDF will ignore
all audit generated before this timestamp.
Cause
You entered an INITIALIZE RDF command that attempted to initialize RDF at a specific TMF
shutdown timestamp.
Effect
RDF is ready to start reading the Master Audit Trail (MAT).
Recovery
This is an informational message; no recovery is required.
* * * WARNING * * * RDF will start at the first record in the TMF master
audit trail whose timestamp is less than the specified timestamp. The
timestamp you specified must follow the documented guidelines.
RDFCOM Messages 483