Reliable Transaction Router
System Manager's Manual
Probable cause:
System management error. A user has copied a journal file, or a disk
containing a journal file. RTR can now see extra journal files, or
copies, that do not belong in the set.
Corrective action, either:
(a) Check the log for the relevant filenames, and delete or move the
spurious journal file or files, or
(b) Reissue the CREATE JOURNAL /SUPERSEDE command (in this case any
recovery information in the old journal is lost).
%RTR-I-STACOMSRV, Starting command server on node [A][A]
Explanation: Indicates that a command server is being
started on node [A].
%RTR-E-SUPCHAEND, Superfluous characters at end of expression, [A]
Explanation: The expression is invalid because the
characters [A] at the end of the expression could not be interpreted.
%RTR-I-SYSSRVCOM, [A] completed on channel [A]
Explanation: Displays the name [A] of the operation
that completed on a channel after issuing a "SYS$SYNCH" command.
%RTR-I-SYSSRVNOW, [A] posted with no wait on channel [A]
Explanation: Displays the name [A] of the operation
that was issued with the "/NOWAIT" qualifier on channel [B].
%RTR-E-TEMPLATE_NOT_FE, Template link [A] valid for front-ends only
Explanation: Template link names are valid for front
end roles only. It is an error to attempt to associate a template link
name with the router or back end roles. A template link is link whose
name contains one or more wild characters chosen from the set "*?%".
'*' indicates a sequence of wild characters; '?' and '%' indicate an
occurrence of a single wild character.
%RTR-F-TIOSYS_FAILURE, General failure in TIO
Explanation: General failure in terminal I/O.
%RTR-F-TIO_BADROWCOL, The terminal is defined as : rows = [A] and cols
= [A]
Explanation: Cannot use the terminal; rows or columns
is set to 0. For UNIX platforms, please use "stty -a" to check rows and
columns. Then use a command like "stty rows 50 cols 132" to set them
correctly.
%RTR-E-TOOBIG, [A] may not be greater than [A]
Explanation: The value of qualifier [A] must be less
or equal to [B].
%RTR-F-TOOMANCHA, Too many channels already opened
Explanation: Too many channels already opened.
%RTR-E-TOOMANCHN, Too many channels
Explanation: Displayed when a "SYS$DCL_TX_PRC" command
is issued and the channel table is full.
%RTR-F-TOOMANDIS, Too many disks specified in journal definition
Explanation: Explanation: Too many disks were
specified in journal definition. The RTR journal can be defined to use
up to a maximum of sixteen disks.
User Action: Issue the CREATE JOURNAL command specifying a smaller
number of disks.
%RTR-F-TOOMANREC, Too many records for one entry in the journal
Explanation: An attempt was made to write more than
65534 records to one entry (transaction) in the journal.
%RTR-E-TOOMANYOBJ, Max DECnet objects exceeded, raise and retry command
Explanation: The executor limit on the number of
DECnet connect objects has been exceeded. Please use NCP to raise the
maximum number of objects on this node.
%RTR-E-TOOMANYSELITM, More then one selitm specified in data-class :[A]
Explanation: More then one selitm specified in
data-class on call to rtr_request_info.
%RTR-E-TOOMUCDAT, Too much data to be monitored
Explanation: An attempt was made to monitor too many
processes. Please submit an SPR.
%RTR-E-TOOSMALL, [A] may not be less than [A]
Explanation: The value of qualifier [A] must be
greater or equal to [B].
%RTR-I-TRMCENTRYNFND, No termcap-entry for terminal-type : [A].
Explanation: No such entry was found in the termcap
file for the terminal type. For UNIX platforms, please check that the
environment variables "TERM" and/or "TERMCAP" (if used) are correct.
Also check that the TERMCAP file (if used) has a valid entry for your
terminal type. (NOTE: These entries are case-sensitive.) The default
terminal type is vt100.
%RTR-E-TRNOTALL032, Not all routers are at the minimum required version
of V3.2
Explanation: Cannot perform the requested action since
not all routers are at a minimum version of V3.2
%RTR-F-TRUNCATED, Buffer too short for msg
Explanation: Buffer too short for message, message
truncated.
%RTR-F-TXNOTACT, No tx currently active on chan
Explanation: No transaction currently active on
channel.
%RTR-E-UICNOTGRP, UIC [A] cannot be used in GROUP mode
Explanation: A "SET MODE/GROUP" command was issued
while running under system UIC (group one). System UIC's cannot be used
in group mode.
%RTR-E-UNEXPEND, Expression ended before [A] encountered
Explanation: The expression is invalid because it
terminated where when token [A] was expected.
%RTR-E-UNKNOWQUAL, Invalid qualifier keyword value - check your program
Explanation: Status return indicating that an
unrecognised qualifier keyword value was supplied. Check your program,
and refer to the RTR Application Programmer's Reference Manual for
permissible values.
%RTR-F-UNRROUNAM, Unrecognised api routine name for CALL
Explanation: The parameter for the CALL command is the
name (or part of a name) of an rtr api routine. This allows the user to
type, e.g. rtr call accept instead of rtr call rtr_accept_tx. This
message is issued if the user has specified a part of an api routine
name that does not match the name of an rtr api routine.
%RTR-F-VALREQ, Missing qualifier or keyword value - supply all required
values
Explanation: A value must be specified for the keyword
or qualifier.
%RTR-F-VALTOOBIG, 0x[A] is too big for [A] byte number
Explanation: A value has been specified that cannot be
stored in the number of bytes specified. Specify a smaller value or a
larger number of bytes.
%RTR-E-VERMISMAT, RTR version mismatch
Explanation: Indicates that utilities and/or sharable
images being used are intended for a different version of RTR to that
which is currently running on the system.
This message can however be ignored when it is displayed after issuing
the first "STOP RTR" command after having just installed a new RTR
release.
%RTR-I-WFPROCESS, Waiting for [A] to start up
Explanation: Displays the name [A] of the operation
that completed on a channel after issuing a "SYS$SYNCH" command.
%RTR-E-WILNOTALL, Wild cards not allowed
Explanation: Wildcards ("%" and "*") are not allowed.
%RTR-E-WTTR, Not in contact with sufficient router nodes - please retry
later
Explanation: Returned by a set partition command when
either inquorate or no routers available to process the command. Try
again later when none of the above conditions exist.
Appendix E
RTR log messages
This appendix describes the various error messages that can be sent to
the operator console or written to RTR's operator log file.
%RTR-E-ABODEAREQ, Transaction aborted that was started by client that
has since exited
Explanation: Indicates that a transaction has been
aborted that was started by a client that has since exited.
%RTR-E-ABODEASRV, Transaction aborted that was accepted by a server
that has since exited
Explanation: Indicates that a transaction has been
aborted that was sent to a server that has since exited.
%RTR-E-ACCERR, Rejecting connect attempt from unconfigured node [A]
Explanation: Node [A] which has not been configured as
part of any RTR facility is trying to establish connection. This could
be a misconfiguration problem, or simply a problem with the setting up
of the DNS service if DECnet-OSI is running.
%RTR-F-ACPINSRES, The RTR ACP has insufficient resources: details in
the rtr log file
Explanation: The RTR ACP was unable to perform an
operation due to an unusual condition. This is most probably a resource
issue, e.g. when the ACP cannot create a shared memory segment.
The RTR log file for contains more details of the problem.
%RTR-E-ALRDCNCTD, Remote node already connected
Explanation: This can be a reason for rejecting a
connect request. Submit an SPR.
%RTR-E-ALRINPRGS, Connection already in progress
Explanation: This can happen if both ACPs
simultaneously try to connect to each other Submit an SPR.
%RTR-E-BADENVVARIABLE, Environment variable [A] has bad value [A]
Explanation: Log file message indicating that an
environment variable has been defined with an illegal value.
%RTR-E-BADIDSIZ, Bad node ID size [A] detected at 0x[A]
Explanation: This message indicates that errors have
been detected in processing of an internal node identifier. The
presence of this message indicates a serious problem in the
configuration of the network name/address databases, and RTR will
likely be unable to operate correctly. Quorum and fault tolerance will
be adversely affected. Check all network databases for consistency of
node & host name and address consistency.
%RTR-E-BADIDTYP, Empty node ID encountered at 0x[A]
Explanation: This message indicates that errors have
been detected in processing of an internal node identifier. The
presence of this message indicates a serious problem in the
configuration of the network name/address databases, and RTR will
likely be unable to operate correctly. Quorum and fault tolerance will
be adversely affected. Check all network databases for consistency of
node & host name and address consistency.
%RTR-E-BADNETMSG, Bad message received from [A] - check network
hardware? Indications %u %u %u %u %u %u %u
Explanation: This message is logged when RTR in unable
to interpret the content of a network message received from a remote
RTR ACP process. Message corruption is the most likely culprit. If the
condition persists, consider a network health check. The indication
numbers printed at the end of the message have meaning to RTR support
engineers only.
%RTR-I-BEINQUO, Backend is quorate in facility [A]
Explanation: The backend role now has quorum in the
facility [A]
%RTR-W-BENOQUO, Backend has no quorum in facility [A]
Explanation: The backend role has lost quorum for
facility [A]
%RTR-E-BEREPLAYQDELETED, Replay queue for BE deleted
Explanation: A transaction in progress on a backend
has had its (replay) queue of replies to the client deleted. Please
report to RTR Engineering.
%RTR-E-BMHDRVSN, Unrecognised broadcast from [A] for facility [A] -
check network? Indications %u %u %u [A]
Explanation: A node has received an unrecognised
broadcast event from the indicated node. If the sending and receiving
nodes are running compatible versions of RTR, the cause of this might
be message corruption. If the condition persists, consider performing a
network health check.
%RTR-F-BRODISBLO, Broadcast message(s) discarded because of network
blockage
Explanation: One or more broadcast messages had to be
discarded because the network throughput is not fast enough. Reduce
broadcast rate or increase communications link capacity.
%RTR-F-BRODISCAC, Broadcast message(s) discarded because of memory
cache congestion
Explanation: One or more broadcast messages had to be
discarded because local memory was exhausted. Reduce the rate at which
broadcasts are sent, or increase the efficiency of broadcast processing
by the recipient applications.
%RTR-F-BRODISLIN, Broadcast message(s) discarded because of link
unavailability
Explanation: One or more broadcast messages had to be
discarded because there is no logical link to the destination node.
%RTR-I-CLUENABLED, RTR cluster [A] is enabled using [A]
Explanation: Information message indicating whether
RTR is making use of any specific cluster software.
%RTR-S-CNCTACCFR, Connection request from [A] accepted
Explanation: A connection request from RTRACP running
on node [A] has been accepted.
%RTR-S-CNCTCFRM, Connection confirmed by [A]
Explanation: A connection request has been confirmed
by RTRACP running on node [A]
%RTR-I-CNCTLOST, Connection to [A] lost
Explanation: DECnet connection with node [A] lost.
%RTR-W-CNCTREJBY, Connection request rejected by [A]
Explanation: RTRACP on node [A] rejected a connect
request from this node.
%RTR-W-CNCTREJFR, Connection request from [A] rejected
Explanation: RTRACP on node [A] made a connect
request, which had to be rejected.
%RTR-E-COMDEAREQ, Transaction committed that was started by client that
has since exited
Explanation: Indicates that a transaction has been
committed that was started by a client that has since exited.
%RTR-E-COMDEASRV, Transaction committed that was accepted by a server
that has since exited
Explanation: Indicates that a transaction has been
committed that was sent to a server that has since exited.
%RTR-I-COMJOUSEA, Commencing journal search for transactions on
facility [A] needing recovery
Explanation: Journal search is starting. This message
appears when RTR is started.
%RTR-E-COMSRVFAIL, Command server failed - diagnostics written to [A]
Explanation: An instance of the RTR command server
process has failed - report occurrence together with supporting
information on current command to RTR Engineering.
%RTR-I-CONNALIAS, Link [A] connected as [A]
Explanation: Support for internet tunnels allows for
the configuration of links from which connections appear to originate
with an source address other than that by which the local node is
registered locally, for example, the connection may appear to originate
from an pseudo-adapter address assigned by the tunnel server. The
CONNALIAS message registers the acceptance of such a connection, and
lists the names of the local and connecting IP addresses.
%RTR-S-CURRTR, Node [A] now a router for facility [A]
Explanation: A new current router [A] has been found
for facility [B]
%RTR-E-CURRTRLOSS, Current router lost for facility [A]
Explanation: The router handling facility [A] for this
frontend node has failed, or [A] has been deleted on the router. No
user intervention is expected, an attempt is being made to reconnect to
an alternate router, if one is available.
%RTR-I-DTXRECOV, Commencing DTX journal search for transactions needing
recovery, log_id = %08X-%04X-%04X-%02X%02X-%02X%02X%02X%02X%02X%02X
Explanation: DTX Journal search is starting. This
message appears when RTR is started.
%RTR-I-DTXRECOVDONE, DTX journal search completed, [A] transactions
found
Explanation: DTX Journal search has completed. This
message appears when RTR is started.
%RTR-I-DUMPOBJECT, [A]: n[A]
Explanation: Object dumped to log.
%RTR-E-ENQDEAREQ, Server rtr_reply_to_client to a client that has since
exited
Explanation: Indicates that a call to
rtr_reply_to_client was made for a client that has since exited.
%RTR-I-FACEXTNBE, Facility [A] extended, with backend [A]
Explanation: The configuration of facility [A] has
been extended to include node [B] as a frontend.
%RTR-I-FACEXTNFE, Facility [A] extended, with frontend [A]
Explanation: The configuration of facility [A] has
been extended to include node [B] as a frontend.
%RTR-I-FACEXTNTR, Facility [A] extended, with router [A]
Explanation: The configuration of facility [A] has
been extended to include node [B] as a router.
%RTR-I-FACLOSTBE, Facility [A] lost Backend node [A]
Explanation: A connection has been lost with backend
node [B] on facility [A]
%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 full). RTR has ensured that the
TX has been committed, but the operator should nevertheless check the
condition on the BE where the TX was aborted to determine why this
occurred (possible resource problems on the server, for example).
%RTR-F-INCOMPAT, Incompatible RTR versions
Explanation: Attempt to start up an incompatible
version of RTR on the same network with shared facilities.
%RTR-F-INTERFERENCE, Group/system interference. Start RTR from other
account
Explanation: Internal error. Send SPR
%RTR-I-JOUEXCWRIT, Exception written to journal for transaction [A];
previous state = [A], reason status = [A]
Explanation: Indicates that an exception record has
been written for the specified transaction. Manual intervention is
required in order to see the transaction through to completion.
%RTR-W-JOUFILFUL, RTR journal file full - use MODIFY JOURNAL to
increase size
Explanation: The RTR journal file is becoming full.
Either reduce the number and size of concurrently active transactions,
or increase the size of the journal file using MODIFY JOURNAL
/MAXIMUM_BLOCKS
%RTR-F-JOUHDRERR, RTR journal record header error - CREATE JOURNAL
/SUPERSEDE and submit SPR
Explanation: An inconsistency has been found in a
record header within the RTR journal.
Corrective action:
1) Reissue the RTR CREATE JOURNAL /SUPERSEDE command.
2) Restart RTR.
3) Submit an SPR.
%RTR-E-JOUNOTAVA, Error during recovery ([A]) from [A] journal ([A])
Explanation: RTR transaction manager requested
recovery from a remote journal, but the request could not be delivered
to the node hosting the journal. In a non-clustered standby
configuration, this indicates that local recovery after a server
failure could not be completed. No user action required, since the
transaction manager will attempt to send the recovery query again, once
it has detected that the remote journal has become available.
%RTR-F-JOUOVERFL, RTR journal file overflow - transaction recovery
information lost
Explanation: The journal file is so full that some
transaction recovery information has had to be discarded. One or more
of the currently active transactions may be incorrectly recovered if a
system failure occurs in the near future.
%RTR-I-JOUSEACOM, Journal search on facility [A] completed. [A]
recoverable transactions found
Explanation: Journal search has completed. This
message appears when RTR is started The number of transactions needing
recovery is indicated by [A].
%RTR-F-JOUSEQERR, RTR journal record sequence error - CREATE JOURNAL
/SUPERSEDE and submit SPR
Explanation: An inconsistency has been found in the
record sequence within the RTR journal.
Corrective action:
1) Reissue the RTR CREATE JOURNAL /SUPERSEDE command.
2) Restart RTR.
3) Submit an SPR.
%RTR-E-LINKSHUT, No longer accepting connect requests from this node
Explanation: A connection could fail between a router
and a frontend or a backend if the link is in the "closed" state. This
could happen if the link has been suspected of causing congestion to
the rest of the network. This state can also be reset by system manager
intervention.
%RTR-F-LNQOVERFLOW, LNQ table has overflowed
Explanation: This status is used to indicate an
inadequacy in the static reservations of the per-link congestion queue
header blocks. Send an SPR.
%RTR-E-LOADLIBFAIL, Unable to dynamically load the shared library
Explanation: The RTR ACP was unable to load the shared
library dynamically.
%RTR-E-LOADSYMFAIL, Unable to find the symbol in the shared library
Explanation: The RTR ACP was unable to locate the
symbol name in the lib.
%RTR-I-LOGFILENT, [A] [A] [A]
Explanation: Displays the time/date [A], node name [B]
and user name [C] associated with the subsequent error message.
%RTR-E-LRCERROR, Found a LRC error in incoming message
Explanation: The checksum, also known as Linear
Redundancy Check, was wrong in an incoming message.
%RTR-W-MESFLOCON, Message flow congestion on link to node [A] for
facility [A]
Explanation: RTR internode communication has become
congested. New messages are waiting for the congestion to clear.
%RTR-F-NETSHUT, Network has been shutdown or has become unusable ([A])
- automatic retry will follow
Explanation: This status results when someone stops
DECnet on a node running RTR Might also occur if the network fails or
otherwise becomes unusable.
%RTR-E-NOCURRTR, Current router search failed for facility [A]
Explanation: None of the routers specified for
facility [A] are currently connectable. The search will continue after
a short interval.
%RTR-W-NODENOTCNFG, Node is not configured for the facility
Explanation: Result of a connection attempt to a
remote node where the connecting link is not configured in the
requested facility at the remote node.
%RTR-W-NODISOLAT, Isolating [A], node suspected of causing congestion
Explanation: The remote node [A] has been diagnosed as
causing network congestion; RTR will isolate the node from the rest of
the network.
%RTR-W-NOFECREDIT, No credit for FE connect acceptance
Explanation: The router has no credit left to accept
any more frontends right now. Other routers can be tried.
%RTR-E-NOTCONFIGURED, RTR not configured on [A] to recognize this node
Explanation: This means that none of the facilities
defined on the local node [A] defined a valid role for the remote node
to permit a connection.
%RTR-E-NOTRECOGNISED, Node not recognized
Explanation: Result of a connection attempt to a
remote node where no facility references the connecting link at the
remote node.
%RTR-E-OBJNOTDECL, RTR network object could not be established - will
try again later
Explanation: A log file entry indicating that RTR was
unable to establish its network object, most likely because the network
was not available. A subsequent entry gives more detail on the error.
RTR will retry the operation later, but the operator should investigate
the state of the network.
%RTR-E-OBJUNKNOWN, RTRACP not running on node [A]
Explanation: A connection failed because RTR had not
been started or had died on the remote node [A].
%RTR-E-OVERFLOW, Table has overflowed, resize NCF
Explanation: This is a general status used to indicate
an inadequacy in the static reservations for the tables. Send SPR, with
RTRACP dump.
%RTR-I-PATHLOST, Node [A] unreachable, retrying
Explanation: Node [A] cannot be reached at present.
This generally means that RTR is trying to reestablish a connection.
%RTR-E-PROTOCOL, Incorrect protocol in optional data
Explanation: Internal error in messages between
RTRACPs. May be caused by network packet data loss or corruption, so
consider a network health check. If condition persists, submit an SPR.
%RTR-E-PRTBADCMD, Partition command invalid or not implemented in this
version of RTR
Explanation: Status return indicating that the ACP
received a request for an unknown partition command.
%RTR-I-PRTCMDFRMBE, Command received for partition [A]:[A] from backend
node [A]
Explanation: Log file message indicating the origin of
a command.
%RTR-E-PRTDELCAN, Partition deleted - operation canceled
Explanation: Status used to terminate a pending
operation when the partition is deleted prior to completion of the
operation.
%RTR-W-PRTLCLRECEXIT, Partition [A]:[A] local recovery terminated by
operator [A]
Explanation: Log message indicating that recovery wait
override requested by operator
%RTR-I-PRTNEWFPOL, Failover policy for partition [A]:[A] set to [A] by
operator '[A]'
Explanation: Log file entry indicating acceptance of
an operator request to change the failover policy of the indicated
partition. Also appears when RTR automatically switches to pre-V3.2
compatibility mode.
%RTR-I-PRTNEWFPOLBE, Failover policy change for partition [A]:[A]
received from router [A], new policy '[A]'
Explanation: Log file entry indicating receipt by a
backend of an operator request to change the failover policy of the
indicated partition. Also appears when RTR automatically switches to
pre-V3.2 compatibility mode.
%RTR-I-PRTNEWFPOLTR, Failover policy change for partition [A]:[A]
received from backend [A], new policy '[A]'
Explanation: Log file entry indicating receipt by a
router of an operator request to change the failover policy of the
indicated partition. Also appears when RTR automatically switches to
pre-V3.2 compatibility mode.
%RTR-I-PRTNEWPRI, Priority for partition [A]:[A] set to [A] by operator
'[A]'
Explanation: Log file entry indicating acceptance of
an operator request to change the backend priorities of the indicated
partition.
%RTR-I-PRTNEWPRITR, Priority change for partition [A]:[A] received from
backend [A], new priority [A]
Explanation: Log file entry indicating receipt by a
router of an operator request to change the priority of the indicated
partition.
%RTR-S-PRTRESUMED, Partition [A]:[A] resumed by operator [A]
Explanation: Log file entry indicating successful
completion of partition resume command. Transaction presentation is now
enabled.
%RTR-W-PRTRSTRCVY, Partition [A]:[A] recovery initiated by operator [A]
Explanation: Log message indicating that partition
recovery was manually initiated by the operator.
%RTR-I-PRTSCANJNL, Partition %ld scanning journal for node id [A]
Explanation: RTR is accessing the journal for node [B]
that may contain relevant recovery information for this key range.
%RTR-E-PRTSETFAILTR, Router unable to process command
Explanation: A partition set command failed at the
router. An entry is written to the log file describing the problem.
Message arguments are the facility name and the KR ID. A second message
is written detailing the nature of the problem.
%RTR-W-PRTSHDRECEXIT, Partition [A]:[A] shadow recovery terminated by
operator [A]
Explanation: Log message indicating that recovery wait
override requested by operator.
%RTR-I-PRTSHDWOFF, Command is set partition shadow state off
Explanation: This message appears in the router log
file indicating what sort of request has been received.
%RTR-I-PRTSHDWON, Command is set partition shadow state on
Explanation: This message appears in the router log
file indicating what sort of request has been received.
%RTR-I-PRTSUSPCAN, Suspend cancelled for partition [A]:[A], operator
[A] - partition resumed by operator
Explanation: Log file entry indicating that a pending
partition suspend operation has been cancelled as a result of an
operator command to resume the partition.
%RTR-S-PRTSUSPEND, Partition [A]:[A] suspended by operator [A]
Explanation: Log entry indicating that partition has
become suspended as the result of operator intervention.
%RTR-E-PRTSUSPTMO, Suspend timeout for partition [A]:[A], operator [A]
after [A] seconds - partition still suspending
Explanation: Log entry indication that a command to
suspend a partition timed out. The partition will still be suspending -
resume the partition to restart presentation of transactions.
%RTR-W-PRTWAITJNL, Partition %ld waiting for access to journal for node
[A]
Explanation: RTR cannot access one or more journals
that may contain relevant recovery information for this key range. The
journal referenced could be one of many unavailable journals. Either
RTR should be started up on the missing backend, or the facility should
be trimmed and the server restarted.
%RTR-F-QAROVERFLOW, No more QARs left
Explanation: This status is used to indicate an
inadequacy in the static reservations for the internal query acceptor
records. Make a note of all QRM counters using SHOW RTR /COUNTER=QRM*
Send SPR with RTRACP dump.
%RTR-F-QCROVERFLOW, QCR table has overflowed
Explanation: This status is used to indicate an
inadequacy in the static reservations for the internal query context
descriptors. Send an SPR.
%RTR-F-QIROVERFLOW, No more QIRs left
Explanation: This status is used to indicate an
inadequacy in the static reservations for the internal query initiation
descriptors. Make a note of all QRM counters using SHOW RTR
/COUNTER=QRM* Send SPR with the corresponding RTRACP dump.
%RTR-F-RAEOVERFLOW, No more RAEs
Explanation: This status is used to indicate an
inadequacy in the static reservations for the internal response
acceptor elements. Make a note of all QRM counters using SHOW RTR
/COUNTER=QRM* Send SPR with the corresponding RTRACP dump.
%RTR-F-RDEOVERFLOW, RDE table has overflowed
Explanation: This status is used to indicate an
inadequacy in the static reservations for the internal response
dispatch elements. Make a note of all QRM counters using SHOW RTR
/COUNTER=QRM* Send SPR with the corresponding RTRACP dump.
%RTR-E-REQDIED, Client exited, incomplete transaction aborted
Explanation: Indicates that a client exited before
completing a transaction.
%RTR-E-REQDIEDPREP, Client exited after calling rtr_prepare_tx,
transaction unresolved
Explanation: Indicates that a client exited after
preparing a transaction.
%RTR-E-REQDIEDVOT, Client exited after issuing rtr_accept_tx, awaiting
transaction result
Explanation: Indicates that a client died after
accepting, but before completion of a transaction.
%RTR-W-ROLESMISMATCH, Node role definitions do not match for this
facility
Explanation: The facility exists, but the definition
of the role for the remote node is not the same as the one in the local
node. The system manager has probably incorrectly defined the
facilities on the two nodes concerned.
%RTR-E-ROUTERUNAVAILTMO, FE discarded transaction due to router
unavailability timeout
Explanation: In rare circumstances, a transaction can
be aborted by an RTR frontend with the status RTR_STS_ROUTERUNAVAILTMO.
This can occur if an RTR client application has accepted the
transaction, but the link to the router is lost before the RTR frontend
has received a response from the router. If no RTR router becomes
available for more than 8 minutes, then the transaction will be aborted
by the frontend. This is to prevent the transaction being duplicated by
RTR, since the router will unanimously decide the outcome of accepted
transactions that have lost their frontends after about 10 minutes. The
correct procedure in this case is for the client application to check
whether the transaction has been completed once the link to a router is
re-established.
%RTR-I-RQEQUALS, Transaction client was [A] on node [A]
Explanation: Displays the process name of the client
[A] and its node address [B] in messages relating to transactions.
%RTR-W-RSPFAC, Response from Node [A] about Facility [A]
Explanation: A negotiation with remote node [A] about
facility [B] has failed for the reason reported in the following line.
This may be a reason for system manager intervention.
%RTR-W-RSPNODE, Connection to node [A] failed : reason is
Explanation: A negotiation with remote node [A] about
facility [B] has failed for the reason reported in the following line.
This may be a reason for system manager intervention.
%RTR-F-RTRACPFAIL, RTR ACP failed - diagnostics written to [A]
Explanation: The RTR ACP process has failed - report
occurrence together with supporting information on current command to
RTR Engineering.
%RTR-I-SETTRAN, RTR SET TRAN command entered facility:[A] partition:[A]
tid:[A] state:[A] new_state:[A] since:[A] before:[A] user:[A]
Explanation: Log file entry recording that an RTR SET
TRAN command is issued.
%RTR-I-SETTRANEND, RTR SET TRAN complete with status:%ld and %ld
transactions updated in partition [A] of facility [A]
Explanation: Log file entry recording that an RTR SET
TRAN command is complete.
%RTR-E-SRVABOREC, Server aborted transaction recovery, check database
consistency
Explanation: Indicates that a server aborted a
transaction being recovered after an earlier failure.
%RTR-E-SRVDIEDCOM, Server exited after being told to commit, check
commit was completed
Explanation: Indicates that a server exited after
being told to commit a transaction.
%RTR-E-SRVDIEDREC, Server exited during transaction recovery, check
database consistency
Explanation: Indicates that a server exited whilst
performing recovery of transactions lost on an earlier failure.
%RTR-E-SRVDIEDVOT, Server exited after voting on transaction, awaiting
transaction result
Explanation: Indicates that a server exited before
completing a transaction.
%RTR-I-STATECHANGED, Transaction:[A] journal state is changed from [A]
to [A]
Explanation: Log file entry recording transaction's
tkj state has changed.
%RTR-I-TIMEEQUALS, Issued at [A]
Explanation: Displays the transaction start time [A]
in messages relating to transactions.
%RTR-W-TOOMANYNETIDS, Too many net IDs for node '[A]' - check for and
eliminate any unnecessary adapter/protocol combinations
Explanation: On a system configured to run multiple
network protocols over multiple adpaters, RTR can run out of space to
store and communicate the resultant node IDs. You may be able to
operate under this condition, but we recommend you review the system
configuration and eliminate any unnecessary adapter/protocol
combinations.
%RTR-I-TRINQUO, Router is quorate in facility [A]
Explanation: The router role now has quorum in the
facility [A]
%RTR-W-TRNOQUO, Router has no quorum in facility [A]
Explanation: The router role has lost quorum for
facility [A]
%RTR-I-TXIDEQUALS, Transaction ID = [A]
Explanation: Displays the transaction id [A] in
messages relating to transactions.