Compaq AA-Q88CE-TE System Manager's Manual page 307

Rtr
Table of Contents

Advertisement

%RTR-I-FACLOSTFE, Facility [A] lost Frontend node [A]
Explanation: This node is no longer a current router on facility [A], for
frontend node [B]
%RTR-I-FACLOSTTR, Facility [A] lost Router node [A]
Explanation: A connection has been lost with router node [B] on facility [A]
%RTR-E-FACNOTDEC, Facility name not matched
Explanation: Result of a connection attempt to a remote node specifying a
facility that does not (yet) exist on the remote node. Check that the facility
name and configuration matches on all nodes concerned. If connecting to a
V2 system, facility names must be specified in upper case.
%RTR-I-FACSTART, Facility [A] started on node [A]
Explanation: Facility [A] initialized on node [B]
%RTR-I-FACSTARTBE, Facility [A] started on node [A] as Backend
Explanation: A connection has been established with backend node [B] on
facility [A]
%RTR-I-FACSTARTFE, Facility [A] started on node [A] as Frontend
Explanation: This node is now a current router for frontend [B], facility [A]
%RTR-I-FACSTARTTR, Facility [A] started on node [A] as Router
Explanation: A connection has been established with router node [B] on
facility [A]
%RTR-I-FACSTOP, Facility [A] stopped on node [A]
Explanation:
%RTR-I-FACSTOPPED, Facility [A] stopped on local node
Explanation:
%RTR-I-FACTRMBE, Facility [A] modified, [A] no longer a backend
Explanation: The configuration of facility [A] has been modified to exclude
node [B] as a backend.
%RTR-I-FACTRMFE, Facility [A] modified, [A] no longer a frontend
Explanation: The configuration of facility [A] has been modified to exclude
node [B] as a frontend.
%RTR-I-FACTRMTR, Facility [A] modified, [A] no longer a router
Explanation: The configuration of facility [A] has been modified to exclude
node [B] as a router.
%RTR-I-IGNREJACCEPTTX, Ignoring recovered aborted part TX for committed
TX
Explanation: Status indicating that a part TX in aborted state was
recovered from journal. However, the TX is already in committed state on the
recovering node, so the aborted part-TX is ignored. This can happen under
unusual circumstances such as where the TX has been rejected on one BE
and on another BE the same TX has been later accepted (whether because
of application inconsistency, or due to some condition in RTR such as journal
RTR log messages
RTR log messages E–5

Advertisement

Table of Contents
loading

This manual is also suitable for:

Reliable transaction router, version 3.2

Table of Contents

Save PDF