hp 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 a problem report.

%RTR-E-JOUNOTAVA, Error during recovery ([A]) from [A] journal

Explanation: The 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 is required, because 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 a transaction due to a full journal file, the 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 was 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: use CREATE JOURNAL /SUPERSEDE and submit a problem report

Explanation: The RTR journal file(s) found are unusable. Submit a problem report.
%RTR-I-JOUREDEL, Rewriting delete record to journal for completed TX [A]

Explanation: The delete record for the completed transaction is being rewritten to the journal.
%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: use CREATE JOURNAL /SUPERSEDE and submit a problem report

Explanation: An inconsistency was found in the record sequence in the RTR journal.

Corrective action:

1) Reissue the RTR CREATE JOURNAL /SUPERSEDE command.

2) Restart RTR.

3) Submit a problem report.

%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. These transactions are unrecoverable using V4 recovery mode. Restart RTR with recovery mode set to V32 using the command RTR SET NODE/RECOVERY=V32 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 between a router and a frontend or a router and a backend can fail if the link is in the closed state. A link can be closed if RTR suspects it is causing network congestion, or by the system manager.
%RTR-F-LNQOVERFLOW, LNQ table has overflowed

Explanation: There are insufficient static reservations of the per-link congestion-queue header blocks. Submit a problem report.
%RTR-E-LOADLIBFAIL, Unable to dynamically load the shared library

Explanation: The RTRACP could not load the shared library dynamically.
%RTR-E-LOADSYMFAIL, Unable to find the symbol in the shared library

Explanation: The RTRACP could not locate the symbol name in the dynamically-loaded library.
%RTR-I-LOGFILENT, [A] [A] [A]

Explanation: Displays the time/date, node name and user name associated with the subsequent error message.
%RTR-E-LRCERROR, Found an LRC error in an incoming message

Explanation: The checksum, also known as the 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 or later for [A] journal recovery, trying [A]

Explanation: To upgrade to V3.3 or later, RTR routers must first be upgraded. This is not always possible in environments that have mixed facility definitions on one node. During recovery from the 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 shut down or has become unusable ([A]) - automatic retry will follow

Explanation: DECnet or TCP/IP was stopped on a node running RTR. This can 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: A connection attempt to a remote node failed. 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 at the moment. Other routers can be tried.
%RTR-F-NOMOREPRT, No more partition slots available

Explanation: RTR is unable to create an additional partition since the limit on the number of partitions on this backend has been reached. Use the /Partitions qualifier to the 'start rtr' command to specify a higher limit. The default value for this limit is 500 partitions. The maximum permitted value is 65536.
%RTR-E-NORULES, The system.mon file has no rules by which this node can monitor itself

Explanation: This node has no rules by which it can monitor itself. Please verify that the system.mon file exists and that it contains REMEMBER EXPRESSION commands by which this node can monitor itself.
%RTR-E-NOTCONFIGURED, RTR not configured on [A] to recognize this node

Explanation: 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 could not establish a 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. Submit a problem report. The transaction can be exceptioned or removed from the secondary journal using the RTR SET TRANSACTION command.
%RTR-E-OVERFLOW, Table has overflowed, resize NCF

Explanation: There are insufficient static reservations for the NCF tables. Submit a problem report with an 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: An internal error has occurred in messages between RTRACPs. This may be caused by network packet data loss or corruption, so consider a network health check. If the condition persists, submit a problem report.
%RTR-E-PRTBADCMD, Partition command invalid or not implemented in this version of RTR

Explanation: The RTRACP 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: The message indicates the source or 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 before 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: The operator has requested a recovery wait override.
%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. This message can also appear 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. This message 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. This message can also appear 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: An operator request to change the backend priorities of the indicated partition has been accepted.
%RTR-I-PRTNEWPRITR, Priority change for partition [A]:[A] received from backend [A], new priority %u

Explanation: A router has received 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: The operator has manually initiated partition recovery.
%RTR-I-PRTSCANJNL, Partition %u scanning journal for node id [A]

Explanation: RTR is accessing the journal for node [A] that may contain relevant recovery information for the specified 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 (key range identification). A second message is written detailing the nature of the problem.
%RTR-W-PRTSHDRECEXIT, Partition [A]:[A] shadow recovery terminated by operator [A]

Explanation: The operator has requested a recovery wait override.
%RTR-I-PRTSHDWOFF, Command SET PARTITION SHADOW STATE OFF received

Explanation: A request to set the partition shadow state to off has been received by the router.
%RTR-I-PRTSHDWON, Command SET PARTITION SHADOW STATE ON received

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 several unavailable journals. Either RTR should be started on the missing backend or the facility should be trimmed and the server restarted.
%RTR-F-QAROVERFLOW, No more QARs left

Explanation: There are insifficient static reservations for the internal QARs (query acceptor records). Record all QRM counters using SHOW RTR /COUNTER=QRM* and submit a problem report with the corresponding RTRACP dump.
%RTR-F-QCROVERFLOW, QCR table has overflowed

Explanation: There are insufficient static reservations for the internal QCRs (query context record descriptors). Submit a problem report.
%RTR-F-QIROVERFLOW, No more QIRs left

Explanation: There are insifficient static reservations for the internal QIRs (query initiation record descriptors). Record all QRM counters using SHOW RTR /COUNTER=QRM* and submit a problem report with the corresponding RTRACP dump.
%RTR-F-RAEOVERFLOW, No more RAEs

Explanation: There are insufficient static reservations for the internal RAEs (response acceptor elements). Record all QRM counters using SHOW RTR /COUNTER=QRM* and submit a problem report with the corresponding RTRACP dump.
%RTR-F-RDEOVERFLOW, RDE table has overflowed

Explanation: There are insufficient static reservations for the internal RDEs (response dispatch elements). Record all QRM counters using SHOW RTR /COUNTER=QRM* and submit a problem report 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: 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 a transaction, but before completion of the transaction.
%RTR-W-RESERVECORRUPT, Reserve memory size was corrupted. The value %u has been reset to %u.

Explanation: Reserve memory size in shared memory was corrupted. The value [A] was either too large or too small; it has been set to the specified default value.

See the /RESERVE_MEMORY_SIZE qualifier of the START RTR command for more information on reserve memory size.

To obtain a reserve memory size other than the default, restart RTR specifying the desired value with the /RESERVE_MEMORY_SIZE qualifier.

%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 facilities on the two nodes concerned have been defined inconsistently.
%RTR-E-ROUTERUNAVAILTMO, FE discarded transaction due to router unavailability timeout

Explanation: Rarely a transaction can be aborted by an RTR frontend with this status. This can occur if an RTR client application has accepted the transaction but the link to the router is lost before the RTR frontend receives a response from the router. If no RTR router becomes available for more than eight minutes, the transaction is aborted by the frontend. This prevents the transaction being duplicated by RTR, because the router unanimously decides the outcome of accepted transactions that have lost their frontends after about 10 minutes. The client application should check whether the transaction has been completed, once the link to a router is re-established.
%RTR-W-ROUTERVSNLOW, Router [A] is incapable of providing data for the rtr_request_info() call for the 'gcs' info class

Explanation: This backend encountered a request, via the API call rtr_request_info(), for information in the global configuration and status (gcs) information class. To satisfy the request, the backend must gather data from all routers. However, router [A] is running an RTR version that is too old to understand the request. Consequently, the information returned from the request will be incomplete.

To ensure complete and accurate data, please upgrade all routers to a version that contains the RTR Explorer.

For more information on the global configuration and status information class, see the documentation on the rtr_request_info() API call.

%RTR-I-RQEQUALS, Transaction client was [A]

Explanation: Displays the process name of the client [A] in messages relating to transactions.
%RTR-W-RSPFAC, Response from Node [A] about Facility [A]

Explanation: A negotiation with remote node [A] about the named facility has failed for the reason reported in the following line. The system manager may need to intervene.
%RTR-W-RSPNODE, Connection to node [A] failed : reason is

Explanation: A negotiation with remote node [A] has failed for the reason reported in the following line. The system manager may need to intervene.
%RTR-F-RTRACPFAIL, RTRACP failed - diagnostics written to [A]

Explanation: The RTRACP process has failed. Submit a problem report with supporting information on the current commands.
%RTR-E-RTRNEEDUPGRADE, Node [A] in facility [A] has a higher, incompatible RTR version. Please upgrade

Explanation: Node [A] in the named facility has a higher RTR version than this router. This router is unable to understand the message and so the gcs information class in rtr_request_info will be incomplete. Please upgrade RTR on this router.
%RTR-E-RTRSTS, [A]

Explanation: A call to an RTR core API call caused an unexpected condition. Such an entry in the log file may be generated by transaction manager calls to the RTR XA interface. Other uses may exist. Read the error text to determine what action may be taken to rectify the situation. Conditions that cannot be remedied should be submitted in a problem report through the usual support procedures.
%RTR-W-SETABORTIGNORED, SET TRAN asked router to abort a tx (id=[A]) in [A] state

Explanation: An RTR backend believed a transaction is in the JNL_VOTED state and asked the RTR router to abort this transaction. However, the RTR router could not abort this transaction because the transaction on the router side has already been committed or aborted. The 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 used the SET TRANSACTION command to request that the RTR router abort a transaction that is in the JNL_VOTED state, but the RTR router could not find this transaction which may have been forgotten. The 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 that was 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 while 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, so before starting the http server, it checks whether TCP is enabled. If TCP is not enabled, then RTR will not be accessible from a web browser.
%RTR-E-THREADREQD, Use of this feature requires the threaded RTR shareable (librtr_r)

Explanation: The caller attempted to access RTR with multiple threads using the unthreaded RTR sharable. This condition is raised by the RTR XA (RM) interface. To eliminate this error, use librtr_r, not librtr.
%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 adapters, RTR can run out of space to store and communicate the resultant node IDs. RTR may be able to operate under this condition, but we recommend a review of the system configuration to eliminate any unnecessary adapter/protocol combinations.
%RTR-E-TOOMANYTRBE, The number of router or backend nodes in facility [A] is too large for this version of RTR

Explanation: The number of router or backend roles in a facility exceeds the capabilities of the current version of RTR. Contact RTR support for further information.
%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 identification [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 cause the client node to be disabled for a period of time.

Index Contents