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

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
426 Messages