RDF System Management Manual for H-Series RVUs (RDF 1.8)
C Messages
This appendix describes the lockstep gateway messages and all messages generated by RDF.
The RDF subsystem produces three general types of messages:
• “Lockstep Gateway Event Messages”, which are reported during NEED INFO HERE.
• “RDF Messages” (page 342), which are reported any time by RDF and directed to the
configured EMS event log (collector)
• “RDFCOM Messages” (page 389), which are reported during your RDFCOM sessions and
directed to your terminal or alternate output device
• “RDFSCAN Messages” (page 434), which are reported during your RDFSCAN sessions and
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 “RDFCOM-Related Filenames and Process Identifiers” (page 176) and the
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.
Lockstep Gateway Event Messages
Lockstep gateway messages are sent to the configured EMS event log (collector). You specify
the EMS event log by using the SET RDF command described in Chapter 8 (page 173).
1
I/O completed on an unknown file number.
Cause While reading $RECEIVE, the lockstep gateway received an I/O completion on an
unknown file number.
Effect The lockstep gateway stops.
Recovery This is an internal error, but the gateway is restarted. If the problem persists,
contact the Global Mission Critical Solution Center (GMCSC) or your service provider.
2
A STARTUPMSG argument is missing for the lockstep gateway.
Cause You are missing either the ENABLE/DISABLE argument, or you have not specified
the name of the RDF extractor.
About the Message Descriptions 335










