RDF/IMP, IMPX, and ZLT System Management Manual

Process-Lockstep Operation
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
14-8
Lockstep and Network Transactions
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.
Lockstep Operation Event Messages
1
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 Customer Support Center (GCSC) or your service
provider.
2
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. Note that the process name must not include a node name.
3
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.
I/O completed on an unknown file number.
A STARTUPMSG argument is missing for the lockstep gateway.
The first argument of the STARTUPMSG attribute for your
lockstep gateway was neither ENABLE nor DISABLE.