Lockstep And Auxiliary Audit Trails; Lockstep And Network Transactions; Lockstep Gateway Event Messages - HP NonStop RDF J-series RVUs Management Manual

transaction is in progress, the RDF gateway merely queues the request. Consequently, if an
application process issues a DoLockstep request immediately after the gateway has started a
lockstep transaction, that request must wait to be performed until the current lockstep transaction
is committed on the backup system. That could also increase response times.

Lockstep and Auxiliary Audit Trails

You cannot use lockstep processing in an RDF subsystem that is protecting auxiliary audit trails.

Lockstep and Network Transactions

You cannot use lockstep to protect data associated with network transactions because the lockstep
protocol only pertains to operations on a single system. If lockstep is used with network
transactions, consistency between lockstep operations and the distributed application database
files cannot be guaranteed after an RDF takeover.
For a description of lockstep operation event messages, see
(page 314)

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
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
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
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
ENABLE or DISABLE as the first argument of the STARTUPMSG attribute.
4
The lockstep gateway has received error errnum when attempting to
communicate with the RDF extractor procname.
314 Process-Lockstep Operation
This is an internal error, but the gateway is restarted. If the problem persists, contact
In your SCF script for starting the lockstep gateway, you must specify either
In your SCF script for starting the lockstep gateway, you must specify either
"Lockstep Gateway Event Messages"
Chapter 8 (page 187).