C Messages; About The Message Descriptions; Rdf Messages - HP NonStop RDF J-series RVUs Management Manual

C Messages

This appendix describes the messages generated by RDF. The RDF subsystem produces three
general types of messages:
• "RDF Messages" (page
configured EMS event log (collector)
• "RDFCOM Messages" (page
directed to your terminal or alternate output device
• "RDFSCAN Messages" (page
directed to your terminal or alternate output device

About the Message Descriptions

In each message description presented in this appendix, this information appears:
• Message number (lockstep gateway and RDF event messages only)
• Message text
• Error codes and parameters—explanations of variables that indicate specific error details,
files, devices, and other elements that appear within the message text
• Cause—the condition or error that produced the message
• Effect—the effect of the condition or error on the system
• Recovery—the steps required to recover from a reported error
Some messages include information from the operating system's file system. When present, this
information, typically a numeric code, appears in the error# or number parameter in the
message description. For the meaning of this code and related information, see the Guardian
Procedure Errors and Messages Manual and the Operator Messages Manual.
Many messages include file names that identify objects such as disk files and processes. When
present, these names appear in the message descriptions as parameters such as filename or
procname. Sometimes, these messages simply report syntax errors that result from improperly
specifying these file names in commands. For more information about file names and the rules
that govern them, see
Guardian Procedure Calls Reference Manual.
You can also receive messages from the NonStop operating system. See the Guardian Procedure
Errors and Messages Manual and the Operator Messages Manual for information about those
messages.

RDF Messages

RDF messages, unlike RDFCOM and RDFSCAN messages, do not appear on your terminal or
workstation screen. Instead, RDF sends these messages to the configured EMS event log (collector).
You specify the EMS event log by using the SET RDF command described in
You can change the EMS event log while RDF is running. The following example shows part of
an EMS event log.
(1)
2007/01/09 16:11:02 \NYC
2007/01/09 16:11:25 \NYC
2007/01/09 16:11:32 \NYC
(1) The date the message occurred.
on the sending system.
(2) The time the message occurred.
on the sending system.
365), which are reported any time by RDF and directed to the
413), which are reported during your RDFCOM sessions and
461), which are reported during your RDFSCAN sessions and
"RDFCOM-Related Filenames and Process Identifiers" (page 190)
(2) (3) (4)
$RCV
$U01
$U02
(5) (6)
771 RDF Remote Receiver Started
773 RDF Remote Updater Started
$DB0001 =>$BB0001
773 RDF Remote Updater Started
$DB0002 =>$BB0002
The clock used is the clock
The clock used is the clock
Chapter 8 (page
About the Message Descriptions
and the
187).
365