Reliable Transaction Router
System Manager's Manual
Previous Contents Index

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

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-I-JOUNOTFUL, Journal file no longer full - journal write succeeded

Explanation: After failing to write the previous journal entry and aborting the Tx due to a full journal file, this entry was successfully written. It may still be advisable to review the journal file's available blocks to determine if there is sufficient space for continued processing.
%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-E-JOUREADINC, Error reading journal file. The journal file appears to be corrupt or incomplete - CREATE JOURNAL /SUPERSEDE and submit SPR

Explanation: The RTR journal file(s) found are unusable.
%RTR-I-JOUSEACOM, Journal search of node [A] facility [A] completed. [A] recoverable transactions found

Explanation: Journal search has completed. This message appears when the first facility with a backend role is created. 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-JOUTXUNRECOV, Found pre-V3.2 transactions in journal for [A], unrecoverable using V4 recovery mode

Explanation: Transaction records were found in the journal that were written by a version of RTR earlier than V3.2. This message indicates that these transactions are unrecoverable using V4 recovery mode. RTR should be restarted and recovery mode set to V32 using the command RTR SET NODE/RECOVERY=V32 to properly be able to recover these transactions.
%RTR-I-JOUTXVERSION, Journalled transactions written by RTR version %u, current version %u, facility [A]

Explanation: Transaction records were found in the journal that were written by another version of RTR.
%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 dynamically loaded library.
%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-W-NEEDV33TR, [A] router in facility [A] incompatible, need V3.3 for [A] journal recovery, trying [A]

Explanation: To upgrade to V3.3 it is required to upgrade RTR routers first. This is not always possible in environments that have mixed facility definitions on one node. During recovery from journal, if RTR detects that the router is an incompatible version, it will try to find another router with the minimum supported version.

No action is required if recovery is successful. This warning is a reminder that there are routers running with incompatible versions of RTR that should be upgraded in the near future. If recovery fails, then the routers will need to be upgraded.

%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-F-NOMOREPRT, No more partition slots available

Explanation: RTR was started with not enough partitions, or the default number of partitions isn't enough to run the application. Recent versions of RTR have a fixed limit MAX_NR_PARTITIONS (500). Please consult RTR Engineering if you need more partitions.
%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: 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-ORPHANSHADTX, Transaction copied to secondary shadow journal, no longer found on primary

Explanation: Remembered transaction was partially copied from primary to secondary journal. Transaction can no longer be found in primary journal. Report to RTR Engineering. Transaction can be exceptioned or removed from secondary journal using RTR SET TRANSACTION command.
%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: The RTR ACP received a request for an unknown partition command.
%RTR-I-PRTBEGIN, Partition %u/[A]:[A] start up, server pid [A] image [A]

Explanation: The first server started on a backend partition. This message has been superseded by %RTR-I-PRTBESTRA
%RTR-I-PRTCMDFRMBE, Command received for partition [A]:[A] from backend node [A]

Explanation: Log file message indicating the origin of a command.
%RTR-I-PRTCREATED, Pid %8s created [A]/[A]:[A] [A]

Explanation: A partition was created on the backend.
%RTR-E-PRTDELCAN, Partition deleted - operation cancelled

Explanation: A pending operation was terminated because the partition was deleted prior to completion of the operation.
%RTR-I-PRTDELETED, Partition [A]:[A] deleted

Explanation: A backend partition was deleted.
%RTR-W-PRTEND, Pid %8s ended [A]/[A]:[A]

Explanation: The last server on a backend partition exited.
%RTR-I-PRTJNLSTA, Starting rundown journal scan for partition [A]:[A]

Explanation: The partition rundown journal scan started on a backend.
%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: An operator request to change the failover policy of the indicated partition was accepted. 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: A backend received 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: A router received 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 %u 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 %u

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: A partition resume command completed successfully. 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 %u 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: A request to set the partition shadow state to off has been received by the router.
%RTR-I-PRTSHDWON, Command is set partition shadow state on

Explanation: A request to set the partition shadow state to on has been received by the router.
%RTR-I-PRTSTATRA, From %13s to %13s, [A]/[A]:[A]

Explanation: A backend partition changed state.
%RTR-I-PRTSUSPCAN, Suspend cancelled for partition [A]:[A], operator [A] - partition resumed by operator

Explanation: 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: A 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: 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 %u 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 an 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: 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: 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]

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-W-SETABORTIGNORED, Set Tran asked router to abort a tx (id=[A]) in [A] state

Explanation: An RTR backend believed a tx is in JNL_VOTED state and asked the RTR router to abort this transaction. However, the RTR router could not abort this tx because the tx on the router side has already been committed or aborted. RTR router could not process this SET TRAN ABORT request, but ignored it and logged this warning.
%RTR-W-SETABORTNFOUND, Router could not abort a tx ([A]) that does not exist

Explanation: An RTR backend uses the SET TRANSACTION command to request the RTR router to abort a transaction that is in JNL_VOTED state. However, the RTR router could not find this tx. This tx could have been forgotten presumably. RTR router could not process this SET TRAN ABORT request, but ignored it and logged this warning.
%RTR-I-SETTRAN, Facility:[A] partition:[A] tx:[A] old:[A] new:[A] since:[A] before:[A] user:[A]

Explanation: A SET TRANSACTION command was issued.
%RTR-I-SETTRANEND, Status [A], [A] transactions updated in partition [A] of facility [A]

Explanation: A SET TRANSACTION command completed.
%RTR-E-SRVABOREC, Server aborted transaction recovery, check database consistency

Explanation: 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: A server exited after being told to commit a transaction.
%RTR-E-SRVDIEDREC, Server exited during transaction recovery, check database consistency

Explanation: 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: A server exited before completing a transaction.
%RTR-I-STATECHANGED, TX [A] journal state changed from [A] to [A]

Explanation: A transaction's key-range journal state (tkj) has changed.
%RTR-E-TCPREQUIRED, HTTP server requires TCP, but this is unavailable or disabled

Explanation: HTTP server requires TCP only. So before starting the http server, it checks whether TCP is enabled or not. If it is not enabled then RTR will not be accessible from web.
%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.
%RTR-E-WRONGSERVER, Connection attempt to wrong command server: originating node '[A]', username '[A]'

Explanation: The HTTP-enabled command server found that the credentials presented by an HTTP client identified a username other than that under which the server is running. This could arise if the command server were restarted, which could invalidate some links in a current HTML display, or more seriously be an indication of system probing by unauthorized users. Frequent occurrence of this error will result in the client node being disabled for a period of time.

Index Contents