RDF System Management Manual for H-Series RVUs (RDF 1.8)

Cause This message is issued by the purger if it has to terminate the current purge pass for
one of a variety of reasons. The reason codes refer to the internal conditions that might be of
use to support and development staff.
Effect The purger terminates the current purge pass. A new purge pass will be initiated
after PURGETIME minutes.
Recovery This is an informational event. Under normal conditions, it should be logged
infrequently. If the event appears regularly and if the purger stops purging files, then it could
be an indication of throughput problems between the extractor and receiver processes. If this
message persists, the purger has stopped purging old image files, and the extractor has not
fallen behind, please contact your service provider.
835
RDFCOM csv command-text [ issued by userid ]
csv
specifies the RDF control subvolume of the affected RDF environment.
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
RDF Messages 371