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

759
Secondary partition on unknown node filename
filename
is the name of the affected file.
Cause
An updater has encountered an audit record associated with either an Enscribe create, an
increase of MAXEXTENTS for an Enscribe file, or a PURGEDATA operation for an Enscribe file,
and the file on the primary system has secondary partitions that are located on different systems
in the network.
Effect
The updater skips this record. If the record is associated with an Enscribe create operation, the
specific partition of the file is not created on the backup system. Therefore, if the updater
subsequently encounters another audit record associated with that file, the updater pauses its
processing until that file is created.
Alternatively, if the record was associated with a PURGEDATA or increase to MAXEXTENTS,
the operation is not replicated on the backup system.
Recovery
If the record was associated with an Enscribe create, you must manually create the file on the
backup system. If the record was associated with a PURGEDATA or increase to MAXEXTENTS,
you must issue the STOP UPDATE command and then perform the operation manually on the
backup system.
760
Image trail file purged filename
filename
is the name of an image trail file.
Cause
The purger has determined that the specified image file is no longer needed and has purged it.
Effect
The specified file is purged.
Recovery
This is an informational message; no recovery is required.
761
Backup stopped
Cause
The backup process of a process pair has been stopped. This probably was the result of an
operator inadvertently issuing a STOP command from TACL.
Effect
A new backup will be created.
Recovery
This is an informational message; no recovery is required.
762
Context file is old; must INITIALIZE RDF
Cause
An RDF process has determined that the existing context file belongs to an older version of RDF.
Effect
You cannot start the RDF subsystem.
RDF Messages 365