HP NonStop RDF J-series RVUs Management Manual page 395

command-text
is the text of the command that was issued.
userid
if present, is the Guardian userid (group.user) of the user who issued the command.
Cause RDFCOM logs this message whenever you issue any of these commands: ALTER,
INITIALIZE RDF, START RDF, START UPDATE, STOP RDF, STOP UPDATE, or TAKEOVER.
command-text is the command text. If the event includes a userid, it indicates that the userid
was not the RDF OWNER or that the userid was not the owner of the RDFCOM object file.
The userid included in the message is the Guardian userid of the user who issued the
associated command.
Effect
The specified RDFCOM command is executed.
Recovery
This is an informational message; no recovery is required.
836
Volume is not enabled for transaction processing
Volume
is the name of the affected volume.
Cause
TMF reports that the specified updatevolume is not enabled. This might be the result
of an earlier failure and the volume is still recovering, or the user has disabled the volume in
TMFCOM.
Effect
The updater is unable to apply updates to this volume until the datavol is enabled.
The updater retries the operation every minute until the volume is enabled.
Recovery
If the volume is recovering, the updater resumes processing once the volume
becomes enabled. If the datavol has been manually disabled, you must enable the datavol to
allow the updater to resume operations.
837
Info - Restarting at image trail file position SNO sno RBA rba
sno
is the sequence number of the image file in use at the updater restart.
rba
is the relative byte address in the image file where the updater restart occurred.
Cause This informational message is logged by an updater when it begins a restart operation.
The image file sequence number and the relative byte address within that image file are
included in the message.
Effect
An updater restart is performed under a variety of circumstances, such as a failure in
the primary CPU of the updater, a failure in the primary CPU of the corresponding disk process,
or various file errors. The reason for the updater restart can be determined from previous
messages. During an updater restart, file-system errors 10, 11, and 71 are not reported by the
updater because they probably represent database operations that have already been performed.
Recovery
Perform any corrective actions suggested by the preceding messages (actions such
as reloading the appropriate CPU, correcting the underlying file error condition).
838
RDFNET process has terminated unexpectedly
Cause
The RDFNET process has terminated unexpectedly.
Effect
This message is issued by the RDF monitor. The monitor sends an abort request to all
remaining RDF processes to stop RDF.
Recovery
Determine the reason why the RDFNET process stopped, correct that problem,
then restart RDF. If the problem persists, contact your service provider.
RDF Messages 395