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

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 175).
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.
Effect
The lockstep gateway stops.
Recovery
In your SCF script for starting the lockstep gateway, you must specify either ENABLE or DISABLE
and the RDF extractor process name with the STARTUPMSG attribute. The process name must
not include a node name.
3
The first argument of the STARTUPMSG attribute for your lockstep gateway
was neither ENABLE nor DISABLE.
Cause
You did not specify ENABLE or DISABLE as the first argument of the STARTUPMSG attribute in
your SCF script.
Effect
The lockstep gateway stops.
Recovery
In your SCF script for starting the lockstep gateway, you must specify either ENABLE or DISABLE
as the first argument of the STARTUPMSG attribute.
4
The lockstep gateway received error errnum when attempting to communicate
with the RDF extractor procname with ATINDEX indexnum.
errnum
is a file-system error number.
procname
is the name of an extractor process.
Lockstep Gateway Event Messages 305