RDF System Management Manual for H-Series and J-Series RVUs (RDF 1.9)

cpu:cpu
are the primary and backup CPUs, respectively.
Cause Both the configured primary and backup CPUs were unavailable when a START RDF
command was issued.
Effect The command fails.
Recovery Wait until both CPUs become available, and reenter the START RDF command.
If necessary, see your system manager.
cpu:cpu CPUS are not SYSGEN’d
cpu:cpu
are the primary and backup CPUs, respectively.
Cause A START RDF command failed because the specified CPUs do not exist (they were
not configured during SYSGEN).
Effect The command fails.
Recovery Reconfigure RDF to use other CPUs or, if you must use the specified CPUs, see
your system manager.
Creation error error# on IMAGETRAIL volume-name
error#
is the file-system error number that identifies the specific error.
volume-name
is the image trail volume on which the error occurred.
Cause During execution of a START RDF command or a VALIDATE CONFIGURATION
command, RDFCOM determined that sufficient disk storage for image files did not exist in
each secondary image trail for at least one additional image file. As one of its validation checks
during processing of these commands, RDFCOM tries to create a temporary image file on the
IMAGETRAIL volume. This allocation failed for the reason indicated by the file-system number
error#.
Effect The command fails.
Recovery See the Operator Messages Manual for a description of the error code. For additional
details about understanding and correcting file-system errors, see the Guardian Procedure Errors
and Messages Manual. Correct the error indicated by error#. This might necessitate altering
the IMAGETRAIL configuration parameter to specify a new volume for the secondary image
trail. Then, reenter the START RDF or VALIDATE command.
Ctrl-subvol network record not found
Ctrl-subvol
is the name of an RDF subsystem control subvolume.
Cause The RDF subsystem with the specified control subvolume does not contain a network
record.
Effect Validation fails.
Recovery You must add the appropriate NETWORK configuration record.
Database synchronization is only available with the NonStop(TM)
RDF/IMP(X) product
Cause You tried to add a volume to the RDF configuration and use the online database
synchronization feature, but RDF/IMP or IMPX is not installed.
Effect The ADD command fails.
Recovery If you want to perform online database synchronization, RDF/IMP or IMPX must
be installed on both the primary and backup systems.
Data from auxiliary audit trails is not allowed with lockstep
418 Messages